Dangit, I was hoping you wouldn't figure it out . . .
I get this too when vendor search crashes. I have gotten this message for example when the search string was "spellbook." I search on spellbook multiple times when I play because I am a mage. Sometimes I get the try again message right off the bat and other times at some point during the play session. Have never kept track of how often it comes up. Don't see this message every time I play. Maybe once every couple of weeks. Usually, when I see this message vendor search is unusable for the rest of the night or at least a half an hour.
Agree that bug messages should be specific. Would time of date and date also be helpful? Maybe, screen shots?
By the way what the macro poster describes happens to me every time I try to add something to a macro. For me, I don't think it is a bug. I can see what gets shifted when I modify the macro. When I am finished adding things I just put everything back into the correct order and most of my macros work fine after that. Sometimes I may have to change the delay time like you mentioned in your post.
I am going to write this.
I think Kyronix mentioned they will dedicate some time to fix the bugs in coming publish.
Frankly speaking, I think bugs are always a priority. Currently it feels like this is "additional work", so they will do this just once.
Long time ago, maybe during OSI days, they did mention the process of each publish involves passing through QA. I wonder if this position still exist in Broadsword.
You typically get paid to QA, not the other way around.
It is difficult to get more primary source information on a bug without using it over and over again, thus breaking the rules in our own right and subjecting our accounts to action. Further if we do our informal QA testing in others' houses, we subject their accounts to action as well.
YOU LEAVE SILVANI OUT OF THIS!!! Hell dont you dare blame any of them till you can say your perfect. That I doubt you ever will be. (notice i am not aiming this at anyone so dont get your panties in a bunch to remove it)
No one is perfect and in the coding game of the 1990's it was truly in its infancy. If you need to rally at something go for TIME. Time was the biggest enemy of any game out there. The world of coding and making on line games went in leaps and bounds. Professors at CSUN told their classes that by the time the finished the course in programming it would be worthless as the speed of the main stream industry was faster then the teaching.
Today the Dev work hard to make a old language program mesh with the new and not have it cascade to failure. Its why the bugs happen to begin with. Don't go ok then rewrite the game in the new language.... ahhhh no.. there is no budget to take UO off line and pick it apart and redo the whole thing. Much less EA letting them, they would love to sunset this game if given half the chance.
* note to the reader* Silvani and I were good friends in the old days when I was a counselor. When a player asked a hard question or had a difficult problem she and i would put our heads together to get a solution. She was one lady for the player. I miss her dearly.
Personally I think it was a early Dev attempt to curb macroing that didnt work right
