Forge History

Forge history stores important forging actions for tracing valuable equipment, investigating material consumption disputes, counting recipe usage, and reviewing abnormal results.

Configuration

History settings are under history in config.yml:

history:
  enabled: true
  auto_save: true
  save_interval_ticks: 6000

Field	Description
enabled	Whether forge history is enabled.
auto_save	Whether cached history is periodically saved.
save_interval_ticks	Auto-save interval in ticks. 6000 ticks is about 5 minutes.

Recorded data

A forge history record usually focuses on:

Data	Purpose
Player UUID/name	Identify the actor.
Recipe id	Count recipe usage and debug recipe issues.
Materials	Check material recognition and consumption.
Quality result	Trace high-quality equipment.
Success/failure	Analyze failure rate and material strategies.
Timestamp	Match logs, economy records, and player reports.
Result item summary	Verify whether the output matches the recipe.

Relationship with quality guarantee

History is not the guarantee counter itself, but it helps diagnose guarantee behavior:

• Confirm actual forge attempts when a player reports a long low-quality streak.
• Check materials, recipe, and preview time window when results differ from preview.
• Check whether player data and history were saved correctly after reloads.

Recommendations

• Enable both enabled and auto_save on production servers.
• Increase save_interval_ticks on high-concurrency servers if disk writes are too frequent.
• Archive old history after seasons or events.
• For “materials disappeared” reports, check history before changing recipe logic.