I built these because I wanted progression-heavy worlds for my people and because apparently simply joining somebody else's server would have been too easy. They are not running on the smaller VPS now. This page keeps what I made without dressing old infrastructure up as a current service.
Current status: intentionally offline. There are no active join addresses, public passwords, whitelist forms, or Minecraft server hiding behind this page. If one of these returns, the page will get current connection details then, not before.
The biggest version of the idea: a heavily customized progression world, a whitelist flow, mod reporting, player activity, and one Flask API that fed both this site and Hazel. It taught me to make the useful status live in one place instead of copying it into every interface.
Its own isolated stack, built so a Hytale restart could not take it down with it. Enshrouded's access model was password-based rather than whitelist-based, which made it a useful reminder that two games on one box still should not be forced through one fake universal control system.
Palworld did not expose the rich status data the other services did, so its API only claimed what it could prove: whether the service answered. It is a small distinction, but it is the same rule the rest of this site runs on. If the data cannot support a player count, do not print one.
The current smaller setup lives on the Infrastructure page →. For the games themselves, hosted or not, wander over to Gaming →.