Live development participation

Help build what
survival becomes.

Selected players work alongside the Network team on unfinished systems, dangerous experiments, new worlds, dungeons, arenas, and the places future stories will begin.

01 / The work

Test it. Shape it. Build it.

Two disciplines.
One evolving Network.

Testing operations

Break systems responsibly.

Test Hardcore gameplay, contracts, expeditions, revival rituals, world threats, multiplayer behavior, balance, performance, exploits, and website-to-Minecraft integration. Useful reports include repeatable steps, evidence, expected behavior, and actual results.

World production

Create places worth surviving.

Develop terrain, settlements, dungeons, event arenas, interiors, technical puzzles, environmental lore, and adventure routes while following assigned briefs, palettes, boundaries, revision requests, and performance safeguards.

02 / Available roles

Choose where you contribute

Specialists wanted.

Apply for one or more roles. Administrators can approve only the roles that best match your experience and the Network’s current needs.

01Testing

Server Tester

Gameplay, integration, performance, balance, exploit, and reproduction testing.

02Building

World Builder

Complete worlds, terrain, biomes, caves, roads, and large-scale composition.

03Building

General Builder

Settlements, structures, roads, bridges, camps, and decorative construction.

04Building

Structure Designer

Dungeons, temples, fortresses, trials, arenas, and gameplay structures.

05Building

Interior Designer

Functional interiors, lighting, furniture, rooms, and detailed decoration.

06Building

Landscape & Terrain Builder

Terraforming, trees, cliffs, caves, paths, blending, and environmental detail.

07Building

Dungeon & Expedition Builder

Shattered Realms routes, encounters, puzzles, extraction, and player flow.

08Building

Redstone & Technical Builder

Performance-safe mechanisms, traps, puzzles, reset behavior, and documentation.

09Building

Event Arena Builder

Threat, PvE, boss, seasonal, tournament, and spectator environments.

10Building

Lore & Environmental Designer

Lore locations, memorials, ruins, books, visual storytelling, and continuity.

03 / Selection

How participation works

Identity first.
Access last.

  1. 01

    Create your website account

    Your application, private messages, work history, and rewards stay tied to one secure account.

  2. 02

    Verify Minecraft in game

    Enter your Java username. The server plugin prepares short-lived whitelist access so you can join play.hardcoreminecraft.net and run /profile link CODE. Your UUID—not typed text—becomes authoritative, and temporary access is removed after linking or expiry.

  3. 03

    Connect Discord and apply

    Verify your Discord identity through OAuth, select roles, describe your availability and experience, and include meaningful portfolio evidence for building roles. Discord is the program contact channel.

  4. 04

    Review and possible trial

    Staff may request information, waitlist the application, or assign a bounded trial build with a brief, palette, deadline, plot, and reviewer.

  5. 05

    Controlled access

    Approved UUIDs are synchronized to only the assigned development servers, worlds, LuckPerms groups, cohorts, and temporary tools.

04 / Before you apply

Development is unfinished by definition

Read the realities.

Expect instability

  • Servers and features may contain serious bugs.
  • Progress, inventories, worlds, and statistics may reset without notice.
  • Features may change substantially or be removed.
  • Builds may be moved, revised, rebuilt, or removed.

Protect private work

  • Do not distribute unfinished server files, screenshots, systems, or private information.
  • Do not copy, steal, leak, or claim another participant’s work.
  • Do not exploit, cheat, grief, or disrupt development sessions.
  • Technical roles never automatically receive operator or unsafe command access.

Contribute professionally

  • Testers report issues responsibly and with useful evidence.
  • Builders follow briefs, style guides, palettes, boundaries, and revision requests.
  • Participation and development access are never guaranteed permanently.
  • Submitted development work may be incorporated into the Network.

Rewards follow contribution

  • Applications alone do not earn rewards.
  • Quality matters more than raw submission count.
  • Founder recognition requires meaningful founding-period work and approval.
  • Temporary access groups remain separate from permanent badges and history.

05 / Recognition

Leave a permanent mark

Contribution becomes history.

Accepted reports, approved builds, completed testing phases, responsible exploit discoveries, launch work, and staff-recognized contributions enter a permanent participation ledger.

Founding recognition FOUNDER

The Founder badge is permanent recognition for qualifying early participants in good standing. It is never awarded merely for applying.

The Network is currently in development

Your work could become part of
every story that follows.

Address copied