Jared H-K's CHARGED UP Scoring Calculator

I’m excited to share my scoring calculator for the 2023 game: CHARGED UP. The calculator will help you augment different scenarios with points and can help with practice, forming strategy, or understanding relationships to scoring elements.

The scoring calculator is based in Google Sheets. Click to visit the Resource Hub and make a copy. An internet connection is required initially, but you can use the Google Drive extension to work offline or download to Excel (not tested).

If you notice any issues or have suggestions, please let me know. You’ll notice the version information at the top – if your sheet is out of date, return to the link to make a new copy.

Good luck this season!

21 Likes

Cert looks to be out of date

Warning has vanished on me, so it might be something on my end?

I recently updated the site’s hosting. I’m guessing it was a cache issue resolved on refresh. Thanks for letting me know!

2 Likes

looks like in auto for the calculator, “docked to charging station and not engaged” vs “engaged with charging station” are reversed at least for me. I’m pretty sure it should be 12 for engaged and 8 for docked.

Thanks.

Thank you – this has been corrected in v1.1.

If you drop below 3 in any choice for endgame, you cannot select 3 again. The other two options in the followng image are zeroed. This is on v1.1.

This is by design. Since there are only three robot per alliance, only three robots can be scored. You need to adjust the three to 0, 1, or 2 in order to have the other options populate non-zero options.

Google Sheets doesn’t have a great way to do dynamic dropdown menus and this is the closest I’ve ever been able to get.

If the other two are zeroed, wouldnt i then have an option to make the “engaged” be 3? That is what im missing in the above screenshot.

I can’t see what you have selected from your screenshot, and I can’t replicate what you’re describing to my understanding. Feel free to DM a link to your copy or more details and I can see what’s up.

Section 6.4.1

Only 1 GAME PIECE is counted per NODE.

Yes I missed that - weird page break :). Thanks.

It seems like the scoring is inverted. The bottom row is putting out the high row scores and vice versa.
image

Wow I’m all kinds of backwards today. This has been fixed in v1.2. Thanks!

3 Likes

V1.3 reflects my new understanding (thanks to the folks I had discussions with on this) that an alliance cannot have both DOCKED and ENGAGED robots at the same time. V1.3 changes the allowable selections in the dropdown menu to not allow for the impossible scenario.

If you’re confused, so was I, but I reread that section many times.

2 Likes

If you score a piece in auto, it should not be able to be rescored in tele-op. Additionally, if it is not present at the end of tele-op, the auto points should be removed.
Section 6.4:

If a GAME PIECE scored in AUTO gets removed from its NODE during TELEOP, the AUTO points are
removed. If a GAME PIECE is scored in that NODE again, the AUTO points associated with the original scored GAME PIECE are restored.

Also the engaged vs docked gives an error

And the point values for the levels are still wrong
image

(based on v1.4)

Thanks for your thoughts, Ankur. I don’t believe any of these are issues that need fixing – maybe the last item if it’s still not resolved…let me know.

Please see this note which has been included in all versions and addresses this concern:

This is a non-customizable Google Sheets error which occurs when a value is not the list of acceptable values. Because 3 robots are selected, now the only “acceptable” value is 0, making 2 and 1 appear invalid. However, if you were able to select it, it’s not invalud.

Can you make a new copy and see if this is still an issue? My working copy has it corrected, so I’m wondering if something got shifted on your sheet or you may have made a copy right as I was updating versions.

I saw that note right after I posted.


It looks like now the tele-op is resolved, but the auto is not.

Ah, I know what’s happening. Some people are expecting the top row to represent the top and others the bottom. Admittedly, this can be made more clear. I’ve corrected these a few times, working towards different understandings. I’ve fixed the math, but I’ll work on some cosmetic improvements and rename the version soon-ish.

EDIT: Made these cosmetic improvements and released 1.5.

1 Like

All bugs aside, this is a great resource! And thank you fo reposting it even if its still a work in progress somewhat. This is really very useful for those “What if” scenarios we like to play