#HuntTheMouse needs more than the player-facing game. Operators have to configure coins, hints, power-up prices, announcements, rewards, merchants, campaign content, and support actions while live hunts are running. Multiple campaigns can be configured and operated at the same time, across different roles and campaign editions, so they need one secure operational surface instead of direct API calls and disconnected scripts.
I built this platform on both sides — the NodeJS and Express services underneath as well as the VueJS and Quasar console on top. On the server I implemented the operational APIs and the business rules behind them: live game controls, campaign configuration, prize and merchant operations, and dynamic pricing for shrink, sonar, detector, golden hints, and eliminate-grid mechanics, with server-side validation on every action capable of altering a hunt already in progress.
Those endpoints can move live gameplay and real prize money, so I also owned the access layer: role-aware permissions scoped per operator action and campaign edition, signed requests between console and services, encryption for sensitive operational payloads, and guarded approval paths that keep high-impact changes from going out on a single unchecked call.
On the client, a config-driven command console renders number, text, textarea, and select controls from those server definitions; dedicated tools cover live coin status, refunds, redemption codes, QR and file operations, text and silver hints, safety hints, brand actions, documents, and the pricing mechanics above.
For campaign operations I built interfaces around merchant invitations and submission review, including approve and reject flows, outlet details, and MapLibre location previews. Prize operations cover groups, stock, roll weights, image uploads, quantity adjustments, and XLSX import and export, while branded-coin review exposes sponsor submissions, coin setup, uploaded assets, and guarded approval actions.
The platform also includes a validated in-game notification composer with templates, scheduling, frequency rules, previews, rewards, and publish states, plus specialist tools for location queries, coin-winner exports, pricing tests, account simulators, encryption, and jigsaw-puzzle configuration. Pinia coordinates shared user and event state; repository modules keep API domains separated; signed Axios and Socket.io connections support authenticated operational access.
The result is a single role-aware operations platform spanning campaign setup, live-game intervention, content and economy changes, merchant onboarding, prize fulfilment, and player support. Teams can configure and run multiple campaigns in parallel, while new campaign-specific workflows remain focused modules built on shared navigation, forms, dialogs, repositories, authentication, and operational patterns.