Skip to content

Conversation

@Katsuvera
Copy link
Contributor

Uses Conditions and a bit of AutoMove instead of vnav to make it through the "RNG room", since personally vnav wasn't working for me.

I did a few hundred runs of Fist of the Father for HW Relic Weapons, and this is the final version of the Path that I settled on as I believe it is the most consistent (had no issues with the last ~75 runs with this final iteration). I believe there might still be a very small chance for it to get stuck (if you need to go to the right and steam hits you right as Arm's Length / Surecast falls off), but even in that worst-case scenario, AutoDuty just teleports back to the beginning and tries the Path again, and the chances of steam fucking you up again are extremely small. And even if it does, it'll just port and try again... So it should never get hard-stuck. Like I said, though, I didn't have this happen across 75 runs or so with this version of the Path, so I digress.

One thing that may be worth noting is that the consistency of the path does lower a bit if Arm's Length or Surecast are not active but... I'm not sure why it would ever be on cooldown? Also, if you use this while playing with other people, you might look a little silly running into a wall for 2 seconds (if it's right-path) but I don't think it's recommended to use AD while playing with other ppl anyway, so I don't believe that's a concern?

That's all. Thanks for your time, and ping Katsureva on Discord if you have any questions or concerns with it. o7

Uses Conditions and a bit of AutoMove instead of vnav to make it through the "RNG room", since personally vnav wasn't working for me.

I did a few hundred runs of Fist of the Father for HW Relic Weapons, and this is the final version of the Path that I settled on as I believe it is the most consistent (had no issues with the last ~75 runs with this final iteration). I believe there might still be a _very_ small chance for it to get stuck (if you need to go to the right and steam hits you right as Arm's Length / Surecast falls off), but even in that worst-case scenario, AutoDuty just teleports back to the beginning and tries the Path again, and the chances of steam fucking you up again are extremely small. And even if it does, it'll just port and try again... So it should never get hard-stuck. Like I said, though, I didn't even have this happen across 75 runs or so with this version of the Path, so I digress.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant