Slitheroo Devlog
This page is the project journal for slitheroo.online. It is where gameplay changes, maintenance choices, and rule clarifications are explained in plain language instead of being left as invisible code changes.
Why The Public Pages Were Rewritten
The game itself had more substance than the surrounding site was showing. The earlier public pages leaned too hard on broad arcade-language and not enough on first-hand documentation. This rewrite shifts the focus toward real publisher identity, clear contact information, usable support pages, and product-specific explanations of how Slitheroo actually works.
That matters for players and for site review. A live game should not feel like it is hiding behind generic filler. If the site says there is a seeded daily board, a live leaderboard, local stats, and optional monetization, the supporting pages should explain those systems directly.
What Daily Challenge Adds
The Daily Challenge was added to solve a fairness problem. A random board is fun, but it makes direct score comparison messy because one player may simply get an easier sequence than another. A seeded daily board keeps the pressure of score-chasing while removing that randomness gap.
It also gives the site a daily rhythm. Players can warm up in Ranked, then take one serious run on the shared board. That is a stronger reason to return than adding more decorative content around the game.
Why Local Stats Stay Local
Not every game number needs to be pushed to a backend. Personal bests, unlocked achievements, streaks, and local preferences are stored in the browser because they should be fast, private to the player, and resilient even when the network is missing. The live backend is reserved for the parts that actually need shared state, mainly leaderboard data.
This split keeps the game lighter and makes the support story easier to explain: if your stats disappear, the first thing to check is local browser storage, not the public leaderboard database.
What Makes A Good Slitheroo Update
A good update changes how the game feels or makes the site easier to understand. That can mean a real mode addition, a better explanation of leaderboard rules, a fix for broken mobile behavior, or cleaner support content. It does not mean publishing more vague text just to make the site look larger.
The rule going forward is simple: if a new page or feature does not help a player, explain a live system, or document a real change, it should not be published.