Danny Day - Dynamic Event-Listeners in Desktop Dungeons

[@forgottenodyssey]

Wow, the idea of using handlers this way just blew my mind - it solved some things I'd been chewing on for years (on and off) for some ideas I've had! Guess it's time to dive back into RL dev instead of putting it off...

[@Levelworm]

Interesting. It looks like an ECS idea in which the handlers are systems.

[@PsclKmn]

Fantastic talk, easy to listen to and I certainly learned new things.

[@jamesrivettcarnac]

Something else to look at is CQRS, where commands and querying are completely separate. Especially if you add on event sourcing, you have coherent separation of event handling and the game state. It's a formal version of what he is saying. It's the segregation of state and handling that is formalized, and would help with the UI. I would use a system that reads the attack command with hero monster as arguments, return the event which can mutate a hero state and monster state if it was a real attack. For predictions, apply these state changes to your UI copy. For real persist it to your ever store (game's world state).

[@zach_attakk]

Hello from the pointy bit of South Africa! Great talk. Gave me lots of ideas.

[@petersuwara5432]

Pretty much reactive programming. Checkout Rx and Combine, they do exactly this... :) Great talk and definitely the way programming is happening.

[@shanemarcus3525]

Tis guys head looks like Beeker from the Muppets. So pointy.