Niko's Nook

Project

• Origin: After running private Minecraft servers for friends, I launched Niko’s Nook as a larger public community in November 2025.
• Audience: The application-based community is designed for players who want a moderated, long-running world rather than a disposable public server.
• Scale: The community has more than 200 members, typically supports 5–20 concurrent players, and has nine volunteer moderators.
• Engineering shift: Opening the server to a wider community required stronger permission boundaries, moderation evidence, abuse detection, backups, and recovery planning.

My role

• Ownership: I manage hosting, DNS, plugins, permissions, security, logs, performance, capacity planning, backups, and recovery.
• Access separation: Infrastructure and host-panel credentials remain separate from day-to-day moderation permissions.
• Collaboration: Volunteer moderators review applications and handle community moderation through scoped tools.
• Boundaries: Moderators manage player conduct and applications, while I remain responsible for the technical platform and recovery procedures.

Process

• Runtime and access: The server runs on Paper, with administrative access through the host panel and SFTP. map.nikosnook.net provides an interactive view of the live world.
• Audit and moderation: CoreProtect records world changes, GrimAC supports abuse detection, and ItemsAdder extends the player experience without changing the underlying operational controls.
• Backups: Hourly backups are copied outside the primary host’s failure boundary so recovery does not depend on the same system that runs the server.
• Incident: A hosting fault required the service to be restored from backup. The recovery demonstrated that the backup process could be used under real pressure rather than only existing as a configuration.
• Communication: Expected downtime and recovery progress were communicated to players so the technical response and community response stayed aligned.

Outcome

• Evidence: Restoring the world after a hosting fault proved that the offsite backups worked when they were needed.
• Operational learning: The incident showed which information matters under pressure: scoped access, readable logs, a known-good backup, and regular updates to players.
• Current status: Niko’s Nook remains active, with a 200+ member community, nine moderators, and a live map at map.nikosnook.net.