SE Dev Game Code Skill

Allows reading the decompiled C# code of Space Engineers version 1.

⚠️ CRITICAL: Commands run in a UNIX shell (busybox), NOT Windows CMD. Use bash syntax!

Examples:

• •✅ test -f file.txt && echo exists
• •✅ ls -la | head -10
• •❌ if exist file.txt (echo exists) - This will NOT work

Actions:

• •prepare: Run the one-time preparation (Prepare.bat)
• •bash: Run UNIX shell commands via busybox
• •search: Run code searches using search_code.py
• •test: Test this skill by running test_search.bat

Routing Decision

Check these patterns in order - first match wins:

Getting Started

⚠️ CRITICAL: Before running ANY commands, read CommandExecution.md to avoid common mistakes that cause command failures.

If the Prepare.DONE file is missing in this folder, you MUST run the one-time preparation steps first. See the prepare action.

Essential Documentation

• •CommandExecution.md - ⚠️ READ THIS FIRST - How to run commands correctly on Windows

Code Search Documentation

• •QuickStart.md - More examples and quick reference
• •CodeSearch.md - Complete guide to searching classes, methods, fields, etc.
• •HierarchySearch.md - Finding class/interface inheritance and implementations
• •Advanced.md - Power user techniques for complex searches
• •Troubleshooting.md - What to do when searches return NO-MATCHES or too many results
• •Implementation.md - Technical details for skill contributors (optional)

Quick Search Examples

# Find class declarations
uv run search_code.py class declaration MyCubeBlock

# Find method signatures
uv run search_code.py method signature UpdateBeforeSimulation

# Find class hierarchy
uv run search_code.py class children MyTerminalBlock

# Count results before viewing (useful for large result sets)
uv run search_code.py class usage MyEntity --count

# Limit number of results
uv run search_code.py class usage MyEntity --limit 50

# Paginate through results
uv run search_code.py class usage MyEntity --limit 100 --offset 0
uv run search_code.py class usage MyEntity --limit 100 --offset 100

Always check the game code when:

• •You're unsure about the game's internal APIs and how to interface with them.
• •The inner workings of Space Engineers is unclear.

Custom Scripting

For building your own utility scripts to work with the indexes and decompiled code:

• •ScriptingGuide.md - How to write Python scripts, use BusyBox, handle Windows paths

Game Content Data

The textual part of the game's Content is copied into the Content folder for free text search:

• •Language translations, including the string IDs
• •Block and other entity definitions
• •Default blueprints and scenarios
• •See ContentTypes.md for the full list of content types

General Rules

• •In the Decompiled folder search only inside the C# source files (.cs) in general. If you work on transpiler or preloader patches, then also search in the IL code (.il) files.
• •In the Content folder search the files appropriate for the task. See ContentTypes.md for the list of types.
• •Do not search for decompiled game code outside the Decompiled folder which is at the same level as this skill file. The decompiled game source tree must be there if the preparation succeeded.
• •Do not search for game content data outside the Content folder which is at the same level as this skill file. The copied game content must be there if the preparation succeeded.

Action References

Follow the detailed instructions in:

• •prepare action - One-time preparation
• •bash action - Running UNIX shell commands via busybox
• •search action - Running code searches
• •test action - Testing this skill