Not A Bug Libero + Curse

What type of bug are you reporting? OM

What is the bug?
Libero + curse results in the user targeting itself with the curse and hurting itself with both the 50% to inflict it and the 25% for each subsequent turn. this only happens if it is the first turn it is a ghost type.
https://replay.pokemonshowdown.com/gen9randombattlesharedpowerb12p6-2219042221 (turn 9)

Are you able to replicate it? If so, how?
yes, i used the almost any ability format to replicate this situation. the result ended up being the same (note that the clef is magic guard in this replay)
https://replay.pokemonshowdown.com/gen9almostanyability-2219046507 (the real interaction is turn 1)

i tested protean too which had the same result https://replay.pokemonshowdown.com/gen9almostanyability-2219057010

for all i know, this is the intended targeting mechanic as curse self targets when it is a boosting move. however, when a pokemon terastalizes into ghost and uses curse on the same turn, the targeting is "correct" and hits the enemy.
https://replay.pokemonshowdown.com/gen9ou-2219048596 (turn 1)

this is what leads me to believe it is a bug and curse should auto target an opponents pokemon if the user suddenly becomes a ghost type.

out of curiosity, i then tested if this same principle would apply when the user had trick or treat used on it prior, and sure enough the curse auto targeted the opponent in both natdex https://replay.pokemonshowdown.com/gen9nationaldex-2219053480
and gen 8 OU https://replay.pokemonshowdown.com/gen8ou-2219054758

because of this interaction especially im pretty confident this is a bug even if there is no released libero + curse mon to test it with in game.
 
Terastal and Protean are different mechanics. Crucially, Protean activates during move execution after the target of the move has already been chosen, but before Curse’s effect has been determined, resulting in this behavior. While I would agree that this is a bug, it exists in-game and PS intentionally replicates it.
 
Back
Top