Break the right things.
Use repeatable steps, expected and actual results, timestamps, screenshots or logs, severity, affected player state, and retest notes. Responsible exploit reports are private and never used for advantage.
Development Corps · Live program
Build the systems
survival depends on.
The Network is an interconnected hardcore platform: lives, seasons, raids, Covenants, world threats, public records, and secure website actions all have to agree. Selected participants help us find where that agreement breaks—and make the finished experience stronger.
01 / Mission
Not an early-access queue
Contribute with
evidence and intent.
Development Corps members receive bounded assignments. Testers reproduce failures and prove fixes. Builders work from controlled briefs. Every accepted contribution is reviewed, attributed, and retained in the program ledger.
Create places with rules.
Produce terrain, structures, arenas, raid rooms, rally spaces, encounters, puzzles, lore, and traversal under palette, performance, safety, boundary, and revision requirements.
02 / Current systems
What the Corps can work on
One platform.
Many failure boundaries.
Assignments open only when the relevant environment and reviewer are available. Applicants choose interests; staff grants the actual scope.
Last Thread
Validate two-Thread life state, Wounds, final-death restrictions, Soul Trials, donor revivals, Chronicle records, and failure recovery without bypassing the authoritative ledger.
Shattered Realms
Build and verify immutable raid templates, rally checkpoints, encounter gates, scaling, sealed loot, extraction, cleanup, recovery, and competitive run classification.
Covenants
Exercise membership, claims, trust, upkeep, rescues, borders, territory messages, seasonal scoring, and privacy-safe website read models.
Threat Director
Test scheduled world threats, safe spawning, contribution tracking, completion detection, escalation, announcements, and recovery after restarts.
Profiles & Chronicle
Review player records, achievements, quests, Scars, milestones, season history, privacy controls, rankings, and server-signed website freshness.
Store & Reclamation
Test payment-neutral storefront states, eligibility blocking, fulfillment queues, refunds, and Assisted segregation. Testers never receive payment credentials or arbitrary life grants.
03 / Disciplines
Apply where you are useful
Specialists wanted.
You may request several disciplines. Approval is per role, and no technical or building role automatically grants operator, production database, payment, secret, or unrestricted filesystem access.
Server Tester
Gameplay, integration, performance, balance, exploit, and reproduction testing.
World Builder
Complete worlds, terrain, biomes, caves, roads, and large-scale composition.
General Builder
Settlements, structures, roads, bridges, camps, and decorative construction.
Structure Designer
Dungeons, temples, fortresses, trials, arenas, and gameplay structures.
Interior Designer
Functional interiors, lighting, furniture, rooms, and detailed decoration.
Landscape & Terrain Builder
Terraforming, trees, cliffs, caves, paths, blending, and environmental detail.
Dungeon & Expedition Builder
Shattered Realms routes, encounters, puzzles, extraction, and player flow.
Redstone & Technical Builder
Performance-safe mechanisms, traps, puzzles, reset behavior, and documentation.
Event Arena Builder
Threat, PvE, boss, seasonal, tournament, and spectator environments.
Lore & Environmental Designer
Lore locations, memorials, ruins, books, visual storytelling, and continuity.
04 / Access path
Identity first. Least privilege always.
Application to
verified contribution.
- 01
Create one website account
Your application, status history, staff messages, assignments, reports, access grants, and recognition remain attached to a private authenticated account.
- 02
Request temporary Minecraft verification access
Because the server is whitelisted during development, the website first queues short-lived link access. Join
play.hardcoreminecraft.netand run/profile link CODE. The server—not typed text—verifies your UUID. - 03
Connect Discord
Discord OAuth verifies your communication identity, joins the configured server when permitted, and lets the bot synchronize the Development Applicant role and deliver private status messages.
- 04
Submit a focused application
Select disciplines, provide availability, describe useful experience, acknowledge development realities, and include original portfolio evidence when a building discipline requires it.
- 05
Review, information request, or trial
Staff may request clarification, waitlist you, or issue a bounded trial with a brief, deadline, reviewer, allowed tools, and exact acceptance criteria.
- 06
Scoped access and synchronization
Approval queues the Development Participant base group plus only the approved LuckPerms and Discord roles. Expiry, suspension, withdrawal, and revocation remove temporary access without erasing historical contributions.
- 07
Assignment, evidence, retest, acceptance
Work moves through an auditable lifecycle. Reports and builds are not counted merely because they were submitted; a reviewer must accept the outcome.
05 / Operating rules
Unfinished by definition
Know the boundaries.
Instability is expected
- Systems may fail, restart, roll back, or be removed.
- Development inventories, builds, worlds, and statistics may reset.
- Testing results are not production rewards or competitive records.
- Never assume a bug grants permission to use it.
Private work stays private
- Do not leak files, screenshots, credentials, exploits, maps, or unreleased mechanics.
- Do not copy or claim another contributor's work.
- Never test outside the assignment's server, world, account, or time boundary.
- Payment data and production secrets are never tester material.
Safety outranks speed
- Destructive tests require explicit authorization and a recovery plan.
- Coordinate multiplayer, economy, claim, raid, and load tests with staff.
- Do not grant lives, ranks, items, or permissions to simulate a case without the approved fixture.
- Report security issues privately with minimal reproduction.
Access is temporary
- Approval does not promise permanent access or future staff placement.
- Roles are synchronized from recorded program state, not manually accumulated.
- Suspension or revocation must not be bypassed.
- Permanent recognition is separate from temporary access.
06 / Record
Accepted work becomes history
Recognition follows contribution.
Accepted reports, approved builds, verified exploit disclosures, completed testing phases, launch operations, documentation, and sustained responsible participation enter a permanent ledger. Raw report count does not determine quality.
Founding-period recognition✦ FOUNDER ✦
Founder is a permanent, manually approved recognition for meaningful early work in good standing. Applying, receiving a trial, or merely joining does not award it.
The whitelist exists because the Network is still being built
Help make every
future story trustworthy.
Apply only if you are ready to communicate clearly, respect boundaries, accept revision, and leave systems safer than you found them.