Implementation Proposal — Persistent Map Editing & DB Migration

[lovely60100]

I can implement the persistence layer for map editing, following the existing "game-data" revision architecture rather than introducing a separate persistence pattern.

Planned implementation:

• Add the database representation required for edited maps.
• Build an idempotent importer for all 294 maps from "api/src/mapas_source/".
• Preserve the existing file-based maps as a fallback during migration.
• Implement DB-over-file precedence for edited maps.
• Integrate map edits with "game_data_revisions", including checksums/revision tracking.
• Add integration tests covering the full migration and persistence flow.

I’ll prioritize preserving current game behavior while keeping the importer safe to run repeatedly without duplication or corruption.

Before implementation, I’ll verify the current map-loading and revision code paths so the solution fits the existing architecture cleanly.

I can deliver this as a focused PR with tests and clear migration notes.

[JohnArayaE]

I would like to work on this issue because persistent map editing needs to integrate cleanly with the existing game-data revision architecture without disrupting the current file-based map behavior or introducing a separate persistence model. I can first review the current map-loading and game_data_revisions flows to identify the safest integration points, then add the database representation for edited maps and build an idempotent importer for the 294 existing maps under api/src/mapas_source/. From there, I can implement DB-over-file precedence for edited maps while preserving the current files as a migration fallback, and connect map changes to the existing checksum and revision-tracking mechanisms. I can also add integration coverage for repeated imports, migration safety, persistence across edits, fallback behavior, and revision consistency so the importer can be safely re-run without duplication or corruption. I will keep the implementation focused on preserving current game behavior and include clear migration notes with the PR. I can have a PR ready within 1–2 days.

[ZacLou]

Senior full-stack developer 15+ years. Expert in database design, persistent storage, scalable systems. Implemented persistent map editing and DB migrations in production. Ready to start immediately.

[Chidi-Dev1]

I’d love the opportunity to resolve this issue. Kindly assign it to me.

[Joyful12-tech]

Hello Maintainer! I'd like to work on this issue. I can deliver it following the requirements and submit a quality PR within 2 days. Thank you!

[ranjeet150]

Hi everyone,

I would like to resolve this issue. Here is my proposed execution plan:

• Implementation: Deliver a clean, modular solution for Implementation Proposal — Persistent Map Editing & DB Migration strictly following Bitcoindefi/OpenAO conventions.
• Testing & Verification: Cover changes with automated tests ensuring CI passes smoothly.
• Delivery: Ready to ship a thoroughly tested PR within 12–24 hours with passing CI.

Ready to deliver a clean, tested PR within 12–24 hours. Please assign!