Audit and Signature
EmakiForge writes audit data to forged result items after successful forging. This data helps trace the source recipe and validate whether material contribution data was tampered with.
Audit data
ForgeAuditBuilder writes data such as:
| Field | Description |
|---|---|
recipe_id | Recipe id used for forging. |
quality | Quality tier name. |
multiplier | Quality multiplier. |
forged_at | Forge timestamp. |
materials_signature | Stable hash signature of material contribution data. |
output_item | Output item identifier. |
materials | Material list with ids and amounts. |
Material signature
materials_signature is calculated from material contribution data. It can be used to:
- Verify that forge data was not modified externally.
- Detect items edited with NBT tools.
- Provide traceability for administrators.
Use cases
- Administrators can inspect forge audit information with forge inspection tools.
- Trading systems can reject items with invalid signatures.
- Logs can keep forge history for dispute handling.