FIELD NOTE 01
Current official full-game issues
No broad developer-authored launch issue bulletin was found in the August 26 source sweep. A developer did reply to one current startup thread, which is documented in the community bucket because the report count remains one.
That distinction matters: an official response to an individual report does not establish prevalence or turn every IL2CPP launch failure into a Sludgineers-wide known issue.
- Current build and timestamp
- Exact developer response
- Affected platform or input
- Scope and report count
FIELD NOTE 02
Current full-game community reports
CURRENT COMMUNITY · SINGLE REPORT · LOW CONFIDENCE — One launch-day user reported a failed to load il2cpp error after trying antivirus, cache, file-verification and reinstall steps. The user then said Smart App Control had not actually been disabled and confirmed that as the issue in their case.
A Sludgineers developer explained in the same thread that Windows Smart App Control can block Unity IL2CPP binaries. Their response says to close Steam, review the Smart App Control setting, re-verify files, and send Player.log plus Player-prev.log from the stated Sludgineers LocalLow folder to Funk Games if unresolved. Changing a Windows security feature has broader system implications, so read the source response and Windows setting carefully rather than treating this single case as universal advice.
- One current report; not widespread evidence
- Reporter identified Smart App Control in this case
- Developer supplied Sludgineers-specific verification and log escalation
- No unrelated Unity-game fixes imported
FIELD NOTE 03
Historical demo issues
Official demo updates mention fixes for cursor, controls, music and sound-effects issues, plus broader gamepad, map and upgrade-tree navigation improvements. Community demo feedback also described a controller case where the jackhammer could remain toggled. These are historical leads, not current launch bugs.
If a similar symptom appears after release, it must be verified again in the current build before moving into either current bucket. The report should record platform, device, input settings, reproduction steps and build.

EVIDENCE LOG