Yakkamon reports that 99,518 trainers are already waiting through preregistration. The number is a strong signal of attention, but for Night Ash it immediately becomes a capacity question. A waiting list does not yet describe concurrent players, regional demand, device mix, or return behavior. It does establish the size of the promise: every person who arrives expects identity, entry, progress, and support to work without learning why a backend is under strain.
Launch Operations has converted the figure into three demand bands rather than assuming all registrations will appear together. The first band tests a controlled opening, the second simulates a concentrated event window, and the third models recovery after a failed regional dependency. Each band has a maximum queue time, session success target, and rollback authority. Teams will know before release who can reduce load and who can restore service.
Xai's gaming-focused Layer 3 architecture provides the relevant execution foundation. Built with Arbitrum Orbit, Nitro, and AnyTrust, it is designed for web3 game activity at scale. Night Ash will use that capability for frequent application actions while keeping the game server authoritative over immediate play. The chain records the durable events that need continuity; it does not replace responsive game logic or excuse weak capacity planning.
The first rehearsal will use 100,000 synthetic registration records and a smaller controlled group of active testers. Engineers will measure account creation, session entry, inventory initialization, retry behavior, and the delay between a completed route and its durable record. Deliberate network faults will be introduced during the busiest interval. A successful run must recover without duplicating equipment, losing progress, or asking a player to create a second identity.
Identity Command owns registration integrity, Game Operations owns the active session, and Network Command owns durable Xai activity. Support Operations owns the language and timing of incident communication. Those lines matter because a launch becomes chaotic when every team can observe a problem but no team has authority to close a gate. The opening plan will therefore include named decisions, not only monitoring thresholds.
A large preregistration count can be more than marketing evidence when it forces the organization to prepare honestly. Night Ash will treat every expected arrival as a load-bearing commitment and will widen access only as the system proves itself. Xai's gaming-first architecture gives the route room to grow, while disciplined rehearsals protect the people entering it. If both layers hold, anticipation can become a lasting population rather than one overloaded night.