WowRefugee

Yet another small UI suggestion.

Often, I pre-make the items I need for dailies before I even take the quest.  (In the case of potions, and other small-inventory items, I may pre-make many of them in a single crafting session.) Also, gathering dailies simply serve items up from your inventory.

So when I talk to the trainer, I likely already have the turn-in.  But I have to go through a lot of dialog boxes to complete the transaction.   First one or more to get to the "accept quest" page, and then another set to get to the turn-in screen.   I am suggesting another button on the "accept quest" page saying "Yes, and I already have it." or something similar.  (Text altered to fit the particular quest dialog narrative, I suppose.) Select that button, and the turn-in page pops up right away, skipping everything in-between.

After leveling to 36, the bulletin board had a 2 level 37 quests available with a yellow '!'.  After I took the first (the "De Valles Inhieritance" quest), the question mark turned gray, even though the remaining quest (the "Peril of the Dryads" quest) was also L37.   This only an issue of the marker color, because the BB menu can still be selected and the quest  still taken.

 capture_available_37_quest_is_gray.jpg   89.19KB   97 downloads

When you interact with a NPC from a distance, you run up and go to a default location.  Some of these default locations are really inconvenient.  I am thinking especially about the 2 leather NPCs in the LW shop in EC - if you talk to the Skinning trainer, your toon will occupy the same location as the LW trainer,  and vice-versa with talking to the LW trainer making you take the same location as the Skinning trainer.

This is incredibly annoying because when you try to interact with the trainer when someone is standing there (through no fault of their own), the default selection is the player. Double-click selects the player, if you aren't watching closely and open a trade window, it will be with the player (I find random people opening trade windows on me a little disturbing), not the vendor.  Having to click the arrow buttons on the pop-up is an extra step which requires paying attention and alertness - not something I am always up to when I am doing my dailies (I often do dailies at times when I am too tired to actually play content).

Solution: Change the default interaction position for the NPC's in question.

I am sure there are other places where this happens, I will update this thread when I come across them.   Other players might chime in also with places they find where this happens.

Just a small UI suggestion.   On the pop-up window that comes up when you do the operation "Split Stack"  (either right-click menu or shift-click), in addition to the numeric entry field and the "Split" button, add 2 more buttons:  "Split 5" and "Split 10" - because these are the among most common actions, especially when doing daily turn-ins.

(The other most common action is just splitting off one item, which you get naturally because the number field defaults to 1.)

I would guess that the above three choices - splitting 10, 5, and 1 item from the stack, makes up >95% of all split actions taken, and making available the above 2 buttons will save people tons of time, because they mostly don't have to futz around with the numeric entry field.

A lot of stuff I like, but a few issues:

WASD movement does not combine well with mouse panning.  When moving normally (click-to-move), hold-right-button panning of the POV is smooth and workably slow.   But if you are moving forward with the "W" key, then any attempt to pan causes the world to spin around you, which is useless.  The pan speed should be the same in all cases.

You can't exit full-screen mode after you have logged out.   You have to log back in, enter the game, go into options, and turn it off.   In general, the game needs an exit button on the login and/or character selection screen(s).  The exit button should pop-down full-screen (if set) and close the browser window.

The new craft-all and mine-to-completion features need polish.  They both trigger error messages when they finish.  These messages should be suppressed for this special case.

Otherwise, it's looking good.