Fixed [Indev 0.51.1] Dream Eater Doesn't Work Properly

[Fanta]

Not necessarily, that is considered a separate bug. In that bug sleep by itself ends prematurely, but in this bug it ends due to Dream Eater usage.

actually if you read my comment, it's the same bug, cause the sleep wears off immediately and that's why dream eater fails.

 

[Tornado9797]

actually if you read my comment, it's the same bug, cause the sleep wears off immediately and that's why dream eater fails.

I have confirmed myself that Dream Eater causes the opponent to wake up, not just coincidence.

In the other thread, the user uses Shadow Ball twice before the opponent wakes up (without a notification of the opponent actually waking up). That is why I consider it a separate bug.

 

[Fanta]

I have confirmed myself that Dream Eater causes the opponent to wake up, not just coincidence.

In the other thread, the user uses Shadow Ball twice before the opponent wakes up (without a notification of the opponent actually waking up). That is why I consider it a separate bug.

ok excuse my english if i can't make myself any clearer, the dream eater is the same as the shadow ball in this matter, since the sleeping pokemon will always be awake, it will always fail, not because of an issue with the dream eater, but because the other pokemon was already awake when dream eater was used on him

does that make sense to you? i know my english sux.

 

[baelrune]

i'm using indev 0.49.1 and i have this problem, but it's specifically elite four, i can use it on average trainers but when i use it on will or bruno their pokemon wakes up during my attack.

 

[Blue]

Is this fixed yet?

 

[Tornado9797]

Is this fixed yet?

If the report is still in this forum, then the likely answer is no.

 

[nullCore]

This happens to for me also with nightmare.

Confirming that this still happens in 0.51.1. Nightmare does nothing to a sleeping target.
Don't know if Dream Eater is fixed or not though. Can someone confirm this for 0.51.1?

 

[jianmingyong]

Fixed in next version... probably v0.53 already have this fix?

 

[Fanta]

Fixed in next version... probably v0.53 already have this fix?

eh..? you're asking? so you mean that this has already been fixed? and not fixed in next version?

 

[jianmingyong]

eh..? you're asking? so you mean that this has already been fixed? an not fixed in next version?

In the next version it is fixed.