Run a Dance Studio can add or rebalance dancers through updates, and the checked official public description does not publish a complete permanent roster. A trustworthy dancers list therefore starts with the names and fields visible in the current game, tied to a check date. This page shows how to build that list and turn it into useful solo and group choices without guessing missing data.
Confirm the correct experience
Join from the official Roblox listing. Confirm Dance Interactive is the creator and the root Place ID is 129244982349741. A roster from another dance experience, a role-play game, or a test build should not be merged into this one.
Record the client version or date and the menu used. A dancer shown only in an event preview or pack advertisement may not yet be owned or generally available, so label the context.
Build a roster table from live fields
For each dancer you can inspect, record only visible fields. Useful columns may include name, rarity or tier, style, displayed stats, training state, current routine, eligibility notes, and acquisition screen. Leave a field blank when the game does not show it.
Keep owned dancers separate from possible pack contents. If the pack panel shows a pool, capture the panel before opening. An image of a character is not proof of its name, odds, or permanent availability.
Sort by usable role
Create three working groups: solo candidates, group core, and backups or specialists. A dancer can appear in more than one group. The goal is to see whether the next performance has enough eligible, prepared performers.
Within each group, compare live stats and training investment, but do not invent an overall power score. A performer with useful style coverage or a saved routine assignment may be more valuable than an untrained higher-tier option.
Track acquisition accurately
Community reporting associates Gems and packs with obtaining dancers and other assets. Use the current pack details for cost, contents, and any guarantee. Record what was actually received without turning a small sample into published odds.
Enrolment may also appear in the studio loop. Read whether a control is enrolling, claiming, opening, purchasing, or assigning. Similar animations can represent different actions and currencies.
Mark training and routine assignments
Add the teacher or training plan shown for each active performer. Record displayed stats before and after training so a change is attributable. The training guide explains that comparison.
Also note whether a dancer is in a solo, group, or competition entry. Before fusing, deleting, or replacing a duplicate, reopen those routines. A roster list is most useful when it prevents an active performer from being consumed accidentally.
Verify new dancers after an update
When update notes or community posts mention a new dancer, look for the name in the live roster, pack pool, event screen, or creator-owned announcement. Capture spelling, visible attributes, availability, and date. Do not copy a fan nickname into the canonical name field.
If the dancer appears only in a screenshot, label it as observed promotional material until the live client confirms acquisition. Limited availability should include the event or timer shown, not an assumed permanent end date.
Handle duplicates and removals
Community reporting says a Fuse option for duplicates and batch deletion for common dancers arrived with the September 4 update. Check whether those controls exist in your version and read the result preview. Preserve at least the copies assigned to active routines or holding meaningful training until the interface proves what transfers.
For a missing dancer, refresh the roster, clear filters, check assignments, and rejoin once. Do not repurchase immediately. Keep ownership evidence and report persistent loss through creator or Roblox support as appropriate.
A useful comparison checklist
- Is the dancer owned, previewed, or only advertised?
- Which solo or group role can they fill now?
- What style and stats are visibly displayed?
- How much training is already invested?
- Are they assigned to a saved routine?
- Does an event or pack timer affect availability?
- Would a duplicate action remove something still in use?
Frequently asked questions
Why is there no fixed full table here?
A static list without current first-party fields would quickly become incomplete or misleading. The live roster and pack screens are the authority for names, availability, and values.
Is rarity enough to rank dancers?
No. Consider eligibility, displayed stats, style coverage, training, and routine fit. The public official description does not publish a universal tier formula.
Can I use a dancer shown in a pack preview?
Only after the account actually owns or enrols the dancer and the routine selector marks them eligible.
How do I compare two dancers fairly?
Use the same live fields and date, then compare them for one specific solo or group role. Avoid combining unknown values into a made-up total.