Started off from the above image posted by a forumer in the getting stuck thread. And I managed to find multiple ways to break the recruitment. Also managed to repro this reliably on test. Steps: a) click recruit this character! b) hold down enter button c) and you can recruit another char again ... Not sure what this fix should be. Maybe disallow 'enter' button when selecting char name ? edit: erm, the map image got truncated off, my bad... I wanted to show raid of ommlet not loading on the map.
This is another recruiting bug but it doesn't stall the game...anyways steps to repro: a) Right after greenfang, grab a MP starter pack, go to the Orc's head tavern. move all starter pack chars to clipboard. b) Click recruit this char! c) hold down 'enter' and the game will keep recruiting whichever character last recruited. You will see the char sheet fly from right to left consistently and the gold being deducted. However, exiting and re-entering the tavern shows only 3 chars on the left.
Another way to get multiple warrior chars at start, requires fast fingers, also a fringe case. Steps to repro: a) press 'recruit a char!', leave the mouse pointer over the button. b) press 'enter' key and immediately click 'recruit a char!' again before gary's prompt appear. Coordinate with both hands. c) then press 'enter' key and another char sheet will slide over to clipboard. From my pov, it seems like the culprit is the 'recruitment' button being left active after a char has gone to the clipboard. Minor bug: When asked to select name, if you clear the name field and then click random again. The 'done' button is greyed but 'enter' still works.
I can't repro this, can you elaborate? 1. I click "recruit this character" (and release the mouse pointer). 2. I see the name this character dialog. 3. When I press (and hold) the enter button, it names the character. 4. I can't see a way of recruiting any more after this.
Of the 3 cases, I'm now only able to repro the last case... :S Was there a new build on test recently ? edit: I'm beginning to suspect that memory is playing a part in this...as I had multiple instances of flash running when the bugs were first found... I will try to repro again...
well, I managed to get the second case again...I think i have a better handle on what's going on... fyi, performance capture at the same instance as ss above.
