Problem definition
An attribution break between recruitment, growth and changes to the 24-player order, match contribution and next investments.
View all bottlenecksGAME DECISION MAP
Pro Yakyū Spirits A
Design direction
Conditionally connect player, growth and order changes to verifiable match contribution and next investments.
View all mechanismsRead the recurring-flow summary
Scout S–D grade official NPB player cards → build a 24-player order and activate combinations → level, train, limit-break, inherit, reach Extreme, and apply titles → play CPU, auto, and real-time baseball modes → receive match, competition, and live NPB rewards → reinvest into players, the order, and the next game.
REASONING IN THIS GAME
Selected designs and judgment conditions
Selected principles and the game-local design6 design records
These entries describe the selected design. Design selection is distinct from actual application and effect validation. The classified objects below retain their own roles and connections.
Condition-branched contribution-explanation overlay
Participation-attribution overlay
Layered route-decision ledger
Acquisition-contract state ledger
LiveOps choice-rhythm ledger
Reference-to-practice-to-return connection overlay
Goals and residual processing
Initial IFR · goal direction
Realign rules, exposure and sequence for contribution conditions, result explanations and next-action connections.
Final IFR · design goal
Branch contribution explanations and next comparison actions by change type, mode, opponent and lineup role at the result surface.
Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
8 analysis items · Read the method
Core classification and definition · External Calendar
External Calendar
Scout S–D grade official NPB player cards → build a 24-player order and activate combinations → level, train, limit-break, inherit, reach Extreme, and apply titles → play CPU, auto, and real-time baseball modes → receive match, competition, and live NPB rewards → reinvest into players, the order, and the next game.
Events, operating schedules, and live operations reactivate participation, exchange, and reward states.
View pattern definition →Core Core loop
Player obtains players via contracts/scout → levels and trains players → raises team strength → enters V Road, League, real-time battle and events → earns rewards for reinvestment.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core Practice Match loop
Mutual followers can test teams in stamina-free practice matches up to 30 times/day.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Competition Trials material loop
Trials supply special ability materials and coins; time spent in Trials competes with V Road for stamina-consuming play.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Competition Real-time PvP loop
Real-time battle opens at player and supports ranked battles and friend room battles.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Supply Challenge Cup loop
Challenge Cup uses weekly changing participation conditions and 5-win cup progression with cumulative rewards after repeated wins.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Competition Strongest Decider loop
Strongest Decider is a round-specific ranking event with official schedules, entry conditions and record ranges.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Return Event loop
Limited events provide rewards such as Energy, S-rank contracts and ScoutP according to each event’s conditions.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Supply Resource split loop
Stamina is the direct match resource, while Energy is premium currency for scout, recovery and slot expansion.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core classification and definition · Action Feedback and Failure Attribution Break
Action Feedback and Failure Attribution Break
The affected flow runs through acquisition/growth/lineup → result → next investment; its limiting point is the combat feedback result handoff.
Outcomes, causes, rules, rewards, and retry information do not close the feedback loop needed for correction.
View pattern definition →Core Action Feedback and Failure Attribution Break · Combat Feedback
The affected flow runs through acquisition/growth/lineup → result → next investment; its limiting point is the combat feedback result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Action Feedback and Failure Attribution Break · Combat Feedback
The affected flow runs through result → next action; its limiting point is the combat feedback result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Decision and Planning Calculability Breakdown · Growth Economy
The affected flow runs through resource spend → route result; its limiting point is the growth economy planning handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Rights and Lifecycle Discontinuity · Asset
The affected flow runs through banner → duplicate/guarantee → next action; its limiting point is the asset lifecycle handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Pressure and Concentration Bottleneck · Operations
The affected flow runs through overlap → scope; its limiting point is the operations pressure handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Outcome and Contribution Attribution Failure · Social
The affected flow runs through friend reference → repeat practice; its limiting point is the social result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Contradictions
Contradiction Patterns
What must improve, and what must remain protected?
6 analysis items · Read the method
Core classification and definition · Outcome and Failure Attribution vs System Depth and Rule Integrity
Outcome and Failure Attribution vs System Depth and Rule Integrity
Improve Complexity Vs Convenience while preserving None.
Causes and retry conditions for outcomes, failures, and fairness must become attributable while strategic, combat, and competitive depth and rule integrity remain protected.
View pattern definition →Core Core Contradiction
Improve Complexity Vs Convenience while preserving None.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Freedom Vs Control
Across mode, improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Freedom Vs Control
Across source/sink, improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Revenue Vs Trust / None
Improve Revenue Vs Trust while preserving None.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Stability Vs Volatility / Performance Vs Load
Across skip → return, improve Stability Vs Volatility while preserving Performance Vs Load.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Freedom Vs Control
Improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Solution Mechanisms
Solution Mechanisms
Which intervention mechanism changes the condition?
6 analysis items · Read the method
Core classification and definition · State and Rule Visibility Encoding
State and Rule Visibility Encoding
Apply State and Rule Visibility Encoding to the source-declared core track while preserving its protected value.
Expose states, rules, and outcomes through readable signals and a consistent grammar to reduce decision loss.
View pattern definition →Core State and Rule Visibility Encoding · Core
Apply State and Rule Visibility Encoding to the source-declared core track while preserving its protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment
Apply State and Rule Visibility Encoding across mode while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment
Apply State and Rule Visibility Encoding across source/sink while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment
Apply State and Rule Visibility Encoding to the source-declared attachment track while preserving its protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment
Apply State and Rule Visibility Encoding across LiveOps while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Route and Return Handoff · Attachment
Apply Route and Return Handoff to the source-declared attachment track while preserving its protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Solution Compositions
Solution Compositions
How should interventions be combined and sequenced?
8 analysis items · Read the method
Core classification and definition · Single-Track Localized Bundle
Single-Track Localized Bundle
Connect 1 source-declared mechanism as Single-Track Localized Bundle.
Combine a core intervention with stabilizing or accelerating support within one problem track and keep its impact localized.
View pattern definition →Core State and Rule Visibility Encoding · Core Composition
Connect 1 source-declared mechanism as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment Composition
Connect 1 source-declared mechanism across mode as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment Composition
Connect 1 source-declared mechanism across source/sink as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment Composition
Connect 1 source-declared mechanism as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment Composition
Connect 1 source-declared mechanism across LiveOps as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Route and Return Handoff · Attachment Composition
Connect 1 source-declared mechanism as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across mode as Core-First Branch-Sequential Portfolio.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across mode as Parallel Local Contracts with Independent Rollback.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence