Debug Card

Discover a Debug Card guide for Applied Energistics 2 Mod Wiki. This page describes how to use debug tags to fix some problems. You probably don’t need to read this unless you’re an AE2 addon/developer or we ask you to read it to help troubleshoot or you’re curious about how AE2 works internally.

Contents

Debug Card Setting

You need to enable unsupportedDeveloperTools in the AE2 configuration. Be extra careful with some of these, there’s a reason why they’re behind the unsupported containing config option. The Dev.DebugCard item is relatively safe to use and you should get yourself one and hold it in your main hand.

Also make sure that WTHIT (Fabric) or Gem (Forging) is installed.
When looking at an AE2 block or part, you should see something like the following:

Debug Card Node connectivity

The Node Exposed indicator highlights the aspects in which this device allows external connections. That has to match what’s visible in the world, otherwise it’s a bug.

Tick rates

To minimize latency, most active AE2 devices go to sleep when they have nothing to do, and then they slowly “wake up” over time. That’s why the input and output buses take a while to reach full speed. This information shows up in the debug info screen:

Tick Status

Sleeping: the device is currently in sleep mode, i.e. will do nothing until awakened.
Awake: the device is not in sleep mode, i.e. it must have some scheduled work.
Can alert: the device is allowed to go from sleep to wake if desired.
Lined up: this device is sure to come in handy and schedule later.
If a device is active, but not queued, it’s an error!

Tick Rate

“Current speed” of the device, i.e. how many game ticks (1 tick = 0.05 seconds) the device waits before two actions. This process will stop working when the device wakes up and then back up when the device has nothing to do.