Fell & Sell Bugs & Fixes: Current Patch, IL2CPP, Saves, Dungeon Stuck
A launch-week troubleshooting hub that separates already-patched bugs from issues still being reported by players.
Fell & Sell shipped fast patches immediately after launch, so troubleshooting advice goes stale quickly. Before using an old workaround, check whether the bug has already been fixed.
Fixed in Ver. 1.0.2
The Aug 26 patch fixed:
- dungeon generation blocking a path and making the level impossible to finish;
- the player freezing after loading a new dungeon floor;
- opened doors closing as a navigation problem — opened doors now stay open;
- overloaded weapon swaps permanently destroying an item;
- stacked equipment equipping the whole stack;
- FOV and several audio/localization issues.
Fixed in the Aug 27 major update
The next major update added or fixed:
- full controller support;
- auto pickup;
- full key rebinding;
- gates remaining locked after all enemies are dead;
- Quest Board empty/reward-loss bugs;
- items/furniture disappearing around scene or shop-building transitions;
- save stutter/crash cases and “Unnamed” save files;
- motion blur being disabled and SSAO/shadow settings behavior.
Failed to load IL2CPP
The developer’s current troubleshooting advice is to check antivirus/security software and verify game files through Steam. Their suggested sequence is:
- Check Windows Security or third-party antivirus quarantine/history.
- Add the Fell & Sell installation folder as an exclusion if the security tool is blocking game files.
- In Steam, open Properties → Installed Files → Verify integrity of game files.
Important: at least some players reported that the antivirus/exclusion advice did not fix their post-update IL2CPP error. So this is an official first-line workaround, not a guaranteed solution.
Save problems
The developer has a pinned save-system thread and says backup saves are available for investigation/recovery. If you have a serious save issue, preserve the affected files before repeatedly overwriting the save with new sessions.
Still seeing an old fixed bug?
If a dungeon is blocked or the Quest Board is empty on a fully updated build, treat it as a regression. Include the build, save behavior, and exact steps when reporting it. That is much more useful than a generic “game broken” post.