Skip to content
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

Mobile>RequiresCondition is broken #16678

MustaphaTR opened this issue Jun 10, 2019 · 0 comments


None yet
2 participants
Copy link

commented Jun 10, 2019

If it is defined, doesn't matter what the conditions are. The units are incapable of moving. I didn't update RV to use PauseOnCondition instead of RequiresCondition for Mobile trait and last engine update i did complately broke all the mobile units. Removing RequiresCondition: chronodisabled made them move again.

Tested on TS on upstream by changing ^Vehicle:>Mobile>PauseOnCondition to RequiresCondition with opposite conditions and it happens there too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.