-
-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Freehold: Auto route improvements #1903
Comments
Pull 6+7, this is what happened:
In short, you pulled a bunch of enemies, hammered most of them dead/down, pulled another enemy 7 seconds after you engaged the last of the pack. Then before this first pack died, you killed this enemy. As a result, a new pull was created and that's now pull 6. Once the original pull died fully it was created and that was pull 7. This is simply a chainpull and there's really nothing I can do about it without making everything really complicated with exceptions etc. The only thing I did change was that if there's a chainpull killed before the original pull, I defer creating the pull until the original pull is fully dead. In the new situation pull 6 will be the original big pull, pull 7 will be the chainpulled enemy. One potential thing I can do is if a chain pull is killed BEFORE the original group, is it really a chainpull? May as well merge it with the original pull then. |
Ok so while writing that down I figured out, it DOES make sense that if you chain pull something, but end up killing it before the original group, it ain't really a chain pull. So implementing that logic and merging the pulls instead landed me here, I think I'll keep this behaviour. Seems to make sense. |
…pull now just merges the pulls together. If you killed a 2nd group before you killed the 1st group, you didn't chain pull but did a deferred big pull really.
…was attached to which blip on the map with a pink line.
This was achieved by solving #1879 . |
Was just running this key while testing another feature and noticed two oddities: https://raider.io/mythic-plus-runs/season-df-2/16931073-10-freehold
The text was updated successfully, but these errors were encountered: