New User Interfaces - A Quick Intro

Due in a few days: [Change Log] 03/02/2015

http://static.cdn.ubi.com/0034/archi...rstacks_ui.png

Currently the options for Units and Stacks are unmarked and it's easy enough to confuse them,
especially if you have a lot of resources available.

http://thesettlersonlinewiki.com/upl...ext_Scale2.jpg

Until you're used to them be a little careful as you click.

Do This.

Only do this if you really mean to.

25 units x 8 stacks = 200

1 unit x 200 stacks = 200

Like the Build Queue, orders can also now be moved up and down in the queue by clicking the arrows/triangles,
while the 'x' remains to cancel an order:

http://thesettlersonlinewiki.com/upl...rows_Scale.JPG

This post could have gone several places but as it is more just a Heads Up! while it's incoming/new than a [Guide], would have been buried in the [Feedback] thread, seems a little too early for [Suggestions] (and matie2506's post here already has some labeling included very nicely,) here t'is.

very great "Guide" easy to understand like always :)
keep it up.

Thanks for that - certainly saved some people from some mistakes

And hopefully, we'll be able to move things in the queue like we could in test, I am sooo looking forward to this improvement :) Oh and this is a good guide for those that haven't tested this on test server :)

so if you build all you can and wanna delete the production you will end up sitting using hours and hours on deleting every single production 1 by 1 with the waiting time

Quote:

---

Originally Posted by SeVeN_K

so if you build all you can and wanna delete the production you will end up sitting using hours and hours on deleting every single production 1 by 1 with the waiting time

---

Why would you want to do that ?

Quote:

---

Originally Posted by Dorotheus

Why would you want to do that ?

---

Well, for one, because it's quicker to delete your entire queue and start again than it is to try using the function to move something from the bottom to the top of the queue if, for example, you really need to replace those cannons/crossbows/elites/etc. you just lost, ASAP... not least because deleting something doesn't kick you back to the top of the queue.

Manipulating the order does... and it is a right, royal pain in the repetitive strain injury to have to scroll back down to the right part of a long queue to move something up one spot, to get thrown back to the top of the queue again... rinse and repeat!

Changing those arrows to 'move to top' and 'move to bottom' would be so much more practical, IMO.

Quote:

---

Originally Posted by Ozzymandeus

Well, for one, because it's quicker to delete your entire queue and start again than it is to try using the function to move something from the bottom to the top of the queue if, for example, you really need to replace those cannons/crossbows/elites/etc. you just lost, ASAP... not least because deleting something doesn't kick you back to the top of the queue.

Manipulating the order does... and it is a right, royal pain in the repetitive strain injury to have to scroll back down to the right part of a long queue to move something up one spot, to get thrown back to the top of the queue again... rinse and repeat!

Changing those arrows to 'move to top' and 'move to bottom' would be so much more practical, IMO.

---

I seem to remember some posts from the latter half of 2012, where people complained that when they deleted items in the queue that something was lost. Possibly pop from barracks queue's , what I can't recall is if that has been changed since then.

However a "To top" would also have the benefit of you not having to remember what was in the queue so that you restart everything you had in there before you needed to make the change. It would also mean less server traffic.

Quote:

---

Originally Posted by Dorotheus

I seem to remember some posts from the latter half of 2012, where people complained that when they deleted items in the queue that something was lost. Possibly pop from barracks queue's , what I can't recall is if that has been changed since then.

---

Should be fixed.. 22645-Change-Logs