Major bug. (in General)
December 16 2010 4:56 PM EST
I hired a minion for my tourney character and for some reason it also hired a minion for my main character. It also took away 8+million dollars. This is not what I wanted to happen.
They are both named the same but the xp is different.
I really hope the can be put back the way it was before. As I don't want a 4th minion or be out all that money.
I see no possible way to do this. I reviewed the code thoroughly over the past half hour, and checked all the logs around the time of this posting. I have come up with nothing.
All I can reasonably think is that you were changing parties and submitting the page multiple times.
December 17 2010 10:15 AM EST
Ouch! That is a huge bummer.
December 17 2010 12:03 PM EST
Is there any way this is connected to the bug of changing teams and not having it actually change (where the wrong team's fightlist shows)?
Honestly to me the more logical fix would be to require AK to fire the new minion and just send him 8 million. Or if you really wanted to be accurate look at how much experience is on the new minion, and just use the hire a new minion formula's found in the wiki.
10 minute job, no need to spend 30 minutes on it.
However, if it was a user error, then I don't think he is liable to fix it. Hence the 30 mins of trying to figure out what went wrong. On top of that, if such an error existed it would be very important to find it and fix it.
December 17 2010 12:37 PM EST
I can tell you that I hit hire once. Not multiple times. I then immediately went and trained my xp which worked just fine(on tourny character) had a few fights. Switched characters had more fights. I continued this switching characters to fight until I decided to train and noticed the extra minion and less moneys.
I don't know code but I bet demi is right and its related to the minor bug that when you switch characters it actually does not switch. Sometimes it will even fight the characters from the wrong character but say the right character.
I Can tell you one more thing. It was not a user error. I was not messing around or doing anything stupid. Just a regular guy doing a regular thing on a regular day in a regular place. I hope that I don't get stuck with this.
December 17 2010 12:39 PM EST
Only problem with that Kefeck is I have spent Ba on my main minion
Even if it was due to switching not fully switching, You'd still have to hire twice. There is no possible way that I can see where you can create two minions from one click.
doesn't the server sends to requests sometimes? I means that's not unheard of is it?
Servers don't send requests, clients do.
NS has spent a significant amount of time researching this. He's looked through the access logs and I'll be discussing the results with AK directly.
In short, it doesn't look like there is an obvious bug, and the hiring requests did not occur simultaneously.
December 17 2010 5:11 PM EST
Just as an aside, with many high cost decisions in CB there is an "Are you sure" type pop-up message. Hiring a minion doesn't have this.
Yes, you do have to select which 'enlist' button to click but given the increasing cost of minions as you progress maybe a pop-up would help.
That said, I can understand the slippery slope dilemma that NS and the admins are faced with that could make an official correction difficult in thus situation.
AK, worst case scenario though I'd say fire the minion and I'll help drum up the money you lost.
December 17 2010 6:56 PM EST
Potentially something to do with using the 'back' button on a browser where a request may have been resubmitted?
Some brainstorming thoughts that would invalidate the 'back button' being able to do anything (or any other way a request could get duplicated and resubmitted accidentally on a different character)...
Is there any sort of timestamped hash sent on a hire minion request or could I store a request and use that same information to hire a minion at two different points in time?
Is there something specific to the active character included in the client to server information as well?
I'm looking at most of that, currently it seems that a refresh combined with an interface issue may have caused this, but further testing will be required. I've spent a couple hours on this already today, so it'll likely be tomorrow before I really know much more than what I've already explained.
This thread is closed to new posts.
However, you are welcome to reference it
from a new thread; link this with the html
<a href="/bboard/q-and-a-fetch-msg.tcl?msg_id=0038m6">Major bug.</a>