Hello,
This update covers three weeks of MapCTF development as part of the effort to catch the series up to the current state of the project. Grouping this work into a single post gives a clearer view of how the platform kept evolving across multiple areas at once, from backend behavior and admin tooling to the overall operational experience.
Let’s go!
Week of February 23, 2026
CI/CD, login, registration, and a gameboard that logs in first
Delivery pipeline and user flow moved together.
This week connected delivery and UX. CI/CD and GoReleaser configuration were added, archive contents were cleaned up, and the repository documentation got refreshed. On the product side, error templates, login flows, and registration functionality all landed.
What landed
CI/CD and GoReleaser configuration
Error templates
Login flows
Registration functionality
Authenticated gameboard
Why it matters
By the end of the week, the authenticated gameboard was working. That means MapCTF moved from template collection to session-aware interface with actual user flow. In engineering terms: fewer mocks, more consequences.
Referenced commits
Week of March 2, 2026
Settings became a subsystem instead of a pile of flags
Configuration started behaving like product logic.
A full settings package arrived this week and was integrated into both the API and map services. We added initialization, getters/setters, registration-related controls, admin configuration wiring, logout behavior, and template metadata for auth-aware rendering.
What landed
New settings package
Settings integration in API and map services
Registration-related controls
Admin configuration wiring
Better auth-aware template behavior
Why it matters
There were also quality-of-life improvements across the map UI: header branding, better error handling, cleaner JS, and more coherent template behavior. The result is a platform that can now be configured with intent instead of being edited by ritual.
Referenced commits
Week of March 9, 2026
Admin panel grows nerves, logs, and fewer page refreshes
Admin workflows and observability got sharper.
This week was a strong admin-focused sprint. We added a GitHub Actions workflow that posts commit updates to Telegram, then pushed hard on admin functionality: JSON/AJAX actions, better settings layout, language settings, rules integration, and active-page UI polish.
What landed
JSON and AJAX admin actions
Better settings layout
Language setting support
Rules integration and UI polish
New
logspackage
Why it matters
The heavier backend work was in observability and audit trails. The new logs package covers activity, announcements, failures, hints, registration, and scoreboard events, with test coverage included. In short: the admin panel is learning to observe the game instead of merely existing near it.
Referenced commits
See you next week!
Follow along
Telegram channel: t.me/mapctf
Best regards,
MapCTF Development Updates
