One thing that can be peculiar in AAA games here is that the whole logic and gameplay actually sits on our UI scripting, which is responsible for player and AI actions (no behavior trees). Animations are just triggered by events sent by the manager but don't control the flow of the game.

Not too much, it's not a technical talk. I show a bit our debug ImGui in the emotion talk which gives you clues on the state machine made to implement the game (it's a classic "phase" implementation suited for turn by turn games).
Code in C++ and plenty of node scripting in the Snowdrop engine.

Oh bah merci 😊

I admit that, to an outsider, making a AAA game may look like shooting a film without a script in a year and then do 6 years of expensive reshoots :D

Interesting thread but yeah it's not that simple to make a model when the industry is not structured for it.

Hmm it does. "Create null from path" allow you to make a shape with a path object in it and link this path as the animation path of another layer (it's the "Trace Path" button).
Or maybe I don't understand what you mean here?

Hmmm it shouldn't be that hard with the "create nulls from path" function no?

Première nuit très pénible mais ensuite c'est nickel ! Parfois les yeux secs donc il faut être rigoureux sur les gouttes artificiels.

Mostly for my own work, trying to rationalize and digest what we needed, even if the UX direction around interactors was already set when I joined the project. It helped a bit the designer who made the button sequence system for the food minigame: youtu.be/8nq9CRiloAE