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

Access speed rules #24

Closed Zannick closed 10 months ago

Zannick commented 1 year ago

Due to the prevalence of upgrades that can affect damage output in some games, maybe it would be simpler to have a field "speed" on accessible things that defines a function returning the time taken, as in we write a formula for how long it would take given the number of damage upgrades or attack speed upgrades, instead of adding a new location with the same canon_id for every possible combination.

Of course, some things like boss fights are variable enough that we should just have an average, but when it comes to things like breaking blocks, it might be useful to have a helper function we can use in all such places.

I wonder if this makes it easier to deal with in-area spot movements, by replacing them with exits. I'm a little worried about having too many spots in a single area, just because of the combinatorial explosion of how many local rules need to be added as only or exc to mark where spots aren't actually connected. On the other hand, having a local exit be just a to rule means we don't have to add that formula for movement, and can continue precalculating the movement time.