Dancer Archive
Thread: Dancer Buffing Problems Found on TC
Eaca wrote:
I'd say passive solo dance buffs not working ever is a great thingOh nooooooes, da bots can't dance buff no mores
![]()
That thought did occur to the testing team, of course. ![]()
Of concern to me is that whether grouped or /setp'd, buffing teams of a dancer and musician have to get buff clients to /stopwatch before they /stoplisten, or it'll blow the dance buff. This concerns me because it puts the chance of success or failure into the hands of the one receiving the buff - and there is again the hassle of having to explain this very critical step to everyone getting simultaneous buffs.
In all of our testing, single /setperformed dance buffs worked fine. One thing not tested specifically was dancer buff only for full groups, as it was assumed that if passive buffing didn't work for one, it wouldn't work for all.
So, let's get as much more testing done as we can, learn the currently known workarounds, and know thatI'm trying to get some 13th hour attention towards fixing the problem.
Though I'm a very tired Dancer right now... I have been up all night testing, after all.
Soooooo how exactly is the “work-around” the bugs? They have to start /watching before /listening? And /stopw before /stopl?
And can not be grouped? Does a dancer have to /setp before the musician?
ROFLMAO this is going to be an interesting mess….
Deli'ah
Petronela wrote:
Well it looks like it’s going live today, can’t wait till I get home to see it.
Soooooo how exactly is the “work-around” the bugs? They have to start /watching before /listening? And /stopw before /stopl?
And can not be grouped? Does a dancer have to /setp before the musician?
ROFLMAO this is going to be an interesting mess….
Deli'ah
Test test test and report back. We were only so many people, with very little time. We tried as many things as we could even to figure out what was sometimes causing the dance buffs to not take, and I'm sure that additional time testing would yield good info.
Thusfar, it seems that the only thing that matters is that the customer /stopwatch before /stoplisten. In active buffing, the order in which the entertainers /setp'd didn't appear to affect the outcome, but I'll be honest... we started with passive buffing, and it took a really long time to isolate what was going on. The active buff tests were done towards the end (around 2:00 am pacific... 5:00 am eastern), and could really stand some more checking. Yes, we were getting tired. ![]()
It is possible that there are other combinations of which performer (dancer or musician) is watched/listened to first, which one /setperforms first, etc., that could cause one or the other of the buffs to not take, although, thusfar all buff failures noted by the test team were dancer buffs.
Panthu wrote:
Deila, I know you'll see what I've said elsewhere, but what do you think?
I really strongly believe that all functional aspects of performance (XP gain and healing/buffing)should only attempt to check two things: (1) Is the performer there? (2) Are they performing at all.
Currently, flourishes are tied to function in an attempt to "judge" performance. This is very silly for Dancers especially because we will usually look best when mixing and/or in a synced group, both of which currently cripple your flo count.
Rather than try to find more ways to force this check on performance, could we instead push for a set Buff or XP gain based on the Dancer's level and not what they are doing now? Could we instead ask that the system try to check for ATK and the state of dancing?
I know these things have been asked for in the past, but this latest bug just seems to make it very timely to ask again. Do you think so?
Several months ago Tiaga posted his thoughts on changing the buff code from basing duration on number of flourishes to time watched (I think). I realize there is likely to be code changes involved in any of these, the likes of which we are unlikely to see until a revamp. It sure would be nice if the players who come to us for buffs actually saw what we do when not buffing them. I think we'dsee fewer posts from non-ents stating that they can't see why anyone would want to do these professions if they could actually *see* why we do them. ![]()
But on a more topical note..is there anyway they can at least hotfix out this change until it works right?
Esharra wrote:
But on a more topical note..is there anyway they can at least hotfix out this change until it works right?
I'm not sure that a hotfix is more topical. As Tiaga has said many times, Keld has flat out said that our buffing code is a total mess and needs to be completely redone. I don't know that it wouldn't be easier to just scrap the old code and create totally new code now. That's what I was asking Deila about.
AFAIK, Keld never said that would have to wait for a revamp, he just said it needed to be done... and things are being done now. ![]()
Message Edited by Panthu on 01-25-2005 12:42 PM
As for hotfixing..I was only referring to reverting the changes brought about by today's patch. God knows our code is borked & yeah, I'd love it if they could just re-write the whole mess.
Panthu wrote:
Esharra wrote:
But on a more topical note..is there anyway they can at least hotfix out this change until it works right?
I'm not sure that a hotfix is more topical. As Tiaga has said many times, Keld has flat out said that our buffing code is a total mess and needs to be completely redone. I don't know that it wouldn't be easier to just scrap the old code and create totally new code now. That's what I was asking Deila about.
AFAIK, Keld never said that would have to wait for a revamp, he just said it needed to be done... and things are being done now.
Edit: Oh, and I'm totally quoting you about the rest, Esh.Well said!
Message Edited by Panthu on 01-25-2005 12:42 PM
Message Edited by Esharra on 01-25-2005 12:18 PM