When enabling any of the advanced ground movement rules in 0.41.10, princess bot will refuse to move her units. In some instances, she will outright refuse to deploy. she will, however, fire normally.
Attached is a .7z containing...
A save with an example of her not moving
gameconf.xml --- Settings that cause the erroneous behavior
gameconfwork.xml ---Settings that work
I cannot, however, find what causes her to refuse to deploy in some cases.
Uh oh, seems like this should've been put into stable 0.42 milestone
Sorry!
Make sure you read the Princess Help documentation (availble form the Help button on the Princess config dialog) to see what Optional Rules Princess is compatable with. There are many that will produce unpredictable results. If the rules you're using aren't on the list contained in the help doc, then this isn't actually a bug but something that simply hasn't been implmented yet.
If you want support for some of these optional rules, you should create Feature Requests for those you want supported. Ideally, you should create separate requests for each option so they can be evaluated, tracked and acted on individually.
The issue is, these are all features that have worked prior-- Hull Down, Backwards movement, sprinting, etc. It's not that princess won't use them, its that princess will literally not do ANYTHING with them enabled.
For instance, I recall princess being compatible with hull down in that, though she would not have entered hull down of her own accord, she did however exit it if she was knocked down to that state. Now she outright will not function.
Last edit: Joseph D. 2015-11-02
This is actually a duplicate of [#4637]. There was a crash in MovePath.addStep because the option to make a PSR when jumping into heavy woods was on. This has since been fixed.
Thanks for attaching a saved game. Frequently, the megameklog.txt (in the logs directory, mekhqlog.txt if you're running MekHQ) is also very useful. In this instance, there was a stack trace from an uncaught exception which would've told me immediately what was going on.
Related
Bugs:
#4637Last edit: Nicholas Walczak 2015-11-03
Alright, thank you very much for the sitrep, man. I'll be sure to attach the log file as well, next time.