About the UMA DASH Wiki

This site is a fan-made wiki for UMA DASH, the Roblox anime racing experience by Krampus Studios. It is not affiliated with, endorsed by, or operated by Krampus Studios or Roblox Corporation. Mechanics, codes, and balance can change during public beta (currently branded around UPD 1.5). When official channels disagree with a wiki page, trust the official channel for that day and check back after we refresh.

• Play: UMA DASH on Roblox
• Discord: discord.com/invite/af8P36Xgj4
• Studio group: Krampus Studios
• Curated URL list: Useful links

UMA DASH asks you to equip an Uma, collect perks, craft builds, prestige (with possible alternate forms), climb leaderboards, and time ultimates in fast races with mobile, PC, and console support. Typical lobbies hold fifteen players. The wiki mirrors those player intents with hubs, leaf guides, and cross-links—not with rumor dumps or script stores.

Clear disclaimer

Everything here is unofficial. Reward numbers, code strings, and evaluation frameworks are compiled from public experience messaging, community verification, and reproducible in-game checks. They can go stale overnight when a hotfix lands or a like-goal code expires. We label uncertainty during public beta instead of inventing certainty. External “Uma Racing” content is a different Roblox title—do not mix their codes or systems into UMA DASH advice.

If a stranger DMs you a paid “private code pack” or an executor that supposedly unlocks Mirror Fragments, that is not part of Krampus Studios’ flow. Codes redeem in-game after group join and tutorial completion. Risk education lives on the scripts hub; free rewards live on codes.

What we cover — major hubs

Use this table as the site map. Every major hub below is intentionally linked so you can jump without hunting the header.

Hub	Purpose
Codes	Working promo codes, rewards, redemption steps, expired archive
Guides	How-to systems: onboarding, controls, prestige, builds, winning
Tier List	Early-beta evaluation framework (not fake absolute name gospel)
Scripts	Safety education—ban risk, categories, fair alternatives
Updates	Beta status, like goals, where to watch news
Players	Group, Discord, leaderboards, etiquette, teammates
Useful links	Official Roblox, Discord, group URLs plus wiki map

Leaf pages hang under those hubs—for example getting started under Guides, best Umas under Tier List, UPD 1.5 under Updates, and auto-farm education under Scripts. Hubs introduce the topic and point downward; leaf pages go deep.

How navigation works

• English lives at the site root (/codes/, /guides/, /players/, …). Other locales use prefixes such as /fr/ and /de/.
• Internal links in articles use trailing slashes and stay locale-agnostic in source form so every language build resolves correctly.
• The header is a three-column row: logo, keyword navigation with dropdowns, and a two-letter language switcher. Dropdowns list child pages and “view all” links back to the hub when a category grows long.
• Legal pages (/terms/, /privacy/, /cookies/) stay English-only shared URLs; language switching on those pages does not invent translated legal paths.
• Tier guidance is labeled early beta framework on purpose. We do not invent unverified Uma name ladders as permanent truth—see tier list.
• Scripts pages explain risks; they do not promise working undetected cheats. Prefer codes, guides, and clean practice.

When you are reading a French or German page, in-article links should stay in that language’s prefix after generation. If something jumps back to English unexpectedly, treat it as a bug report candidate—not as the intended design.

Editorial standards

1. Prefer experience-page facts, Discord announcements, and reproducible code lists over rumor screenshots.
2. Mark uncertainty during public beta instead of inventing certainty.
3. Keep progression advice consistent across codes, prestige, perk, and tier pages.
4. Encourage fair play in 15-player lobbies (players hub).
5. Never require readers to leave this wiki to understand a basic system—deep links should still summarize.
6. Distinguish UMA DASH from similarly named Roblox racers every time confusion appears.
7. Refresh after milestone code waves and named patches (UPD 1.5 and beyond).

Suggested reading order for new players

1. Useful links — bookmark the three official destinations.
2. Players — join the group and Discord the right way.
3. Codes — claim Gold, Prestige Carats, Prestige Spins, Color Rerolls, fragments.
4. Guides — start with getting started, then controls, builds, win conditions, prestige.
5. Tier List — spend spins and Carats intentionally.
6. Updates — understand the beta chapter you are playing.
7. Scripts — only if you need a clear “why not” when peers push farms.

Returning players after a patch can invert that order: updates → codes → tier list → guides.

Corrections and scope

Features can ship, soft-launch, or change names while the beta title still says UPD 1.5. If you spot a stale reward number or a broken internal path, compare against Discord and the experience description, then flag it through community channels tied to this project when available. We would rather shorten a claim than pad pages with invented charts.

This wiki will not:

• Sell codes or account boosts.
• Host malware-adjacent “free spin generators.”
• Pretend to be Krampus Studios support.
• Guarantee leaderboard placements from any single build.

It will:

• Keep major hubs interlinked: codes, guides, tier list, scripts, updates, players, and links.
• Explain public-beta systems with enough depth for a serious first week.
• Point you back to official Roblox and Discord surfaces whenever authority matters.

Related

• Useful links
• Players hub
• Updates hub
• Guides hub
• Codes

Thanks for racing fairly and for treating public beta as a shared construction site. Bookmark the hubs you use weekly, verify codes in-game, and keep the unofficial nature of this wiki in mind whenever balance shifts overnight.