Uma Musume Grand Live Token Planner

The Grand Live Token Planner (/token-planner) tracks which songs a player wants, which have already been bought, and how many of each Performance token remain to be saved.

The planner is entirely client-side. Song costs, effects, presets, technique requirements, and saved state all live in the browser code.

Token types

The five tracked resources are:

me is retained as the internal key even though the English UI abbreviates the resource as Co. Changing that key would require a stored-state migration.

Song states

Each of the 21 songs has a stable ID, year group, title, effect description, and five token costs. The two checkboxes have an enforced relationship:

• Marking Got also marks the song as Want.
• Clearing Want also clears Got.
• A song contributes to the remaining total only when it is wanted and not bought.

The summary counts wanted, bought, and open songs. For each token type:

Save = sum(cost for every wanted song that is not bought)
After Held = max(Save - tokens already held, 0)

Held tokens affect only After Held. They do not change song state or the raw Save total.

Presets

The page currently includes four presets:

Selecting a preset replaces the current wanted and bought sets. Reset Preset reapplies the selected preset, while Clear All empties song selections without changing held-token values.

Filters and bulk actions

The view filter can show all songs, a particular year, or only wanted songs that have not been bought. Search matches the song title and effect text.

Bulk actions operate on the currently visible songs:

• Want Visible marks every visible song as wanted.
• Clear Visible clears both Want and Got for every visible song.

This makes the order of filtering and bulk selection significant. For example, selecting Year 2 and choosing Want Visible changes only Year 2 songs.

Technique requirement reference

The technique requirement chips are a static quick reference:

They do not participate in token totals. If the source planning sheet changes, update the technique requirement data independently from song costs.

Persistence

State is saved under umatools-token-planner-v1 and contains:

• the selected preset;
• the active year/remaining filter and search text;
• held amounts for the five token types;
• wanted and bought maps keyed by song ID.

On load, state is sanitized against the known song IDs, preset names, filters, and non-negative integer token amounts. Unknown songs are discarded. The v1 suffix is the schema boundary: use a new version or an explicit migration when making incompatible changes.

Updating the planner

Song and preset data are currently constants in public/js/token-planner.js; there is no generated JSON dataset. When adding or changing content:

1. Give every song a permanent, unique ID.
2. Supply all costs through the song() helper so missing token types normalize to zero.
3. Keep preset references limited to known song IDs.
4. Update the visible song count in the HTML if the total changes.
5. Check old saved state still loads safely.
6. Verify totals by hand for at least one mixed wanted/bought/held plan.

Source files