{"id":41,"date":"2026-06-01T12:46:34","date_gmt":"2026-06-01T12:46:34","guid":{"rendered":"https:\/\/blogs.scummvm.org\/mohit\/?p=41"},"modified":"2026-06-01T14:07:46","modified_gmt":"2026-06-01T14:07:46","slug":"week-1-chasing-crashes-in-the-dm-engine","status":"publish","type":"post","link":"https:\/\/blogs.scummvm.org\/mohit\/2026\/06\/01\/week-1-chasing-crashes-in-the-dm-engine\/","title":{"rendered":"Week 1: Chasing Crashes in the DM Engine"},"content":{"rendered":"

Hi everyone! Now that the GSoC coding period has begun, I moved from working primarily on the GUI to investigating crashes and gameplay bugs in the DM engine while becoming more familiar with its internals.<\/p>\n

The first issue I looked at was a progression blocker near the start of the game. After assembling my party in the Hall of Champions, I found, as Strangerke had pointed out, that the gate to the dungeon remained shut despite stepping on the floor sensors. The issue turned out to be an incorrect early return in the sensor effect logic, preventing the pressure plate from triggering the door-opening event.<\/p>\n

\"\"<\/p>\n

Another crash occurred when highlighting a selection in the game’s save dialog. The cause was a simple parameter ordering mistake in a box constructor used to draw the selection highlight.<\/p>\n

Another task involved implementing EventManager::highlightScreenBox()<\/em>, enabling visual highlighting for UI elements such as the movement controls.<\/p>\n