Monster Priority

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Priority List with "skaar:ach300k:max500k:ac"
2. Multiple Skaar monsters are engaged
3. Profit!

What is the expected output? What do you see instead?

expecting each Skaar to reach achievement goal and than do loop for max goal.
instead each Skaar fills till max and only than moves to next.

What version of Golem are you using? Beta or release? On what browser?

currently r1029, but the issue seems to have appeared after r1019

Does anything relevant appear in the Console? (ctrl+shift+J)

nop

Please provide any additional information below.

maybe make the choice of priority order to be a user configurable option

Original issue reported on code.google.com by alozovik on 30 Mar 2011 at 11:17

[GoogleCodeExporter]

This happens with other monsters, not necessarily Skaar.
I just did some checking with Ancient Dragons

Original comment by alozovik on 31 Mar 2011 at 6:43

[GoogleCodeExporter]

Might be worth working out a better way to deal with this using the new Script 
worker.

There's two parts to this:

1. Non-advanced use. Want to be able to just order a list of Monster types for 
simple priority.

2a. Advanced use - could do with a list of data to be passed through for it to 
be easily used via the Script worker.

or

2b. Provide a dynamic Group of option, and split out the current priority list 
into it - so all the options can be set by UI instead of text.

Personally I prefer 2b - though 2a would give a lot more power to users...

Original comment by RycochetTM on 2 Apr 2011 at 6:30

• Changed state: Accepted
• Added labels: Worker-CA-Battle

[GoogleCodeExporter]

I checked this with dragons on 1092, and it correctly went down the list from 
ach, ach, ach, and then only over ach after all completed.  Please confirm this 
is still happening, and let me know the console logs if so, as well as full 
priority order list.

Original comment by 0Artifi...@gmail.com on 5 May 2011 at 7:19

• Changed state: Verify