Debug Conditional Triggers GDevelop5

Job ID: 40002050

Budget: $30 – $250 NZD

I have a small top-down game built with GDevelop5 and a handful of conditional triggers are not behaving as expected. A typical example is a multi-step puzzle: the player meets the required conditions, yet the door refuses to open—or opens repeatedly—because the event sheet logic isn’t firing in the right order. The core mechanics, graphics, and performance are otherwise solid; the problem is squarely inside the gameplay events that rely on conditional actions.

Your task is to open the project in GDevelop5, trace the faulty events, and rewrite or reorder them so the logic executes exactly once, exactly when it should. Feel free to use the built-in debugger, breakpoints, or preview mode—whatever helps you prove the fix works in-engine. When you’re done, send back the updated project file along with a short change log explaining what you adjusted and why, so I can follow the reasoning and avoid similar mistakes next time.

Acceptance criteria:
• Every conditional action now triggers reliably under the correct in-game circumstances.
• No new regressions appear in player controls, enemy behaviour, graphics, or performance.
• You provide the revised project file plus a brief, clear summary of changes.
• Be able to fix the camera question.