HomeThe short version is simple: the original build of Exorion got us moving quickly, but it is no longer the right foundation for the version of the platform we want to ship next. The product has grown, the expectations around it have changed, and the quality bar we want for the next era is much higher than what a light refresh could realistically deliver.
That is why this version is being phased out instead of endlessly patched. We would rather be direct about that now than quietly drag an aging build forward while pretending it is still the future.
Why we are retiring this build
The reason this build is being retired is more specific than a routine refactor. Due to a recent ongoing situation involving one of Exorion's original developers, and the feud against Discord relating to their account and ownership of the bot, we had to take a much harder look at how Exorion should exist going forward. That situation made it clear that the old 2024 line was not the foundation we wanted to keep carrying into the future.
Rather than force the platform to keep orbiting around old assumptions, we decided to rebuild with clearer structure, stronger ownership boundaries, and a much more deliberate long-term direction. The old version still mattered. It proved ideas, gained real users, and taught us what needed to change. But it is no longer the base we want to build the future on.
What you are already seeing
The new dashboard, guidebooks, and website overhauls you can already see are not side quests. They are the visible front edge of the new Exorion. We started shipping the public-facing foundation first because clarity matters: better docs, cleaner navigation, and a more coherent site make it much easier to understand where the product is going.
In other words, if the site feels more structured lately, that is intentional. We are building the language, layout, and product flow that the next generation of Exorion will sit on top of.
What this means for servers already using Exorion
For servers already using Exorion, this shift is less about an overnight cutoff and more about a change in product philosophy. We are massively rethinking older feature areas such as ER:LC Management and the Staff Punishment System. Instead of re-shipping the same niche toolset that became overrated within the ER:LC community, we want to release more distinguishing features with a clearer identity and broader value.
- The 2024 generation will continue to exist while the transition is prepared responsibly.
- Some familiar systems may return in a completely different form, and some may be replaced outright.
- The newer dashboard, guides, and website surfaces will increasingly reflect the direction of the platform going forward.
Where we go from here
The next version of Exorion is about more than a visual redesign. It is about better structure. We want a system that is easier to extend, easier to document, easier to reason about, and easier for server owners to trust.
That means clearer permissions, more polished settings flows, stronger guide coverage, and a website that feels like one product rather than several disconnected surfaces. It also gives us room to explore ideas we would have struggled to ship cleanly in the old build.
We are not interested in replacing one messy stack with another. The whole point of this change is to create something that feels deliberate end to end.
Thank you for sticking with us
Transitions are always awkward in the middle. Some parts look polished before others. Some ideas arrive in writing before the feature is live. That is normal. What matters is that the direction is now clearer: this older version is winding down, and the next Exorion is already being built in front of you.
If you want to track that work, keep an eye on the blog, the new guidebooks, and the ongoing dashboard updates. They are the clearest signals of what is coming next.