Okay, some strangely detailed info bits for ya.
Character #1: 2 bags and paperdoll.
When I login this character *without* Auto Queue Object delay, I get the following messages on login:
Ignored action request (already queued)
Queuing action request #2... 4 secs left
Finished two queued actions.
My two bags open, but my paperdoll does not.
When I login this character *with* Auto Queue Object delay set to 1500ms, I get the following messages on login:
Queuing action request #2... 4 secs left
Queuing action request #2... 4 secs left
Queuing action request #2... 4 secs left
Finished 4 queued actions.
My two bags and paperdoll open.
Character#2: 1 bag and paperdoll
*Same exact results in every way as character #1*
Character #3: 1 bag and paperdoll
When I login this character *without* Auto Queue Object delay, I get no Razer specific messages on login.
My main bag opens, paperdoll does not.
When I login this character *with* Auto Queue Object delay set to 1500ms, I get no Razer specific messages on login.
My main bag opens, paperdoll does not.
~
The thing I don't understand about this is how it works with some characters and not others. Honestly, another thing I don't understand is why Razer attempts to open gumps at login. The UO client is more than capable of doing this by itself, and rather fast at that. Can we have a way of disabling this feature?
|