-
Notifications
You must be signed in to change notification settings - Fork 308
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
Princess needs to know about TacOps vehicle arcs for planning movement #6300
Comments
Hmm. I couldve sworn this had an issue before. Good to see it being brought up though. |
@RaozSpaz I haven't been able to get a lot of in-depth testing on this yet, but I am hoping the loosened close-to-contact path restrictions will fix some of Princess's wayward tendencies here too. |
Your changes for this are in the 50.02 version right? If so I will be playing on that version within the next day or two and will pay close attention to it for you. |
Correct, and thanks! |
Shoot, I didn't realize that the project tracker could change this bug's state. If we see any regressions in 0.50.02, we will re-open this. |
So as of right now [after about 15 battles] its really hard to say if its been 100% fixed. Ive only seen her do the turned next to me bit like once or twice, and that Im fairly certain was because she was out of MP. HOWEVER, I have seen her randomly turn while down an alleyway, for effectively no reason. There was a mek in the direction she was facing but it was behind buildings. Where as I had 4 tanks down the road staring all 3 of the turned vees in the side. |
Finding more instances of suboptimal pathing. |
Here are the MM saves for the entire battle, the most obvious event occurred around turn 4-5 but it's a small scale fight and should be easy to produce in various eventualities here. |
[Placeholder / to be refined]
Princess appears to not know that TacOps vehicle arcs are more restricted than the default arcs, when planning movement with that option enabled.
See this conversation for details.
The text was updated successfully, but these errors were encountered: