The developer updated an incident simulation platform built on Flask and SQLite by adding a weekly challenge mode and public user profiles. The system avoids using cron jobs or additional database tables to manage the weekly rotation.
The weekly scenario is selected lazily upon the first request of the week. The system uses a random number generator seeded with the week's key to ensure consistency. To prevent repetition, the selection process excludes scenarios used in the previous four weeks, as well as tutorial cases.
The leaderboard logic queries existing run data directly. It filters attempts completed within the specific week and ranks players primarily by score, then by speed. Administrative accounts are excluded from the rankings to ensure fairness.
Public profiles display solved cases and achievements for users who opt in. To protect privacy, these pages return a 404 error for users who have not consented to leaderboard participation and are marked with noindex tags to prevent search engine indexing.