Planned Work — Next Chapter

Planned features are not included in the current release. Investigations may lead to a different implementation or be deferred. Reliability fixes can take priority between milestones.

• Build reliable two-player matches, starting with delay-based networking if it reaches working matches substantially sooner. Preserve a path to rollback.
• Investigate Generations' original networking and battle replay system, including deterministic playback and genuine state restoration.
• Assess RPCS3/RPCN protocol and infrastructure reuse before choosing a route. Platform compatibility, licensing, authentication and public-service requirements must be checked; existing RPCN access is not promised.
• Test complete matches, disconnections and recovery on two PCs across separate connections.

• During a natural pause in online work, add profile Ninja Info Cards: completed Free Battle wins/losses, win percentage and three most-used characters. Keep version-specific statistics distinguishable and leave room for online results.
• After the first functional online milestone, replace View Bonus Requirements with View Match Stats: compare players' APM, dash types, substitutions, attacks, Kunai, jutsus, supports and damage. Include counters only where the mechanic exists.
• Reuse the accepted responsive APM calculation, count discrete inputs consistently, distinguish attempted inputs from executed actions and use active match time.
• Later analysis may add data-based playstyle names, strengths/weaknesses and decision advice. “Aping” and “Black Air Forces” are tentative nickname ideas, not initial statistics-page features.

• Expand practical training tools and independent map/music selection.
• Add individual UNSG V2 mechanic switches in the launcher, including the ability to disable selected cancels such as Kunai → Jump. These controls are still queued.
• Extend profile-linked collection features where practical. Define ranking/Elo rules after reliable online play exists.

• Continue deeper optimization after functional online, with measured comparisons and an available working renderer fallback.
• Investigate Vulkan rendering correctness before offering it as a supported alternative.
• Resolve higher-resolution pause/ultimate rendering issues and evaluate additional graphics options.
• Assess lower-end hardware support and Linux/macOS feasibility. No unverified minimum specification or performance improvement is promised.

• Explore character, costume and map backports, using the established variant-specific portrait workflow where applicable.
• Investigate alternate movesets while preserving existing versions. Pain's newer tilt is a reference to confirm; a second outfit and a move-selection menu remain alternative approaches to compare.
• Assess additional character slots, custom content and mod-tool compatibility before committing to a particular implementation.
• Retain story/cutscene corrections, visual polish and expanded music/map requests.

• Maintain the consolidated, searchable version guide and organized launcher notes. A hosted browser link remains an option.
• Retain the community wiki/results-site and Sally Discord knowledge-bot requests as later work.
• Advanced CPU behavior, additional collection features and a new R3 mechanic require further design or feasibility work.

• Retain reported support/projectile contact interactions, Hidan substitution-to-guard, wall dash-clash/rebound behavior, puppet protection and ranged-cancel edge cases for focused reproduction.
• General first-air-hit inconsistency after Air Chakra Dash remains parked until reproducible. Raikiri's recorded contact problem is corrected; other reported dash-to-jutsu delays need equivalent comparisons before being classified as bugs.
• The withdrawn 80% HUD experiment is not scheduled for another attempt without a new request.