The Hardcore Minecraft Network Complete Player Guide

The Hardcore Minecraft Network is a custom Hard-mode survival experience built around one idea: a life should be more than a number. Every survivor receives two named Threads, every serious loss becomes part of a permanent record, and every recovery has a visible cost. The world remembers what happened, who survived it, and how they returned.

Two Threads. No stockpile. No paid escape hatch. Prepare carefully, choose your risks, and leave a Chronicle worth reading.

Important: this guide replaces the Network's retired life-parts, automatic death-ban, and purchasable-extra-life rules. The current system is The Last Thread. When a value is adjusted during development, the verified in-game rules and live Network pages take priority over older screenshots, videos, or posts.

What kind of server is this?

The Hardcore Minecraft Network is not vanilla one-death Hardcore and it is not a casual survival server wearing a red heart as a costume. It is a persistent Java Edition survival network where death, recovery, cooperation, competition, and seasonal history are connected by one authoritative ruleset.

The world runs on Hard difficulty with PvP enabled under the Network's combat law.
Every player begins with two usable Threads, which is also the normal maximum.
The first death is The Breaking. The second is The Falling.
Contracts, Threats, Covenants, rescues, Shattered Realms, Milestones, Scars, revivals, and seasons all feed the same player history.
The website publishes server-verified records without exposing private orders, active coordinates, secret solutions, Covenant vault balances, or private Last Wills.
Paid ranks support identity and presentation. They do not improve survival odds.

Ordinary survival remains the foundation. You are not required to treat every Contract, Threat, or Realm as a daily chore. These systems are invitations to accept additional danger when you are prepared for it.

Current access status and how to join

The public survival server is currently whitelisted while active development and launch testing continue. The connection address is:

play.hardcoreminecraft.net

Create an account on hardcoreminecraft.net.
While the development whitelist is active, review the Development Corps page and apply if you want to test, build, document, or help verify systems.
Use the Minecraft Java Edition account you intend to keep as your Network identity. Do not rotate accounts to bypass restrictions, cooldowns, records, or disciplinary action.
After access is approved, join play.hardcoreminecraft.net. Accept the Network resource-pack prompt for the intended visual presentation.
Generate a Minecraft linking code from your website account and enter /profile link CODE in game.
Confirm your starting state with /hardcorestatus, /lives, and /profile.

If the server reports that you are not whitelisted, your account has not been admitted yet. Repeated join attempts, alternate accounts, or username changes do not accelerate access. Watch the official News page and your Development Corps dashboard for verified updates.

Your first 75 minutes: the Oath

A new seasonal survivor begins as Unblooded. Your two Threads exist, but you have not yet entered ordinary competitive life. The Oath completes after 75 minutes of active online survival.

Use this period to establish food, shelter, basic equipment, safe routes, and trusted contacts.
Ordinary non-consensual PvP is locked while either survivor is still Unblooded.
Logging out does not advance online-only timers.
Once the Oath is complete, your state becomes Two Threads: one active Thread and one reserve Thread.

The Oath is not a tutorial shield against the environment. Mobs, falls, lava, the void, poor preparation, and accepted lethal duels can still end a life. Treat the first night as preparation, not invulnerability.

The Last Thread life model

Every Thread is a named Ledger record with a source, activation history, loss state, and audit trail. The Network does not merely store “2” beside your username and hope every plugin agrees.

Two is the ceiling

Threads cannot be stockpiled. The legitimate paths are deliberately narrow:

Starting Threads: the two records issued when your seasonal life begins.
Soul Trial Reforging: one Pure recovery while on Last Thread, available once per season.
Donor-sacrifice Reclamation: a Fallen survivor returns because another living survivor permanently gives up a reserve Thread.
Verified technical reversal: an exact correction for a documented server or plugin fault.

Threads are not sold, gifted between friends, granted by rank, awarded through promotions, converted directly from Soul Fragments, or handed out as ordinary seasonal prizes. A store purchase cannot rescue a run.

Competitive divisions

Pure: the survivor has progressed only through the allowed Pure rules, including a legitimate Soul Trial.
Reclaimed: the survivor returned through a donor-sacrifice ritual. The return remains part of the permanent record.
Assisted: a technical or administrative intervention changed competitive classification.

These divisions preserve context. A Reclaimed or Assisted story still matters, but unlike records are not presented as identical achievements.

Death one: The Breaking

Your first death consumes the active Thread and moves you to Last Thread. It also creates immediate physical and economic consequences.

Soul Fragment loss: forty percent of carried fragments are affected. Twenty percent are destroyed and twenty percent are placed in the Death Cache.
Death Cache: the cache is owner-only for 30 minutes, accessible to the owner's Covenant until 60 minutes, public after 90 minutes, and decays after 24 hours.
Broken Wound: six hours of online recovery at 16 maximum health with half natural regeneration.
Offline time does not heal the Wound. You must survive while carrying the consequence.
Chronicle entry: the Breaking, its cause, and later corrections are recorded.

Death coordinates are not automatically turned into public live intelligence. Public records are delayed or privacy-filtered so the Chronicle can preserve history without becoming a map to active recovery.

Totems are not extra Threads

A Totem of Undying may prevent a fatal event, but repeated activations are tracked against the current active Thread. The second successful activation creates a four-hour online Totem Burn that disables absorption. A third activation on the same Thread is suppressed. Totems can buy a moment; they cannot create endless immunity or replace the life system.

Death two: The Falling

If you die while no reserve Thread remains, you become Fallen. Normal survival access ends, your Estate enters a protected transition, and a seven-day revival window begins.

Your final death remains in the Chronicle.
Estate, memorial, Death Cache, and Last Will systems begin their own controlled lifecycles.
You cannot erase the event by changing accounts, unlinking a profile, refunding a purchase, or asking another player to transfer a normal Thread.
If the revival window closes without a valid Reclamation, the seasonal state becomes terminal.

The Falling is meant to hurt, but it is not meant to become a support-ticket lottery. Recovery rules are published, bounded, and checked by the server.

Recovery path one: the Soul Trial

A Pure survivor on Last Thread may attempt one Soul Trial per season. Bloodbound survivors are not eligible. Begin or inspect the Trial with:

/soultrial begin
/soultrial status

The Trial follows six Seals: Endurance, Blood, Realm, Defiance, Fellowship, and Sacrifice. It combines long-form survival with meaningful combat, Realm, social, and sacrifice requirements rather than a simple currency exchange.

The Sacrifice offering requires 32 Soul Fragments and one Nether Star.
A marked Trial relic must be carried through a Hard-or-higher Shattered Realm.
When all Seals hold, the survivor must complete the solo Reforging finale.
Death can end the active Trial. Use /soultrial status rather than assuming progress survived a failure.

A successful Reforging restores one reserve Thread and changes the state to Reforged without leaving the Pure division.

Recovery path two: Reclamation

A Fallen survivor may return through a public, server-tracked ritual while the seven-day window is open. Reclamation is not a paid revive and it is not a command that silently moves a number.

Four to eight participants defend the ritual.
One eligible living donor permanently sacrifices a reserve Thread.
The Covenant provides a major Soul Fragment offering and ritual materials.
The altar must survive six escalating waves.
The ritual is durable across ordinary restarts and records its outcome.

Use /revive info, /revive status, and the other /revive subcommands for the current requirements. A successful return is classified as Reclaimed and leaves visible Covenant Soul Debt. The cost is part of the story and cannot be bought away.

Recovery path three: verified correction

When a confirmed server fault consumes the wrong Thread, staff may append a technical reversal. A correction identifies the exact death and reason, restores only the state justified by evidence, and preserves the original record with a visible correction.

Lag, regret, an ordinary disconnect, losing a fair fight, or failing to understand a mechanic does not automatically qualify. Report suspected faults promptly with time, location, screenshots, video, and any relevant messages. Never reproduce a destructive bug after you have enough evidence to report it.

PvP, duels, Bloodbound crime, and combat logging

PvP is enabled, but it has context. The Network distinguishes consent, protected new players, declared danger, and unlawful killing.

Oath protection: ordinary PvP is blocked until both survivors complete the Oath.
Lethal duels: use /duel challenge PLAYER. The other player must explicitly accept. Duel deaths still consume Threads.
Blood Zones: when announced, these are lawful high-risk PvP areas with their own public context.
Murder: an unlawful kill outside a duel or Blood Zone marks the killer Bloodbound, creates a fragment bounty, and adds an online-time consequence. Repeated murders increase the burden.
Soul Trial restriction: Bloodbound survivors cannot enter the Pure Soul Trial until the condition clears.

The 30-second combat tag

Damaging another survivor starts a 30-second combat tag. Logging out while tagged does not make you vanish safely. The server leaves a durable combat body carrying your inventory and health state.

If you reconnect while the body survives, it is removed and your inventory is restored.
If the body is killed, its inventory drops and the death is processed against your real Thread.
Using crashes, forced disconnects, alternate accounts, or network manipulation to escape combat is prohibited.

Check your tag with /combat status. Finish the fight, escape legitimately, or survive until the tag expires.

Soul Fragments: the risk currency

Soul Fragments connect the Network's high-risk systems, but they do not automatically become lives. Direct fragment-to-Thread conversion is disabled.

Fragments are used for systems such as:

Soul Trial sacrifice and recovery progression.
Covenant creation, territorial expansion, rescues, and shared offerings.
Shattered Realm entry costs.
Reclamation rituals and other published survival commitments.

Fragments can be earned through verified Contracts, Threat contribution, Realm outcomes, and other gameplay. Participation checks exist to reject idle attendance, repetitive pair farming, kill trading, and duplicate delivery. Carrying fragments is a risk because The Breaking can destroy or cache part of them.

Hardcore Contracts

Contracts are opt-in assignments with stated objectives, time limits, failure conditions, and bounded rewards. They are designed to create stories, not to manufacture a compulsory login checklist.

You may hold two personal Contracts at once.
Rotations can include daily, weekly, seasonal, survivor, hunter, rescue, delver, event, executioner, and Realm-related work.
Contracts may be solo, party-based, or support either format.
Death, prohibited equipment, abandonment, failed escort conditions, or expiration can fail an assignment.
Presence alone is not contribution. Damage, defense, delivery, rescue, travel, survival, and objective work are verified according to the Contract.
Failed and expired assignments remain part of the record rather than disappearing.

Start with /contracts available, inspect a Contract with /contracts details, and review your commitments with /contracts active. Track only risks you are actually prepared to finish.

World Pressure and the Threat Director

World Pressure is the public 0–100 signal showing how hard the world is leaning against its survivors. It responds to verified seasonal progression and recent outcomes. It does not secretly remove Threads or create unavoidable invisible damage.

The current Threat family includes:

The Long Night, where sleep is denied and the darkness fights back.
Grave Tide, which pushes waves of the dead into the world.
Ashfall, which strains growth and brings environmental danger.
The Hunt, a contribution-tracked pursuit of a marked beast.
Red Moon, which strengthens hostile creatures and raises the stakes.
Death's Silence, where natural regeneration is suspended.

Threats use public warning phases, objectives, and outcome records. Exact hidden schedules, live boss coordinates, encounter seeds, and private scouting data are not published.

Use /threat current to inspect the active event.
Use /threat join to register for contribution and eligible rewards.
Rewards are based on meaningful participation, not only the final hit.
Threat outcomes can affect seasonal pressure, Contracts, Scars, reputation, and the Chronicle.

Shattered Realms

Shattered Realms are isolated, mechanic-driven endgame raids for one to six players. Each fireteam receives its own clean, version-locked world rather than entering a shared dungeon already stripped by another group.

The six Realm families are The Drowned Vault, The Hollow Keep, Ember Mines, The Rotting Cathedral, The Crystal Maw, and The King's Tomb. They use symbols, relics, plates, temporary roles, split routes, damage windows, enrages, boss mechanics, secrets, and a final extraction.

Before launch

Every participant must have a linked website identity.
Fireteams support solo play through six-player groups.
The leader selects the Realm and every member confirms readiness.
Scaling, roster, and template version lock when the deployment begins.
Current entry costs are based on difficulty: Hard, Extreme, and Mythic Realms require progressively larger fragment commitments.

Inside a Realm

Building, breaking, portals, and unapproved teleportation are disabled.
Deaths consume real Threads. A Realm is not a consequence-free minigame.
Encounter revive tokens can restore a downed teammate inside the run, but they never restore a consumed Thread.
Disconnect protection preserves a slot briefly and may leave a combat body.
Eligible runs can resume from signed checkpoints before their recovery window expires.
Secrets and active objectives remain private to the fireteam.

Extraction is the completion

Killing the final boss is not enough. Loot moves through unsecured, carried, cached, secured, and claimed states. The fireteam must physically extract before the Realm collapses. Unsecured rewards may be lost on failure, while successful delivery is recorded exactly once.

Use /shattered list, /shattered details, and /shattered fireteam to begin. The compatibility command /expedition may also expose familiar fireteam and session actions.

Covenants, claims, and rescues

Covenants are seasonal survival communities, not unrestricted factions. They coordinate territory, shared fragment vaults, rescue beacons, Contracts, revival altars, memorials, reputation, and seasonal legacy.

Creating a Covenant

A formation requires three founders, a charter, and 24 Soul Fragments.
A new Covenant waits through its formation period before claiming territory.
A player belongs to only one Covenant in the season.
Every public rank follows the same 16-member maximum.
Roles govern invitations, membership, vault withdrawals, claims, rituals, and succession.

Territory

Claims are available in the normal overworld, must remain connected, respect protected WorldGuard regions, and use a capacity that grows through membership and Covenant reputation up to a 64-chunk seasonal ceiling.

Claim costs rise in published tiers as territory grows.
Removing a chunk cannot split the remaining territory into disconnected islands.
Hoppers, pistons, fluids, explosions, and other mechanics are checked at borders so protection cannot be bypassed from outside.
Boundary titles and particles identify when you enter or leave Covenant territory.

Claim flags and trust

For public-access flags, true generally means the action is publicly allowed, while false means trust is required or the environmental action is blocked. Core protections cover building, breaking, containers, switches and doors, redstone, explosions, fire, fluids, entities, vehicles, teleportation, and related interactions.

/covenant claimflag FLAG VALUE updates every active claim owned by the Covenant and becomes the default for future claims.
/covenant claimflagid CLAIM-ID FLAG VALUE is the deliberate single-claim exception.
/covenant trust, /covenant untrust, and /covenant trustlist manage visitor, access, container, build, and manager-level permission.
PvP remains governed by the Network combat law; a claim setting is not permission to evade Oath protection, duels, Bloodbound consequences, or combat tags.

Rescue beacons

A survivor in danger can create a privacy-safe rescue request. The public listing gives an approximate region, while exact coordinates are disclosed only to accepted rescuers.

The request has a fragment cost, expiration, and personal cooldown.
Only a small accepted rescue team receives the private destination.
Completion requires a real escort over distance and time, not touching the requester for an instant.
Requester death, abandonment, logout beyond grace, or pair farming can invalidate the rescue.

Use /rescue request, /rescue list, /rescue accept, and /rescue status.

Seasons and permanent Legacy

The Network is structured around a public seasonal rules clock rather than silent difficulty changes. The planned twelve-week arc moves through five acts:

The Awakening: opening survival, Oaths, and lower Pressure.
The Hunger: scarcity, Contract escalation, and Covenant formation.
The Red Age: mature PvP law, severe Threats, and Realm pressure.
The Collapse: claim strain, harder encounters, and Legacy races.
The Last Week: final records, ending conditions, and archive preparation.

The live Season page is the authority for the current day, act, public escalation, and verified archives. When a season closes, leaderboards freeze by division, Covenant and world records are archived, Legacy records and Crests are generated, and only explicitly seasonal state is reset. The Chronicle does not forget the previous world.

Milestones, Scars, Last Wills, memorials, and the Chronicle

Power is temporary. The record is permanent.

Milestones: one-time progression, discoveries, lore, titles, cosmetics, and Legacy. They do not grant Threads, combat power, claim capacity, protected extraction, or leaderboard score.
Wounds: temporary mechanical consequences that heal through online survival.
Scars: permanent identity records with no mechanical power. They show what a survivor endured.
Last Wills: private-by-default instructions for an eligible beneficiary, message, protected item, fragments, Covenant contribution, memorial choice, and public privacy state.
Memorials and Estates: controlled records and world transitions following the Falling.
The Chronicle: the public, privacy-safe history of Breakings, Fallings, rescues, revivals, Reclamations, corrections, succession, Threats, Realms, and season archives.

Use /milestones, /scars, /lastwill, and /soulledger to review your own records. Visit the Chronicle to see what the Network has published.

Profiles and the website

A linked player profile joins trusted server data with player-controlled presentation.

Server-verified rank, survival state, division, Threads, deaths, play history, Milestones, Scars, titles, achievements, and selected statistics.
Player-authored biography, motto, profile theme, banner, avatar, featured achievement, and statistic showcase.
Separate privacy controls for public profile visibility, online state, last seen, statistics, and achievements.
Private order history visible only to the authenticated linked account.

Live pages label records as verified, stale, delayed, private, or unavailable. If the server has not published a record, the website shows an honest empty state rather than inventing data. Exact active raid coordinates, hidden Threat schedules, Covenant vault balances, private Wills, recovery intelligence, and payment information are never public profile content.

Fair Survival store policy

The Network storefront offers recognition and cosmetic identity through ranks such as Supporter, Vanguard, Warden, Titan, Mythic, and Ascendant. Monthly and lifetime presentation options may exist, but every tier follows the same survival constitution.

Paid products may provide chat and tab identity, Discord recognition, profile presentation, titles, particles, emotes, memorial styles, or other cosmetic and social features. They cannot provide:

Threads or Soul Fragments.
Health, damage, protection, inventory, or safe extraction.
Teleport power that bypasses survival rules.
Covenant member or claim capacity.
Extra Contract slots, Realm access, or revival priority.
Leaderboard or seasonal score.

Your payment cannot save your life. Support may change how your story is presented, never whether you survive it.

Network conduct rules

The mechanical rules create consequences, but they do not replace community standards. The following rules apply across Minecraft, the website, linked Discord spaces, applications, and Network-operated services.

1. Play fairly

Do not use hacked clients, X-ray or cave-finding tools, prohibited minimap intelligence, packet manipulation, reach or combat assistance, movement cheats, duplication, inventory manipulation, unauthorized macros, bots, or automation that plays the game for you. Cosmetic, accessibility, and performance tools are acceptable only when they do not reveal hidden information or automate competitive actions.

2. A bug is not permission

Do not exploit duplication, reward loops, claim bypasses, invulnerability, desynchronization, payment faults, race conditions, disconnect behavior, or any mechanic that clearly produces unintended advantage. Stop once you have enough evidence and report it privately. Publicly teaching an active exploit or continuing to benefit from it can be treated as deliberate abuse.

3. Do not bypass identity or consequences

Alternate accounts, account sharing, username changes, unlinking, VPN use, or household accounts may not be used to evade bans, death states, Bloodbound status, cooldowns, Contract limits, rescue safeguards, Covenant limits, store restrictions, or leaderboard classification. Ban evasion and punishment evasion can extend action to connected accounts.

4. Respect other people

Harassment, hate speech, slurs, sexual harassment, threats, stalking, doxxing, malicious impersonation, targeted humiliation, spam, and repeated unwanted contact are prohibited. Conflict inside the game does not authorize abuse outside it.

5. Respect claims and world boundaries

Do not bypass Covenant protection with fluids, pistons, hoppers, explosions, projectiles, entities, alternate accounts, teleportation, or external tools. Unclaimed land is not permission for targeted harassment, repeated destruction with no gameplay purpose, or attempts to make another player unable to participate.

6. Follow combat law

Do not combat-log, kill trade, stage bounties, farm alternate accounts, bait protected new players, trap players through an exploit, or coordinate fake duels to manipulate records. Lawful PvP remains lethal; unlawful manipulation remains punishable even when the server technically allowed an action.

7. Do not manipulate progression

Contract boosting, idle Threat registration, rescue pair farming, staged Realm records, artificial Covenant reputation, repeated reward handoffs, leaderboard collusion, and other fake contribution are prohibited. Rewards and records may be removed when the underlying participation was not legitimate.

8. No scams or unauthorized trading

Do not impersonate staff, fake giveaways, distribute malicious links, steal accounts, sell Network access, or conduct unauthorized real-money trades for in-game items, Threads, fragments, ranks, accounts, or services. Use only the official storefront for published Network products.

9. Protect private and unreleased information

Do not leak private coordinates, exploit reports, staff messages, development files, credentials, unreleased maps, raid solutions, private test footage, or another player's personal information. Development participants must follow the stricter boundaries attached to their assignments.

10. Corrections preserve history

Staff may reverse illegitimate rewards, restore verified losses, remove fraudulent records, roll back exploit effects, hide abusive public content, or restrict access. Corrections are based on evidence and audit history; they do not silently rewrite legitimate outcomes. Penalties can include warnings, record removal, temporary restrictions, account unlinking, or permanent removal depending on severity and repetition.

Player command starter kit

Use /help for the commands currently available to your rank and context. The Network hides commands you cannot use, so tab completion is not a promise of permission.

/hardcorestatus: current state, division, Oath, and competitive standing.
/lives, /lives history, /soulledger: Threads, fragments, and Ledger history.
/profile, /profile link CODE, /titles, /scars, /milestones: identity and permanent progression.
/contracts: browse, accept, track, and review Contracts.
/threat current, /threat join: inspect and register for Threats.
/covenant, /rescue: community, territory, trust, vault, and rescue tools.
/shattered or /expedition: Realm fireteams, readiness, launches, checkpoints, and extraction.
/duel, /combat status: lawful PvP consent and combat-tag state.
/soultrial, /revive: the two legitimate gameplay recovery paths.
/lastwill: beneficiary, message, fragments, protected item, Covenant contribution, memorial, and privacy.

What to expect during development

The whitelist remains active because the Network is still being tested as one connected machine. A command existing does not automatically mean every content path is final.

Realm encounters, Threat pacing, Milestone targets, Covenant values, rewards, and performance limits may be tuned from verified play data.
Development worlds, inventories, temporary records, builds, or statistics may be reset when a test requires it.
Systems can be paused when live data, migrations, or recovery safeguards are not healthy.
Public pages may briefly show delayed or unavailable data rather than publishing an unverified guess.
Major rule changes will be published. The Network will not quietly turn a cosmetic purchase into survival power or erase a legitimate death to simplify operations.

Development Corps participants are expected to report repeatable evidence, keep unreleased information private, remain inside assigned boundaries, and understand that temporary access is not a promise of staff status or permanent whitelist access.

Your first-session checklist

Read this guide and the live Last Thread rules page.
Join with the correct Minecraft identity and link your website account.
Check /hardcorestatus and /lives.
Use the Unblooded period to establish shelter, food, equipment, and an exit route.
Do not carry every Soul Fragment you own into avoidable danger.
Learn the combat tag before engaging another player.
Inspect a Contract or Threat before joining it.
Do not enter a Shattered Realm until every participant understands that deaths consume real Threads and loot is not secure until extraction.
Join or form a Covenant only when you understand its roles, shared vault, claims, and responsibilities.
Set a Last Will before the world makes the decision urgent.

You enter with two Threads. The first death breaks the run. The second ends it. Enter prepared. Leave a Chronicle.