nethercore-systems Nethercore Debugging
Use the player's Debug Inspector and the current console bindings. F4 is the documented default inspector shortcut; confirm active input configuration before relying on other shortcuts. Host keyboard controls are not guest keyboard/mouse APIs.
Register stable state
ZX raw FFI uses name pointer + byte length + a byte pointer to correctly typed storage, not a two-argument convenience API. Register initialized, suitably aligned, long-lived memory in init. Do not leave dangling pointers to stack locals or resized vectors.
static mut GRAVITY: f32 = 9.8;
fn init() {
unsafe {
let name = b"Gravity";
debug_register_f32_range(
name.as_ptr(), name.len() as u32,
core::ptr::addr_of!(GRAVITY).cast::<u8>(), 1.0, 50.0,
);
}
}
Use available debug_watch_* functions for read-only views; do not assume every registration type has a watch equivalent. Verify signatures in nethercore/include/zx.rs. See inspector API.
Simulation boundary
The host handles pause/step/time scale. Do not early-return from authoritative update based on a local debug pause, or multiply simulation delta_time by a local time-scale control: that can break rollback consistency. Debug edits/actions are local scenario tools, not automatic synchronized multiplayer inputs.
Do not claim zero release overhead without checking the build/registration path. Gate optional instrumentation using the project's existing mechanism when needed.
Evidence
Log with pointer and byte length, inspect actual player state and reproduce with controlled inputs. The testing skill documents real ROM-backed headless assertions/actions/semantic snapshots with matching binaries. Require live values, completed reports and failing controls; parser success alone is not gameplay execution. Use a separate inputs/screenshots-only rendered replay for presentation checks.