Skip to content
DarkBladeDev Docs

Diagnostics, FAQ, and Flight Recorder

This guide covers common administration and player issues, validation errors, and runtime diagnosis using the Process Flight Recorder introduced in v2.5.0.

1. Frequently Encountered Issues

Issue 1: “Workstation not recognized” or clicks open Vanilla Anvil

  • Cause: The station block material does not match blocks: in stations/*.yml, or fallback_to_vanilla: true is letting the vanilla GUI take precedence.
  • Fix: Check /cfe station list to ensure the station loaded. Verify that your block matches the exact Bukkit material. If using custom tags, ensure the block PDC tag matches pdc_key:.

Issue 2: “Process does not start when clicking”

  • Cause: Missing tools in hand, insufficient input quantities, or unmet capability requirements (e.g. temperature too low).
  • Fix: Run /cfe recipe info <recipe_id> to view required materials and capabilities. Run /cfe status to inspect current station capabilities.

Issue 3: “Ghost blocks not appearing on multiblocks”

  • Cause: PacketEvents is missing or disabled.
  • Fix: Ensure PacketEvents v2.14.0+ is running in /plugins. Check server startup logs for PacketEvents initialization.

2. Process Flight Recorder (v2.5.0+)

CraftingEngine includes an in-memory black box telemetry flight recorder that captures the complete execution timeline of crafting processes.

Inspecting Traces via Command

Ventana de terminal
/cfe process list                    # Find active or recently completed process UUIDs
/cfe process info <process_uuid>     # Displays full chronological event trace

Telemetry Details Recorded:

  • Process Initiation: Player UUID, workstation coordinates, blueprint ID.
  • Stage Transitions: Time elapsed in each stage, probabilistic weights chosen, and failure recovery branches taken.
  • Player Actions: Strike timestamps, minigame accuracy scores, and cooldown compliance.
  • Resource Lifecycle: Exact moment inputs were consumed, refunded, or outputs produced.

3. Diagnostic Commands Summary

CommandPurpose
/cfe statusOverall plugin health, memory buffers, and loaded counts.
/cfe recipe validate-allBatch test all blueprints for schema and material errors.
/cfe multiblock checkScans target blocks to diagnose multiblock structure errors.
/cfe item inspectPrints exact namespaced identifiers of held items.

4. Getting Support

If you encounter bugs, performance issues, or edge cases: