Jump to content

Attacking Priority Broken


vascoegertklei
  • Branch: Live Branch Version: Windows Fixed

Choosing priority for a manual attack command has no affect. It always defaults to priority 5. This has been the case for a very long time now.

Easiest way to test is to try to set a !! attack task --> no yellow alert generated.

Checking the dupe errands tabs confirms this bug.


Steps to Reproduce

Issue a manual attack command on any critter with any priority other than 5. Check the errands tab of a dupe. Observe that the priority remains at 5.




User Feedback


A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.

I usually set attacking to ++ in the priority menu for all dupes. This helps a lot if you manage your other priorities reasonably.

Edited by blacklodgepup

Share this comment


Link to comment
Share on other sites



Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
  • Create New...