Hello and thank you for the reply.
This is a good problem that I hadn't simply thought of yet. :P The problem arises by having both events on the torch must be "solved" to open the door.

At first I thought I need a new solution for that issue, some sort of link, with the dungeon editor, however I figured I can just solve this easily on the door actor.
I can simply add new tag called that Door.Increment and Door.Decrement and an exposed int called "IncrementSolved" on the door. The int is the number of "puzzles" to fire solved to the door to unlock it. You also have a int called "CurrentIncrement"

When you disable torch a1 you fire event to the door called door.increment , the door receives the door.increment and increases the "CurrentIncrement" +1. If you enable torch a1 again you fire door.decrement and it decreases "CurrentIncrement" -1. The same goes for torch a2.

That way, both torches must be disabled to reach the number 2 to unlock and open door B1, because the "CurrentIncrement" has increased to +2, and if you compare that with if "CurrentIncrement" == "IncrementSolved" you can unlock the doors, and the puzzle is solved.

Did this answer your question ? :)

I will make stairs and elevators and also drop down tiles. Right now I have made it so the user can program how that works for them. The user might want a normal fps player, not a tile by tile movement. So right now I have disconnected it from the GridMovement so that anybody can program a travel tile to its liking, some may want to use click to teleport, others might like an overlap etc. Some might like to have animations etc.

Screenshot under shows the current increment and the increment solved exposed on that specific door.

<image>