C# diagnostics: start with the symptom
Build, logging, file and expression failures require different checks.
Choose the symptom
- RFxxxx build error
- Runtime message or exception
- Keep a run log
- A file failed to open
- A formula parsed but failed to execute
Keep the distinctions clear
A successful build does not check gameplay preconditions. PushError does not stop execution. Empty Output does not prove there is no error: a filter may hide it.
CSharpLanguage profiling functions in this version do not provide a C# method profile. Zero script time in the built-in profiler is not a cost measurement. Managed breakpoints and profiling need a separately configured .NET tool; that workflow is not certified here.
Reckfell Engine documentationBack to top ↑