@Dev_VKC FD Mavae has permanent stealth, even after FD Ash got killed
That’s not a bug. FD ash permanently gives camouflage to Maeve
Am not aware of it. I thought Maeve will lose her stealth once fd ash got killed
How did this happen?
Battle ID: bb0e5
The second copy was added next next in line???
Ah I see now. Quite interesting. Maybe it should then be immune to copy/rebirth skills like Shi Na. But why was it added AFTER peng and not right next in line.
1 Like
I think it happens because the pg was revived, if it had not been revived, peng would enter and the copy would go after peng, so I think that is normal
Moral of the story - Aethereon’s rebirth move should negate revenge.
3 Likes
Should it also get raw maneater bomb all?
1 Like
@Dev_VKC Seduce reduces bosses hp to 1, is this intentional?
Haha
I understand what you’re saying, but what I’m saying is something else entirely. My complaint is that a mythic Pokémon with the maximum bonus to life potions, with everything maxed out, has to play before a legendary or super epic Pokémon with the same speed.
What’s so funny ?? 
It’s cool that this was reported back in september 10th and it still has not been fixed nor has she been disabled in pvp. @Dev_VKC What’s the point of playing the game anymore if bugs can just exist and you ignore them?
1 Like
We’ve checked and confirmed that the setting is definitely 200s.
Our guess is that the seconds on the TU bar may not update properly.
Did you see this happen in PvP?
Could you tell us which monster it was and what its seconds showed?
Any extra details you can share would really help!
It was the dark unbreakable shield dragon with Nyx fermattad. It got a turn even tho it was between 190-200
1 Like
I need to use “Van Sith” please. I haven’t played ranked because of the ban and they still haven’t fixed such an easy-to-fix error.@dev_VKC
Welcome to Neomonsters, we have updates once every 6 months no matter how urgent the issues are 
Enemies selected for “engage+” become non-injury for over 300s in pve
Thank you for reporting!
Yeah, it’s an easy fix, but unfortunately with the Neomon code, we need to submit a full update to apply it… that’s the difficult part.
This issue is either new or one we missed if it was already reported. We’ll include the fix in the next update.
2 Likes
What was the enemy and what battle did you play?
1 Like