known issues testing section (in General)

i went to florida for ten days and so was out of pocket for a bit as i played on my phone. i wasn't sure if anyone has had a chance to test these things especially since we had a tournament so was just seeing if we could clear some of these off yet:

Fixed: Can Be Removed Once Tested

* If a tournament character is your largest character, ba cost are determined by it. [15] (added 12/12/2009)
* Known Issue - DB seem to function 1 level less than their stated +, even if named [16]
* Add a join / apply button on the clan pages to make it easier to join clans. [17] (added 5/30/2010)

if you were able to test one of these, or can now, please post here so that we can move 'em out!

thanks! ; )

DB is fixed

does anyone have any input on the other issues?

ive recently joined a clan twice via the clan page.


i doubt we can confirm the BA cost when we have a tournament, although it would be nice to have a tournament at 7million mpr

it wouldn't be all that hard. You'd just have to retire anything bigger than your tourney character for 4 days :3 I'll try it when my rentals get back.

good point :P

Yep. If a tourney character is your largest character it will still affect the cost of your BA..


http://www.carnageblender.com/bboard/q-and-a-fetch-msg.tcl?msg_id=0033xo

hmm, i guess it is actually two issues then, ba regen rate and ba cost. i wonder if i need to actually separate them into two issues and only leave the ba regen rate one in the testing section?

nightstrike if you read this please advise! ; )

Yes, they are separate. I forget which one I fixed.

from kefeck's post i think that you fixed the regen so far and the cost remains to be fixed. later today, i will separate them that way and hopefully we can get some testing done during the next tournament to verify a fix as well as which one was fixed! ; )

i separated the two issues, left the cost one in low priority and left the regen one in the fixed but needs confirmation section. if i did get them switched, we should catch when testing! thanks kefeck for the heads up to that post.