Please sign in to comment.
Don't let explore options impact connectivity checks
This was impacting seed stability: this code is called in various contexts, including stair checks / vault exit checks, plus from some lua code. The returned coordinate could be different depending on these options. The options that could potentially matter are `explore_wall_bias` and `explore_item_greed`, though I suspect the latter won't. The former I have verified to matter on seed 18127138284784505733 (UV4's game of the month seed right now), where setting it to 1 prior to this commit produces a different dungeon than the default value of 0. Thanks to u/kitchen_ace for noticing that deleting their rc file changed the dungeon, otherwise I'm not sure I would have ever found this bug.
- Loading branch information...