Problem codes
Every error the engine's tools give has a stable code, SH and four
digits, and its first digit is its class: SH0 the command is wrong,
SH1 the setup, SH2 a file of the game's, SH3 the operation. A
program branches on the code, never on the message. Each page here is
the one cargo shuyi explain <code> prints.
- SH0001: The command's arguments or input are wrong
- SH0002: No game is running in the MCP session
- SH0003: No module of that name is built in the game's engine
- SH0004: The build closed the link at its hello: the token is wrong
- SH0005: The JSON Pointer names no value in the scene's data
- SH1001: No shuyi.ron here or in a folder above
- SH1002: shuyi.ron doesn't read, or lacks what the command needs
- SH1003: A piece of the toolchain is missing
- SH1004: The game doesn't depend on the engine through the shuyi crate
- SH1005: No build is listening at the address
- SH1006: The build speaks another link version than this shuyi
- SH2001: A text file's syntax is wrong
- SH2002: A text file isn't valid UTF-8
- SH2003: A file isn't there
- SH2004: Several files could be the asset
- SH2005: No format reads the file
- SH2006: A file is bigger than its format reads
- SH2007: The pack differs from its sources
- SH2008: A name in the file isn't one it may use
- SH2009: Something given once is given twice
- SH2010: A number or a size is out of range
- SH2101: The game's code or text names a key
- SH2102: A screen's text is written in its code
- SH2103: The rules use what keeps them from being pure and deterministic
- SH2104: The rules depend on a screen, device or tool crate
- SH3001: The game's tools don't offer the operation
- SH3002: The game's tools failed
- SH3003: No such target, or the target profiles don't load
- SH3004: A file the operation reads or writes can't be
- SH3005: The game's tool program didn't build, or stopped before it answered
- SH3006: The build's link is busy, closed, or answered what shuyi can't read
- SH3007: The record was made by another build or with other content
- SH3008: The target's check found errors, so nothing was exported
- SH3009: The built program holds a path of the build machine
- SH3010: The target has no exporter, or no run step, yet
- SH3011: The export's build, or writing its package, failed
- SH3012: The final package holds what the game's disclosure part doesn't allow