Don't know if its just me but looks like they have broken the apothecary with the updated. None of my revive buttons work in 23 Well at least we can't complain about the revive times.
I think it is a great idea just as long as you dont have to use items to get the bar to come up if you use astone that will b nice!And Can you please allow glessic 29 to try this out?TY for all your hard work steph, IgotU
I have over 1200 tries at a +4 to a +5. Mathematically speaking (and I know this is FAR from the norm for such an item, yet, still, here I am) this means the success rate for this item is around .007% or greater. Does this mean with the first attempt it goes up to .017% or does it go to up 1% of .007 to .014? Furthermore, does repairing and item count as part of the upgrade/enhance process? If not, then the gap between payer and non-payer goes up even more? Is the intent of this implementation to improve non-payer chances or to widen the gap between payer and non-payer? Please just cut through the crap, be specific, tell us what the 1% refers to. If its a straight +1%, then you may have something. If we assume that repair does not count as part of upgrading/enhancing, and a straight n+1%/try, then one would need 30 protection stones to give us 15 chances at 15%. The game is dying, and has always been dying when the gap between payer and non-payer widens. This was true back when lvl 11 fletch was introduced. The ONLY thing that saved the game was the great gifting fiasco (those who have been around over a year know what I refer to). If this is implemented, AND repair does not count as part of active upgrade/enhance, AND it is not n tries + 1%, then you can consider this game finished. Most people are haning by a thread now, but given that your super domains are already dying, that you won't merge domains, that raids allow for continuous around the clock non-defend AND the possibility of an even wider gap between payer and non-payer if the details of this improvement are not made to lessen the gap between payer and non-payer .... consider this game completely toast.
Why is this only going to be in certain domains? Just as a test before it's pushed out to all of them? Because of the domains listed, I'm in none of them.
kabam should start threads stating changes they are about to create and ask for player opinions before any programming starts, this would cut out a lot of arguments and players quitting, instead of releasing it to a few test domains and then releasing it to all domains even after it proves to be a total fail....