Godot: autoloads (GameState, TurnManager, EconomyManager)

[leocagli]

Objetivo

Implementar los singletons globales que mantienen el estado del juego accesible desde cualquier escena y sincronizado con la capa Web3.

Alcance

• GameState.gd: estado completo (mapa, unidades, ciudades, jugador activo, turno actual)
• TurnManager.gd: fases de turno (ver #godot-turn-system)
• EconomyManager.gd: acumulación de recursos por turno
• WebBridge.gd: puente JS (ver #godot-web-bridge)
• EventBus.gd: bus de señales (ver #godot-signals)
• Serialización/deserialización del estado a Dictionary para enviar al contrato

Skill de referencia

/godot-autoload-architecture

Tareas

• Registrar todos los autoloads en project.godot en orden de dependencia
• GameState.gd: vars tipadas para units: Array[UnitData], cities: Array[CityData], map_seed: int
• Método GameState.serialize() -> Dictionary y GameState.deserialize(data: Dictionary)
• GameState.sync_from_chain(on_chain_state: Dictionary) llamado tras cada resolve()
• EconomyManager.calculate_yields() recorre ciudades y actualiza GameState.resources
• Tests mínimos: verificar que serialize → deserialize produce estado idéntico

Aceptación

Cualquier escena puede acceder a GameState.units sin importaciones adicionales y el estado se reconstruye correctamente desde los datos on-chain tras un turno.

[gloskull]

Hi, I’d love to work on this issue. I have 4 years of experience across backend, frontend, full-stack, and smart contract development. I understand the task clearly and can deliver a clean, efficient, well-tested solution on time, with strong focus on code quality and maintainability. My PR will be submitted in under 10 hours.

[leocagli]

🟢 Reopened for assignment. The only interest so far was from accounts flagged for automated mass-claiming (gloskull). This issue is open — comment /assign to take it.

[leocagli]

🟢 Reopened for assignment. The only interest so far was from accounts flagged for automated mass-claiming (gloskull). This issue is open — comment /assign to take it.

[Vinaystwt]

I can take this.

I’ll add the core Godot autoload architecture for GameState, TurnManager, and EconomyManager, register them in project.godot, and keep the responsibilities clearly separated: GameState for serializable game state, TurnManager for current turn/phase ownership, and EconomyManager for per-turn resource/yield calculation.

I’ll include GameState.serialize(), GameState.deserialize(...), and GameState.sync_from_chain(...) with dictionary-based state so it can round-trip cleanly for Web3/contract integration later. I’ll keep the implementation minimal and foundation-focused, reuse existing bridge/event patterns if present, and avoid adding full gameplay systems in this PR.