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

Drop behavior for carryalls #16376

Open
matjaeck opened this Issue Apr 2, 2019 · 0 comments

Comments

Projects
None yet
2 participants
@matjaeck
Copy link
Contributor

matjaeck commented Apr 2, 2019

Currently, when queuing orders the behavior for dropping the cargo differs:

  • queuing the pick-up has the effect that the cargo is not dropped after a queued, normal move order
  • queuing mover orders after pick up has the effect that the cargo is dropped after the move order

This is rather complicated and I would suggest to either always drop the cargo after the final queued move order or to keep queued move orders behave like force move orders but introduce a deploy feature to drop cargo when landed, which you currently can not do.

This would have the nice side effect that you could easily unload cargo from transport and carryalls with a common order. If the design guidelines allow it, one could consider to introduce DropOnDeploy instead of DropAfterMove as the default behavior.

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.