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.