The Hardcore Network Development Changelog

The Hardcore Network has changed far beyond a visual refresh. We have rebuilt the public website, storefront, player accounts, server integration, and the foundation of the Hardcore experience around one goal: every life should matter, and every player should leave a history behind.

This is the foundation for a persistent Hardcore network where survival, loss, recovery, and legacy are all part of the same story.

How to read this development changelog

This update covers a mixture of public features, production foundations, and systems that are still being expanded. We want to be direct about that distinction.

Live: available on the public website now and backed by production data.
Integration testing: implemented across the website, database, or Paper plugin, but still being verified under real gameplay conditions.
Planned expansion: the foundation exists, but the full content, balance, interface, or automation is still ahead.

A database table, command, or public page is not the same thing as a feature-complete gameplay system. Feature complete means the system is understandable to a new player, safe under failure, balanced for the wider server, visible in the correct interfaces, and supported by staff tools.

A completely new home for the Network

The website has been redesigned from the ground up with a new identity, a clearer presentation of how the server works, and a direct path for new players who want to understand the experience before joining.

A rebuilt homepage with live Network information, player records, featured profiles, development status, and a prominent server address.
A dedicated Network directory explaining the major gameplay systems.
Public news, player directories, profiles, leaderboards, Chronicles, Threats, expeditions, Contracts, Covenants, revivals, seasons, and Hall of the Fallen pages.
The official connection address is now presented consistently as play.hardcoreminecraft.net.
Expanded Terms of Service and Privacy Policy pages covering accounts, purchases, game services, and player data.

Planned website expansion

Deeper live integrations for Threat objectives, expedition rotations, Contract progress, Covenant activity, revivals, and season history.
Clearer status language showing which systems are live, in testing, temporarily unavailable, or planned.
More complete empty states and onboarding for visitors arriving before public access.
Focused system guides explaining lives, Pure and Assisted competition, revivals, store delivery, ranks, and seasonal progression.
Continued accessibility, mobile layout, performance, and privacy improvements across every public page.

A real Minecraft server storefront

The store is no longer a collection of disconnected purchase links. It now works as a complete basket and checkout experience built for Minecraft players.

Stripe-hosted checkout through the Network payment domain.
A persistent basket with quantities, multiple products, coupon codes, discounts, and Minecraft username validation.
A commerce model for one-time items, monthly subscriptions, lifetime ranks, renewals, cancellations, refunds, disputes, and failed payments.
Rank products for Supporter, Vanguard, Warden, Titan, Mythic, and Ascendant, with permanent and monthly options presented together.
Extra Lives and other server entitlements are recorded individually instead of being treated as an anonymous command.
Private order history now shows payment, queue, fulfillment, refund, and review states.

Store purchases are queued for the Paper plugin to process safely. The website no longer needs direct remote-console access to deliver purchases. Fulfillment is allowlisted, recorded, and designed to prevent the same order from being applied twice.

What comes next for the store

Publish final in-game perks only after each permission and benefit is configured and tested.
Make upgrades and downgrades entitlement-aware so rank changes replace the correct permission state instead of stacking conflicting groups.
Complete monthly-rank lifecycle behavior for renewals, failed payments, cancellations, and end-of-term access removal.
Add clearer delivery receipts showing exactly which entitlements were applied and when.
Expand reconciliation for partial refunds, disputes, reversed lives, failed fulfillment, and orders requiring staff review.
Review every product against Pure and Assisted rules before public launch.

Player accounts and public profiles

Players can create a website account, link it to their Minecraft identity with an in-game code, and build a profile around trusted server data.

Secure Minecraft profile linking from the website to the Paper server.
Server-verified statistics, achievements, play history, current lives, rank, survival status, and activity.
Private purchase history visible only to the account owner.
Profile customization with themes, accent colors, banners, layouts, avatar styles, biographies, featured statistics, and privacy controls.
Public profile and player directory pages that respect each player's visibility settings.
Current bans and life totals synchronized from authoritative server systems.

What comes next for profiles

Broaden achievements with survival, exploration, social, Contract, Threat, expedition, revival, and seasonal families.
Add clearer progress for achievements that are not yet unlocked.
Expose more Ledger history, Scars, Chronicle milestones, Covenant contributions, and Legacy records without exposing private data.
Improve synchronization freshness indicators so players know when each record last came from Paper.
Add showcases for rare achievements, notable deaths, Legacy Crests, and endgame objectives.
Expand field-level privacy for online status, statistics, achievements, death details, and historical records.

Ranks now match Minecraft

Website rank badges mirror the LuckPerms prefixes used in game. Survivor, Supporter, Vanguard, Warden, Titan, Mythic, Ascendant, and Owner retain their symbols, brackets, colors, and bold lettering. Ascendant and Owner preserve their individually colored letters instead of using a generic gradient.

LuckPerms remains the source of truth. When a linked player's rank changes in Minecraft, the website profile follows it.

Rank perks are the next major milestone

The rank identities and store options exist, but final benefit packages will not be invented before the server configuration is ready. Each package will be published after its LuckPerms permissions, gameplay behavior, subscription behavior, and Hardcore impact are verified.

Future rank work includes cleaner upgrade paths, expiry handling for monthly access, public comparison tables, and a firm separation between cosmetic or convenience benefits and anything that affects competitive records.

The Soul Ledger

The new HardcoreNetwork Paper plugin introduces the Soul Ledger as the persistent authority for player lives. Lives are no longer represented by only a number. Every life receives its own record, source, acquisition history, loss state, and audit trail.

Starting, earned, gifted, revived, purchased, promotional, administrative, and rank-provided lives can be distinguished.
Life grants and reversals are repeat-safe and traceable.
Deaths consume a specific active life and enter the player's Chronicle.
Permanent death is recorded when the Ledger reaches zero.
Purchased or administratively supplied help moves a season record into the Assisted class.

What the Soul Ledger still needs

Live testing against every real death cause, restart, disconnect, rollback, and life-changing command.
Reconciliation between the Ledger and the visible Hardcore life display so neither can silently drift.
Final rules for life caps, rank-provided lives, promotional grants, gifts, seasonal resets, and staff corrections.
Better in-game Ledger presentation with pagination, source explanations, loss details, and staff-only context.
Alerts when an entitlement, death, or reversal cannot be mirrored to the visible life state.
Correction tools that never rewrite history silently.

Pure and Assisted Hardcore

Competitive records are divided into two transparent classifications. Pure survivors progress without purchased, promotional, or administrative life assistance. Assisted survivors can still compete and build a legacy, but their records remain in a separate division.

This separation allows the store to support the Network without weakening the meaning of a Pure Hardcore achievement.

Planned classification rules

Before public competition, every life source and recovery mechanic will receive an explicit Pure or Assisted ruling. The website will explain the trigger without exposing private order information. Once a season becomes Assisted, a refund, profile setting, or ordinary correction will not erase that competitive history.

Leaderboards will remain separated, and future seasonal rewards can use classification-aware eligibility instead of treating every record as directly comparable.

The Chronicle of the Fallen

Deaths are becoming permanent pieces of Network history. The Chronicle records the player, season, classification, final life, survival time, cause, dimension, biome, general region, rank, and any public final message.

A live death feed and detailed obituary pages.
A public Hall of the Fallen.
An in-game /hardcore fallen record for recent permanent deaths.
Last Will privacy choices for public obituaries and coordinate disclosure.

Planned Chronicle expansion

Capture named hostile mobs, bosses, active Threats, expeditions, Contracts, Covenants, achievements, and Scars related to a death.
Improve inventory snapshots and estimated value without turning obituaries into raw data dumps.
Add filters for season, classification, cause, dimension, notable records, and staff curation.
Create richer memorials for historically important players.
Add correction tools that preserve the original record and reason for correction.
Connect permanent deaths to Last Wills, Covenant history, rescue attempts, and revival eligibility.

Revival Rituals, Scars, and Last Wills

Death is serious, but the story does not always end immediately.

Revival Rituals require an altar, activation item, life fragments, multiple defenders, and a donated life.
Rituals run through hostile waves and can fail.
Successful revivals record the returned player, primary reviver, participants, and donated life.
Near-death events can become permanent Scars.
Last Wills can preserve a final message, beneficiary, memorial preferences, and death privacy choices.

Planned ritual, Scar, and Last Will expansion

Scale revival waves by participants, season age, target history, and donated-life strength.
Add cooldowns, preparation guidance, protected failure recovery, and anti-exploit rules.
Create ritual variations without allowing a risk-free revival route.
Expand Scars into a curated catalog with triggers, rarity, descriptions, visibility, and achievement relationships.
Complete Last Will transfers for fragments, Covenant donations, memorial choices, and eligible non-life possessions.
Build staff resolution for invalid beneficiaries, missing Covenants, or state changes during execution.
Add a public revival feed while keeping private Will choices private.

The Threat Director

World Threats are modular server events. The initial set includes The Long Night, Grave Tide, Ashfall, The Hunt, Red Moon, and Death's Silence.

The Hunt tracks its marked beast, player damage contribution, eligible participants, fragments, seasonal score, and completion when the beast is slain. Duplicate event types are blocked, abandoned beasts are cleaned up, and Threat creatures use safe-ground searches to avoid terrain, hazards, and suffocation.

The full Threat Director vision

Evaluate deaths, population, remaining lives, season age, boss defeats, fragments, participation, performance, and cooldowns.
Use warning phases and escalating announcements without publishing exploit-friendly exact coordinates.
Track damage, defense, survival, objectives, support actions, and event duration instead of only a final hit.
Add Contract progress, seasonal score, rare materials, Chronicle recognition, and Covenant participation.
Make every Threat mechanically distinct rather than relying only on global potion effects.
Add world and region rules, restart cleanup, performance budgets, spawn limits, and staff overrides.
Publish clearer objectives, outcomes, and participant recognition on the website.

Contracts and the Shattered Realms

Contracts are intended to provide meaningful objectives instead of empty grind counters. The foundation stores definitions, assignments, progress, completion, expiry, and seasonal rewards.

The Shattered Realms framework introduces managed adventures with time limits, party records, bosses, extraction, secured and unsecured rewards, failure recovery, and seasonal statistics. Initial definitions include the Drowned Vault, Hollow Keep, Ember Mines, Rotting Cathedral, Crystal Maw, and King's Tomb.

Planned Contract incorporation

Daily, weekly, seasonal, Covenant, rescue, Threat, and expedition rotations.
Multi-stage objectives responding to meaningful events.
Party contribution, abandonment, expiry, and repeat-safe rewards.
Contract boards in game and online with progress, remaining time, requirements, and rewards.
Difficulty and reward balancing based on season data.
Special Contracts involving low-life rescues, cursed items, bosses, Threats, and full-party survival.

Planned Shattered Realms incorporation

Complete encounter design, objectives, boss behavior, extraction, rewards, and failure states for each Realm.
Party formation, readiness checks, capacity limits, reconnect handling, and abandoned-session recovery.
Strict separation between secured rewards and items lost before extraction.
Rotations, difficulty tiers, optional challenges, time records, flawless completion, and seasonal achievements.
Inventory and location recovery that remains safe across crashes and restarts.
Public rotations, recent clears, party records, and leaderboard categories.

Covenants and settlements

Covenants give survivors a persistent group identity. The foundation supports creation, invitations, membership, roles, reputation, shared fragments, logs, and recorded disbanding.

Planned Covenant incorporation

Granular permissions for invitations, members, vault activity, Contracts, settlement settings, and public profiles.
Shared Contracts, Threat participation, expedition parties, rescues, seasonal score, and reputation.
Settlement identity with banners, descriptions, privacy, memorials, and controlled territory integration.
Transactional vault withdrawals, contribution history, limits, recovery, and duplicate-deduction protection.
Public profiles, members, activity history, seasonal rankings, and archived legacies.
Moderation for abusive names, abandoned ownership, disputed vault activity, and mistaken disbanding.

Seasons, current rankings, and permanent legacy

The public leaderboard opens on the active season automatically. Players can switch between Pure and Assisted divisions, compare seasonal records, browse previous seasons, or return to lifetime statistics.

The active season is the default current leaderboard.
When a season changes, the leaderboard follows the new one automatically.
Previous seasons remain available through the archive selector.
Season rollover includes a protected dry run.
Season summaries and Legacy Crests preserve long-term accomplishments.

What a complete season transition will include

A dry run showing which records archive, reset, carry forward, or require attention.
Protected confirmation, database backup, maintenance state, audit record, and recovery path.
Final snapshots for leaderboards, classifications, Ledgers, Chronicles, Covenants, Contracts, expeditions, Threats, and rewards.
Automatic activation of the new leaderboard while the previous season remains viewable.
Legacy Crest calculation, cosmetic delivery, profile display, and historical season pages.
Explicit reset rules for inventories, economy, lives, temporary Contracts, settlements, active Threats, and expeditions.

Operations and reliability

The rebuilt staff command center brings together Ledger lookup, audited life grants, Threat control, Contract availability, Chronicle curation, failed Last Will recovery, service health, migrations, and audit activity.

The system uses versioned migrations, transactional gameplay writes, duplicate-delivery protection, restart recovery, private administrative access, and separation between public and account-only records.

Planned operations expansion

Player reconciliation showing visible Hardcore state beside authoritative Ledger state.
Dedicated views for revival failures, Will transfers, expedition recovery, Threat participation, Covenant moderation, and season readiness.
Payment reconciliation connecting checkout, order, fulfillment, entitlement, life record, and reversal in one timeline.
Alerts for queue age, stale synchronization, failed background work, health, migrations, and cache status.
Correction workflows requiring a reason, previewing the effect, and preserving original values.
Operational documentation for backups, restoration, rollovers, payments, fulfillment, and plugin recovery.

Where the Network stands today

The server remains whitelisted because it is still in active development. The website and underlying systems are taking their production shape, while gameplay balance, rank perks, content configuration, and live event tuning continue.

That whitelist is not a mystery or marketing timer. It exists because we are building and testing the systems that will define every future life on the Network.

The planned development path

Remaining work is organized by dependency and risk instead of announcing dates before the systems are ready.

Phase one: authoritative survival

First comes reliability for the Soul Ledger, death processing, classification, store fulfillment, profile linking, LuckPerms ranks, and restart recovery. A Hardcore network cannot build on uncertain life data.

Phase two: visible player history

Chronicles, Scars, achievements, Last Wills, profiles, privacy, the Hall of the Fallen, seasonal rankings, and correction tools will grow until a player's history is understandable in game and online.

Phase three: meaningful shared systems

Contracts, rescues, Revival Rituals, Covenants, Threat participation, shared progression, and rank perks will move from foundations into balanced loops with complete interfaces and reward rules.

Phase four: endgame and seasonal depth

The Shattered Realms, advanced Threats, Covenant competition, seasonal objectives, Legacy Crests, archived histories, and protected rollover will form the long-term structure.

Phase five: public access readiness

Before the whitelist is lifted, core systems will be load-tested, failure-tested, documented, balanced, and reviewed as one connected experience. Public access depends on readiness, not on whether a single page or command exists.

What we will not rush

Rank perks will not be called final before their permissions and competitive impact are known.
Purchased help will not be mixed invisibly into Pure competition.
Season rollover will not run without a dry run, audit trail, backup, and recovery plan.
Revival, Last Will, and store operations will not silently consume lives, fragments, or payments when a later step fails.
Expeditions and Threats will not be called complete simply because a boss can spawn.
Private orders, Wills, and account information will not become public profile content.

Two lives. One story. A permanent record of what happens next.

Watch the news page for focused previews, testing announcements, rank perk details, and the path toward public access. When the gates open, connect with play.hardcoreminecraft.net.