Jump to content

Debugger: Difference between revisions

From Advanced Computers Wiki
No edit summary
No edit summary
Line 13: Line 13:
* If the computer did boot initially and a fatal Lua error occurred which was not caught by the OS or [[UEFI]], the stacktrace is also shown in this output.
* If the computer did boot initially and a fatal Lua error occurred which was not caught by the OS or [[UEFI]], the stacktrace is also shown in this output.
* The Ac IP Address of this computer
* The Ac IP Address of this computer
=== Peripheral info ===
Blocks that act as device cable peripherals also have a unique, numeric id assigned to them which is accessible via the property <code>.uniqueId</code>. This is is also shown on block right-click, making it an ideal way for finding the correct peripheral if you have multiple of the same type.


=== Cluster info ===
=== Cluster info ===

Revision as of 02:15, 7 September 2026

Debugger
Debugger

The allows obtaining additional information about the state of a variety of blocks. It also provides access to the crash information of computers as can be seen in the screenshot below. You can access this information by holding the debugger in your hand and right-clicking any block with it.

Displayed output

Currently it lists the following properties about blocks that support this information.

Debugger output
Debugger output

Computer info

For Computers, the following information is added:

  • The current state of the computer, i.e. whether it is stopped, running or crashed.
  • In case the computer is in the crashed state, a reason is also displayed, such as "No mainboard installed".
  • If the computer did boot initially and a fatal Lua error occurred which was not caught by the OS or UEFI, the stacktrace is also shown in this output.
  • The Ac IP Address of this computer

Peripheral info

Blocks that act as device cable peripherals also have a unique, numeric id assigned to them which is accessible via the property .uniqueId. This is is also shown on block right-click, making it an ideal way for finding the correct peripheral if you have multiple of the same type.

Cluster info

For any blocks that support connecting to cables but are not just cables, the debugger lists all connected cable clusters and all participants in each cluster. For brevity, participants are only listed for the first occurrence of a given network id, but networks with the same id also share the same participants.