search

Zannick / logic-graph

Tools for video game logic representation and analysis, particularly routing and beatability checks for speedruns and randomizers.
MIT License
3 stars 0 forks source link

Movement requirements #109

Closed Zannick closed 9 months ago

Zannick commented 9 months ago

This is a quality-of-life change that would let us change in-area exits that check for open doors to be simple movements (and thus get times added automatically).

[ ]: Accept req in movement items and create a table of requirements. [ ]: Evaluate these requirements in the condenser. [ ]: Check these requirements when checking movements.

Zannick commented 9 months ago

This kind of conflicts with movement_states which are cached versions of movement requirements (that affect time as well).

Zannick commented 9 months ago

Alternate idea: add an exit parameter e.g. movement: base which calculates the exit time as if it were a local movement. For non-base movements we'll have to decide whether to require the movement reqs are included explicitly or added implicitly.

If we wanted to allow multiple movements in this field, it would have to create multiple exits as we don't currently have variable times.