Burn mechanics change?

[FNTCZ]

From the patchnotes: Burn no longer halves the ATTACK stat, but rather halves Physical Damage.

 

WTF? that's not how it works in the original games, why are the devs messing with the battle mechanics pulling changes out of a hat? @Kyu

[NonoPetitRobot]

So that mean Foul Play will hit to the same damages on a burned target right ?

[axx]

It's listed under 'Bug fixes' so I'm guessing thats how it works in the late gens?

[FNTCZ]

Just now, axx said:

It's listed under 'Bug fixes' so I'm guessing thats how it works in the late gens?

No, the way it works is definitely halving the attack stat.

[axx]

Just now, FNTCZ said:

No, the way it works is definitely halving the attack stat.

Generations III to V

Instead of modifying the Attack stat, a burn now technically halves the damage a burned Pokémon does with physical moves; it still does not reduce damage done by moves that deal direct damage.

Burn now inflicts damage at the end of its turn. If a burned Pokémon knocks out an opponent, it will now take burn damage.

If a burned Pokémon has the Ability Guts, burn's damage reduction is ignored (and its Attack is boosted by Guts).

Fire-type Pokémon can no longer be burned by any method.

 

Per bulbapedia.

[Kamowanthere]

Yes, the burned pokemon should have half of their attack stat in battle (not base, at lv 50/100). I didn't get what they mean lol

[DoubleJ]

Mostly boosts Foul Play. Can't think of another scenario yet. 

[FNTCZ]

7 minutes ago, DoubleJ said:

Mostly boosts Foul Play. Can't think of another scenario yet. 

It nerfs the damage output of burned mons.

 

Instead of only halving the attack stat part of the damage equation now it plainly halves the entire thing (base power, item boosts, etc)

 

8 minutes ago, axx said:

Generations III to V

Instead of modifying the Attack stat, a burn now technically halves the damage a burned Pokémon does with physical moves; it still does not reduce damage done by moves that deal direct damage.

Burn now inflicts damage at the end of its turn. If a burned Pokémon knocks out an opponent, it will now take burn damage.

If a burned Pokémon has the Ability Guts, burn's damage reduction is ignored (and its Attack is boosted by Guts).

Fire-type Pokémon can no longer be burned by any method.

 

Per bulbapedia.

Might aswell go back to 12.5% tick damage then. We're left with a single mechanic that has both gen 3 and gen 7 parts of it, lol.

 

Not to mention that when calcing we always use gen 7 because that's where all our battle mechanics come from, it makes no sense to back away from that.

Edited July 23, 2019 by FNTCZ

[axx]

3 minutes ago, FNTCZ said:

Might aswell go back to 12.5% tick damage then. We're left with a single mechanic that has both gen 3 and gen 7 parts of it, lol.

Not to mention that when calcing we always use gen 7 because that's where all our battle mechanics come from, it makes no sense to back away from that.

I mean, is working as in Gen VII, bulbapedia just has a weird way to put information incrementally:

 

Generation VI

If a burned Pokémon uses Facade, burn's damage reduction is now ignored.

Generation VII

Same as Generation VI, but a burned Pokémon once again takes damage equal to 1/16 of its maximum HP each turn at the end of each turn.

 

tl;dr Gen VII is the same as Gen III but with 6.25% damage.

[FNTCZ]

3 minutes ago, axx said:

I mean, is working as in Gen VII, bulbapedia just has a weird way to put information incrementally:

Wait. Idk, showdown definitely halves the damage, doesn't it?

[NikhilR]

Just now, FNTCZ said:

Wait. Idk, showdown definitely halves the damage, doesn't it?

I looked at the showdown calc for SM, and this is how it is:

 

If Foul Play damage does X% to Healthy Mon, then Foul Play does same X% damage to Burned Mon. 

Edited July 23, 2019 by NikhilR

[Matoka]

To my knowledge, the only intended change that this burn mechanic bug fix should affect is the interaction between Foul Play and the Burn Status, as previously Foul Play would effecitvely do half damage vs. Burned Targets (when it should do full).

This should be parallel with the base games, and should not cause unintended "custom" interaction