Durability
Durability defines how pickaxe wear, maintenance, repair state, and runtime usage boundaries are interpreted in ore discovery mining across the PVERSE gameplay layer.
Overview
Durability is the gameplay-layer condition system that governs pickaxe wear and maintenance over time. It exists to give tools operational meaning beyond pure ownership by making their continued use depend on managed condition, repair decisions, and runtime state resolution.
This page is descriptive rather than balance-final. It explains what durability means, where it applies, how repair and blocking behavior should be understood, and how these states remain auditable over time. Exact numeric values such as max durability, repair unit cost, loss amount, and scaling curves remain SSOT-owned and can evolve forward-only.
Scope
Durability defines pickaxe condition and maintenance behavior within the Game Systems layer.
- pickaxe wear during ore discovery mining
- repair interpretation, recovery state, and runtime blocking at depleted condition
- separation of gameplay meaning, SSOT parameters, and server-side enforcement
- forward-only updates to durability policy, tuning, and repair handling
Core Model
The core model is that a pickaxe has a condition state which changes through valid gameplay usage and can be restored through repair actions. This condition state is not a cosmetic label. It is a real gameplay boundary that affects whether a tool remains eligible for continued ore discovery mining.
- durability represents operational condition, not ownership or tier by itself
- ore discovery mining consumes condition under valid runtime rules
- repair restores missing condition through explicit maintenance actions
- depleted condition blocks further eligible use until durability is restored
Core Definitions
| Term | Meaning |
|---|---|
| Durability | The current condition state of a pickaxe during ore discovery mining. |
| Max Durability | The upper bound of a pickaxe’s restorable condition under current configuration. |
| Durability Loss | The condition consumption associated with eligible ore discovery mining activity. |
| Repair | An explicit maintenance action that restores missing condition. |
| Repair Unit Cost | The SSOT-governed cost basis used to interpret restoration of missing durability. |
| Blocked State | The runtime condition in which a pickaxe may no longer continue eligible ore discovery mining because durability is depleted. |
| Mastery | A progression-linked factor that may affect how durability capacity or maintenance economics are interpreted. |
Operational Behavior
In operational terms, durability follows a predictable lifecycle. A player equips a pickaxe, uses it in ore discovery mining, consumes condition according to runtime rules, and restores that condition through repair when appropriate. This creates a maintenance loop that gives tools continued operational meaning instead of reducing them to static assets.
When durability reaches a depleted state, ore discovery mining is blocked until repair restores the tool to an eligible condition. This keeps the rule simple, auditable, and enforceable. Durability state is resolved server-side, even if clients show estimated or simplified condition display.
Repair Model
Repair is the maintenance action that restores missing condition. It exists as a predictable operational sink rather than a hidden penalty. The conceptual model supports partial restoration and full restoration, but exact UI choices, prices, and thresholds are governed separately by live configuration and implementation policy.
What matters on this page is the meaning of repair: it is the explicit bridge between depleted condition and renewed eligibility. Repairs do not rewrite past wear history; they create new forward state by restoring a tool into a usable condition.
What Durability Affects
- continued eligibility for ore discovery mining
- tool maintenance rhythm and downtime planning
- the economic interpretation of repairs as an operational sink
- how players manage stronger tools over longer cycles of use
What Durability Does Not Define
- it does not directly define refining or forging result probabilities
- it does not redefine unrelated fixed-time reward loops
- it does not act as the source of truth for final numeric repair values
- it does not override broader token, market, or participation policy
Constraints
- this page does not hard-code final durability caps, repair prices, or wear values
- durability is enforced through authoritative runtime state rather than client presentation alone
- depleted tools require explicit restoration before eligible use resumes
- future tuning changes apply forward-only and do not retroactively rewrite prior durability history
Integrity Considerations
Durability integrity depends on keeping roles separate. Docs define meaning and boundaries, SSOT owns changing numeric values, and code enforces valid state transitions such as wear, repair, and blocked usage. This separation keeps maintenance rules stable in interpretation even when balancing evolves.
- durability state should be derived from authoritative server records rather than client display alone
- repair actions must produce explicit state transitions instead of hidden resets
- past wear and restoration history should remain auditable even after future balance changes
Future Expansion
As PVERSE expands, durability may connect to richer pickaxe specialization, maintenance-linked mastery benefits, visual condition signaling, premium convenience layers, or additional repair-adjacent systems. The conceptual model should remain stable: tools wear through use, can be restored through repair, and only valid forward transitions define their state.
Summary
- Durability defines pickaxe condition and maintenance meaning in ore discovery mining.
- Wear, repair, and blocked use are distinct runtime states with explicit interpretation.
- Exact values remain SSOT-owned and can evolve without redefining system meaning.
- All durability changes follow forward-only handling and preserve auditable history.