Godot: arquitectura de señales y EventBus

[leocagli]

Objetivo

Definir un bus de eventos central (EventBus) con todas las señales del juego para desacoplar los sistemas entre sí.

Alcance

• Autoload EventBus.gd como única fuente de verdad de señales
• Señales de unidades: unit_moved, unit_attacked, unit_died, unit_promoted
• Señales de ciudad: city_built, city_captured, production_complete
• Señales de turno: turn_started, turn_phase_changed, turn_ended
• Señales Web3: wallet_connected, proof_generated, tx_confirmed, web3_error
• Señales de UI: hex_hovered, unit_selected, city_selected, panel_opened

Skill de referencia

/godot-signal-architecture

Tareas

• Crear autoloads/EventBus.gd con todos los signal declarados y tipados
• Añadir EventBus a la lista de autoloads en project.godot
• Documentar cada señal con un comentario de una línea y sus parámetros
• Crear scripts/EventBusTypes.gd con enums compartidos (Phase, TerrainType, UnitType)
• Validar que ningún nodo se suscriba directamente a señales de otro nodo (todo pasa por EventBus)

Aceptación

Todos los sistemas se comunican exclusivamente a través de EventBus; no hay llamadas directas entre escenas no relacionadas y el bus imprime en _DEBUG cada señal emitida si OS.is_debug_build().

🎁 Evidencia = reward mayor

• Acá no hay mucho visual que mostrar, así que la evidencia es la salida: tests, logs o respuestas, pegados como bloque de código. Con eso entrás a reward de GrantFox.
• Si además grabás un video corto de los tests corriendo o del flujo reproducido, califica para reward mayor.
• No es obligatorio, pero pesa mucho en la evaluación.

Qué conviene mostrar en esta issue:

• Salida de _DEBUG del EventBus pegada como bloque de código, mostrando la traza de señales de un turno completo con turn_started, unit_moved, unit_attacked y turn_ended.
• Captura del listado de autoloads en project.godot o en la pestaña Autoload del editor con EventBus registrado.
• Salida de una búsqueda sobre scripts/ y scenes/ que muestre que no quedan connect directos entre nodos no relacionados, todo pasa por EventBus.

Pegá las capturas directo en la descripción del PR, arrastrándolas al cuadro de texto de GitHub.

[Glam26]

I'd like to take this on.

I've worked on similar enhancements involving backend services, frontend features, and testing. I'll deliver a solution that aligns with the existing codebase, includes thorough test coverage, and is accompanied by clear documentation where necessary.

[Glam26]

I'd like to take this on.

I've worked on similar enhancements involving backend services, frontend features, and testing. I'll deliver a solution that aligns with the existing codebase, includes thorough test coverage, and is accompanied by clear documentation where necessary.

[Glam26]

I'd like to take this on.

I've worked on similar enhancements involving backend services, frontend features, and testing. I'll deliver a solution that aligns with the existing codebase, includes thorough test coverage, and is accompanied by clear documentation where necessary.

[Glam26]

I'd like to take this on.

I've worked on similar enhancements involving backend services, frontend features, and testing. I'll deliver a solution that aligns with the existing codebase, includes thorough test coverage, and is accompanied by clear documentation where necessary.

[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, Glam26). This issue is open — comment /assign to take it.

[Vinaystwt]

I can take this.

I’ll add a centralized EventBus.gd autoload as the single place for game-wide signals, covering unit, city, turn, Web3, and UI event categories. I’ll keep the signals typed where practical, document every signal with its expected parameters, and add shared enum/type helpers only where they reduce ambiguity.

I’ll keep this scoped to decoupling architecture, not gameplay implementation. The goal is that scenes and managers communicate through EventBus instead of directly subscribing to each other, with optional debug logging in debug builds so emitted events are easy to trace.

[grantfox-oss]

🦊 GrantFox — @Vinaystwt has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #37)
2. Your PR will be reviewed by the Bitcoindefi maintainers

Good luck! Track your progress on GrantFox.

[rupesh-kumar-sah]

Hello team,

I am interested in working on this issue.
Plan:

1. Deliver Godot: arquitectura de señales y EventBus with proper loading/error states and clean component architecture.
2. Verify UI performance and zero console errors.

Looking forward to contributing—please assign whenever convenient!