Closed GoogleCodeExporter closed 8 years ago
We are currently in the middle of a raid and noticed the same. The error-values
are
not listed in the log (we're going to have to go to backups and reconstruct).
One member noticed that every time EP ticked GP was decreasing at varying rates
for
different people.
Original comment by nhakob...@gmail.com
on 17 Apr 2009 at 1:52
same thing here... any members in the raid got their GP reset to 0... those NOT
in
the raid were not effected...
Original comment by lib...@gmail.com
on 17 Apr 2009 at 2:15
Same thing here. All reset to 100.
Original comment by joelst...@gmail.com
on 17 Apr 2009 at 2:43
Same thing happened to us. We were able to notice the problem, and before
logging
out, we backed up our old values. We were able to save them, but it was a very
close
call. We will not be using EPGP recurring rewards until this gets fixed to
prevent
it in the future
Original comment by kiooki...@gmail.com
on 17 Apr 2009 at 3:36
same thing here. and actually when people were awarded items, they were not
credited
GP still stayed at the default value.
Original comment by derekr...@gmail.com
on 17 Apr 2009 at 4:13
Same thing happened to us tonight. All GP data for our raid group is lost.
Everyone's GP values set to 0. Wish we had backed it up or noticed sooner. I
was
running the recurring mass awards.
Original comment by dragonri...@gmail.com
on 17 Apr 2009 at 4:52
The same thing happened to my guild. We weren't using Recurring Awards or
anything. I
noticed everyone's GP was at 0 and then when it did start crediting people with
GP,
it also reduced the amount by 100 (our minimum GP amount). This bug is brutal.
Original comment by deleb...@gmail.com
on 17 Apr 2009 at 5:06
In addition to what I (and others it seems) have reported, the decay values
reported
in the log are positive (not negative as was previously done). It seems that
the EP
and GP are still subtracted, however.
Original comment by nhakob...@gmail.com
on 17 Apr 2009 at 6:44
This is embarrassing :-( Apologies for the mess.
This is fixed in r1196 and r1197.
Original comment by evlogimenos
on 17 Apr 2009 at 6:50
Issue 401 has been merged into this issue.
Original comment by evlogimenos
on 17 Apr 2009 at 8:05
Original comment by evlogimenos
on 24 Apr 2009 at 1:21
Issue 411 has been merged into this issue.
Original comment by evlogimenos
on 24 Apr 2009 at 1:22
Original issue reported on code.google.com by
TheNewAl...@gmail.com
on 17 Apr 2009 at 1:45