RTC/Warnings, Errors and Crashes
Back up your project
While you are editing your dungeon it is always best to keep at least two copies of your project. The first being the one that gets added to and changed. The seconded being a copy of this, which gets saved over after you have each successfully 'compile' and test.
Verify Layout
This is a helpful tool that can be found in the Level tab in the editor. This tool checks for any layout issues in your dungeon.
This could include:
- Stairs, ladders, and poles in one level that don't match up with a set in the corresponding level, ie a stairs down matching a stairs up. Fix: put a set in or check your level offsets.
- Pits that fall into solid walls. Fix: remove wall
- The party starting position is in a wall. Fix: remove wall, or change party start location in the Main Data tab found in the Setup tab.
- Shops features that are not matched up to shops. Fix: put shop currencies and stock onto a/the shop tile, have the shop sell and buy tiles target the shop tile.
- Heroes/characters that have not been placed into a mirror or starting party. Fix: remove unplaced heroes, or place them all into mirrors, or place them into the starting party.
Other crashes
Even after compiling with no errors the game may still crash.
Possible reasons:
Incorrectly sized graphics.
Only occurs if you have added images straight into the .txt file (incorrectly), or edited the image size after importing into the editor. Fix: Check through all the custom graphics by selecting them in the add new graphics window, an error message will appear when you highlight the name of graphic which has the problem.
Infinite loops
For example, say you have a relay that triggers a monster generator and also targets itself to keep triggering the generator, but the relay has no delay associated with it RTC will go into an infinite loop that locks up the rest of the "game loop" and never returns control to the rest of the program. Fix: Check you don't have any of these kinds of constructs, if you do, adding in a 1 tick delay solves the problem.
You'll also get the same problem with 2 teleporters that point to each other that teleport objects instantly. Fix: Add a tiny delay to stop RTC from going into an infinite teleport loop that will crash the program.
