Repository navigation
Reports and Provenance
Reports explain the installed saved balance: estimated material values, actual Essence payouts, measured equipment references, resolved Skill parameters and Bonus progression. They do not establish survival acquisition, renewable rates or hidden mechanics.
Editing a CSV or Markdown report does not change gameplay. Edit the human configuration and explicitly rebuild instead.
All paths below are beneath config/essence_ascendance/.
- Run
/essence debug balance summaryfor the running balance summary. - Run
/essence debug balance validateto check the saved result against the running server. - Check
diagnostics/report_manifest.jsonfor matching balance identity and a complete export. - Read
README_REPORTS.txtandreports/balance_report.md.
These commands require permission 2 and support console. Validation reads saved data; it does not install or generate balance. /essence admin balance export recreates the derived reports from the active snapshot without recalculation.
A report-write failure after installation can leave valid gameplay with incomplete reports. Fix the write problem and export again. Edited TOML files and an old CSV do not describe newly active gameplay until a rebuild succeeds.
Every CSV below lives in reports/. Open as UTF-8, comma-separated data with headers. The exporter writes CSV, not XLSX.
| Files | Contents |
|---|---|
valuation.csv, warnings.csv
|
Intrinsic estimate, total spendable payout, routed Essence amounts and reasons |
valuation_sources.csv, valuation_source_dependencies.csv
|
Advisory loaded recipe structure; explicit export only; join by item_id and source_index |
equipment.csv, equipment_capabilities.csv
|
Measured external axes and catalog strength bands |
generated_equipment.csv, fishing_rod.csv
|
Installed Ascendance equipment baselines and rod values |
evidence.csv, evidence_dependencies.csv
|
Retained facts, provenance and dependencies |
curves.csv, bonus_tracks.csv
|
Prices, partial-funding samples, active spans and Bonus endpoints in their native units |
skill_rank_parameters.csv |
Every published Skill rank's exact native parameters and cost, including accepted settings |
builds.csv, build_skill_ranks.csv, build_selections.csv, build_category_pressure.csv
|
Modeled legal selections and contributing ranks; join by projection_id and scenario_id |
combat_builds.csv, combat_assumptions.csv, combat_defense_pressure.csv
|
Conditional numeric composition checks and their assumptions |
attunement_targets.csv, attunement_breadth.csv
|
Category targets and required/optional seals per chapter |
attunement_methods.csv, attunement_calibration.csv, attunement_pacing.csv
|
Registered activity units, calibration and modeled quantities |
attunement_investment.csv, attunement_repetition.csv, attunement_reachability.csv
|
Development, repetition and native activity opportunities; does not measure item acquisition |
latent_ore_supply.csv, latent_ore_policy.csv, latent_ore_worldgen.csv
|
Configured placement policy/minimums and final distributions |
runtime_parameters.csv, ascension.csv, invariants.csv
|
Resolved scalar pointers, chapter summary and complete-recipe conservation |
projectile_policy.csv, guard_policy.csv, posture_status_policy.csv, vitality_policy.csv
|
Saved system behavior explanations |
Routine rebuilds remove the two optional exhaustive recipe tables; explicit export recreates them. Markdown evidence lists are bounded during routine rebuilds. Complete decision tables and warnings remain available.
Older quest, adaptive-balance and competitive-provider tables belong to the retired generation model. A file left in an old directory is not a current export merely because it is readable. Check the manifest and this file list; fresh configs are required for the new model.
economic_value is an advisory estimate. total_essence and routed amounts describe base-item dissolution after conservation. Native enchantment components can change a stack's actual result: an enchanted-book catalog row is an upper bound, while the Archive/tooltips and loaded enchantment diagnostics show component-specific values.
The generator does not measure resource access, supply or automation. A saved reachable=false or unknown classification means access was not established, not that the item is impossible to obtain. Equipment stage describes relative measured strength, not when a player can acquire it.
Complete static recipe constraints concern spendable payouts. An advisory estimate can exceed a recipe bound without being a conservation failure. Opaque recipes are excluded from hard conservation and counted explicitly. An invariant PASS covers the modeled material bill, not every hidden machine operation or mod interaction.
Bonus values remain continuous between completed player-tier endpoints. A track may finish before Transcendent; higher player tiers retain the earned benefit. Eligible equipment tier does not cap the player's Bonus.
For Skills, compare the emitted skill_settings.toml with skill_rank_parameters.csv after a successful rebuild. Native paths and units matter; a smaller cooldown can be an improvement. Configuration cannot remove prerequisites or fabricate numeric ranks for binary mechanics.
Build reports are estimates of compatible combinations, not measured combat tests. A listed active-Skill cost may omit prerequisites, equipment or Bonus spending, so it is not the total price of developing that character.
| Path | Purpose |
|---|---|
diagnostics/report_manifest.json |
Profile identity and export status/detail |
diagnostics/report_text.json |
Lossless sidecar for cells exceeding 32,767 characters |
diagnostics/pack_metadata.json, diagnostics/generation_evidence.json
|
Saved environment and generation context |
diagnostics/bonus_tracks.json, diagnostics/routing_classification.json
|
Track and routing explanations |
diagnostics/failed-generation-*.json.gz |
Diagnostic candidate that did not install |
diagnostics/uncommitted-profile-*.json.gz |
Candidate whose durable commit failed |
A failed-candidate diagnostic is not installed balance. Use the summary and validation commands to check what the server is actually running. Keep the relevant log when investigating generation errors or timing.
Share mod/loader versions, integrity, relevant warnings and a small reproduction. Remove private paths, coordinates, player identifiers and credentials. Keep sanitized reasons and units.
Home · Preset downloads · Configuration · Rebuilding · Issues
Beta.18 · Minecraft 1.21.1 / 26.1.2 · Fabric / NeoForge. Pack makers: tune the settings and rebuild. Players: use the Ascendance Archive for gameplay and current server values. Version and upgrade guidance.
- How pack balance works
- Apply changes and rebuild
- Skill, Bonus and global settings
- Overrides and customization
- Item valuation and economy
- Progression and power
- Integrations and compatibility
- Worked scenarios