Bug Hunting (Patreon)

Right now I'm playing through several maps and writing down all issues I find. The maps that doesn't crash and can be fully played are being featured in this YouTube playlist.

Here's a list with some of the maps that are crashing the engine:

• retrojam6_khreathor (crash)
• retrojam6_negke (crash during gameplay)
• retrojam6_newhouse (crash)
• retrojam6_mjb (crash)
• retrojam6_mukor (crash): mod_numknown == MAX_MOD_KNOWN
• retrojam6_lp: map not behaving correctly. Ceiling bars above final elevator doesn't open, and several enemies doesn't appear.
• retrojam6_otp: map not behaving correctly. There are stray brush entities with the origin key accidentally left blank, and non-functional triggers (monsterjump at start, Shambler teleport).

Crashes caused by protocol limits, such as in retrojam6_mukor, will have a lower priority to fix because their issue is with the protocol, not the engine itself.

Maps that crashes during gameplay are the worst ones to fix when their crashes can't be reliably reproduced. Sometimes the reasons for their crashes are complex and can't be reliably tracked down with a debugger. Still, I fixed a number of such crashes earlier this year, so they're not impossible to fix.

Maps that doesn't behave correctly shouldn't be too difficult to fix, but I'm thinking about which kind of tools I could create in the engine to debug them. I know other engines have several map debugging tools such as bounding box visualization.

Maps that crashes upon loading can either be the easiest or the hardest ones to fix. But they're the most numerous ones, and fixing one of them should fix several of them, so they're high priority to fix.

I'll keep playtesting more maps to see how many more maps are affected by each problem, and to find out other issues.