Purge City Projects · Minecraft
One place for the Diggy installer, current version information, connection details, update instructions, mod references, and the settings used on Diggy.
expressing-france.tun.ply.gg
The final public address will appear here when the server opens.
Get Diggy
Choose your operating system. Install once, then keep using the same Diggy software for normal future updates.
Purge City Projects · Diggy
Possible future improvements and testing we want to remember.
This is a working wishlist of possible future improvements for Diggy. These items are not promises, and they are not listed in priority order. This is mainly a place to keep track of ideas and remember what we want to work on next.
Build an isolated production-like environment for client, server, installer, updater, manifests, Admin/API, and website integration testing. Support direct-upgrade testing from older supported Diggy states, then promote the exact validated bytes to production.
Finish the permanent Toxicc domain, DNS, HTTPS, routing, hosting, and maintainable website deployment path, with external verification after changes.
Restore automatic Discord dev-log posting when player-facing published APIs or release contracts change. Combine related changes into one post, publish only after the corresponding change is live, and avoid duplicate announcements.
Provide centrally managed community waypoints for player builds and important locations. Keep shared waypoints separate from personal Xaero data and never overwrite, delete, or duplicate player-owned maps or waypoints.
Harden the remote Admin path so status, console commands, whitelist actions, restart/stop, update controls, and incident evidence remain reliable through server and network interruptions.
Add verified on-demand and scheduled backups for irreplaceable server state, including worlds and player data, plus safe restore workflows and off-machine recovery coverage.
Stage updates while players are online, apply only when the server is empty or explicitly authorized, and serialize update/restart ownership so destructive operations cannot overlap.
Expand server, JVM, tick, resource, tunnel, Admin/API, crash, and disconnect diagnostics so incidents can be investigated remotely without needing direct access to the host PC.
Provide a tested rollback path to the last known-good frozen release and verify restored state without rebuilding release artifacts or replacing unrelated player/server data.
Continue direct-upgrade, repair, idempotency, ownership, install-root, and player-data-safety work so supported older Diggy states converge safely to the current release.
Continue addressing rubberbanding, simultaneous disconnects, join hangs, server-thread stalls, memory pressure, and tunnel-versus-runtime failure classification with regression coverage for recurring incidents.
Maintain one conflict-free Diggy keymap and configuration ownership model so new mods do not silently introduce keybind conflicts or overwrite player preferences.
Keep short, practical recovery procedures for common incidents such as server down, Admin down, update pending, failed release, player join failure, and rollback.