Agree on all points. Still waiting for warca/Bazilogon buff.
I have been talking with mike and he says that if he needs a few things to put in an update he will ask me in the future. So you will probably end up seeing some stuff you want put in.
Bahamuzar needs a buff.
His most important move throw can’t even kill a monster?
and then there is summon Swarn which can be easily countered with timestrike.
he’s already buffed, you need a give turner or team turner to support him to prevent time strike and also he should be behind protectors coz they can support each other.
Really love this update! Good job devs! Now go for clans and some competitive (monthly?) permanent pvp with rewards! 
The main problem is his throw move.
It is not like a one hit KO move unlike burnsalot’s double energy blast which easily kills two enemies.
maybe you used throw on a bulky enemy, swift dual throw is handy and also can be used together with hellfox, after you’ve used swarm and swift dual throw then hellfox will rebirth you so you get your shielp up again and you can once again summon swarm and swift dual throw. Aegis and another throw monster or SE protector would work good with them. ![]()
Mike – thanks for the updates.
The bitterbeast issue I’ve noticed has everything to do with sleep. His overwatch always works perfectly for me (knocking him to 1 tu) but if he is asleep, if dreamhunt is what causes the damage, he goes to 1 tu but doesn’t wake up until after his “turn,” causing him to go back to 100 tu. In my opinion, this is not how it should work since damage of any kind is supposed to give him the next turn.
I’ve never seen bitterbeast not go to 1 tu for any reason other than the dreamhunt bug.
I agree with the other bugs heros pointed out:
xx monster put to sleep sometimes has an opportunity to get one attack off even though the sleep graphic is showing. This seems unfair.
xx I have seen the weird bug where a monster randomly will absorb a ton of tu for no reason. For example, I was just farming for xp in last battle of chapter 7. My SS killed the enemy frontline. The Midas DR killed one of my mons, bringing in my blitzdragon. He stunned the enemy mons, but then there was this long awkward pause as the game seemingly tried to figure out whose turn it was. When it unfroze, for some reason my own chronozeroes (whose turn was soon) had been kicked to 397 tu, even though: a) it was my blitz who had stunned the other team; and b) chrono can’t be stunned in any event. I see this type of bug happen maybe once a week.
xx finally, just as a reminder, revenarchion still seems highly susceptible to death revenge. He gets hit virtually every time he is on the field. I guess it could be random, but if so, it has been a shocking run of bad luck since November. On a related note, I don’t think it’s fair that 150 doom bomb and 400 second bomb don’t cause revenarchion to respawn. I understand DR (notwithstanding the fact that it hits him disproportionately) because I had a hand in killing the enemy in that instance, and it’s a revenge move where the enemy is already dead, but if the enemy chooses to kill himself, I’m not sure why he should get the benefit of revenarchion not respawning.
I’m not using dreamhunt and have seen the bitterbeast bug many times, as I said before it seems like there are two issues with him.
Guess so.
I thought there were going to be balance changes in this update? Nothing got balance changed and no monsters got fixed right? I’m just making sure I didn’t miss anything
Yes, but since he is hit and then overwatch takes over the attacking monsters turn has ended. So he should be awake when his attack becomes 1 second.
+1
Yeah, no balance changes yet. Those are(probably) next.
if anyone wants to test a team agaisnt any other team i can make it and battle you with friendly pvp setting in a few days
Test your team is great. Problem is - the AI is stupid. Im destroying teams at 900 that usually destroys me. But still great feature 
Should be able to take a peak at these before next update. Sorry about the lack of bugfixes/balance changes this time around, everyone.
Aww crap, I shouldn’t have invited this friend of mine. But it was so tempting!