Piercing Sting

[godfather4]

Piercing Sting

Type: Bug
Category: Physical
Priority: +1
BP: 15
PP: 20
Acc: 95%
Makes Contact: Yes
Target: Adjacent (Choose 1)
Description: The user quickly pierces the opponent's body to inflict internal damage. It inflicts greater damage on lighter targets.
Sumthin' i should reference: Low kick deals more damage on heavier targets.

Secondary Effect: [What the move really does]
If opponent is hit, at the end of the turn, it takes damage based on his weight by the formula: [(300+user attack stat)-(target weight[lbs]+target defense stat)]/4. This effect will not happen if the opponent is Rock type, Steel type, if the formula result is below 0, or if the opponent has the ability thick fat.
Obs.: This move is 100% Accurate if Close Combat was used in the turn before, and if the opponent is traped or paralyzed/frozen. Reason: it's easier to hit specific points at the opponent if you are close to him, or if it can't move much.

Why it is the way it is:
Ideas that i already thought and rejected + reasoning: [read before commenting]

SPOILER: Click to show

1. To remove a fraction of the opponents HP:
Bad because this move is based on imprinting a wound at the opponent, which will vary depending on its type of body.

2. To start a perish countdown when it hits:
At first this seems good but if the opponent switches it barely gets any damage so no.

3. To make the effect hit steel and rock types:
"Most of them are heavy so this shouldn't be a problem." is a valid comment, but i ask you, do they bleed? No.

4. To make the effect like a second hit instead of calculating by that formula:
I can still consider this if that formula fails badly. However, it doesn't seem logical to me that it happens this way.

5. To last 3 turns (with lower dmg of course):
I can still consider this. However, in case of a switch the opponent would be rid of a wound, and without medicine or healing abilities this is not reasonable.

6. 100% Accuracy all time:
I can still consider this. However, specific places in the opponent must be hit in order for the effect to happen so that's why its 95.

7. For this move's secondary effect to get past Protect/Spiky Shield/King's Shield/Detect/Quick Guard:
I can still consider this. Would make more sense if it was a special move.

8. For this move to have 60BP but only deal damage at the end of turn(result would be close enough):
I can still consider this. I'm keeping the original idea as the weight should also be an important factor.

9. Then why the damage isn't calculated same way as low kick(inverted actually):
Because Low kick bases its BP on the opponents weight, damage is not applied as an effect.

Affected by stuff:

SPOILER: Click to show

Protect/Spiky Shield/King's Shield/Detect/Quick Guard: Yes
Magic Coat: No
Snatch: No
King's Rock: No
BrightPowder: Yes

Pokemon that get this:
Beedrill, Kricketune, Escavalier, Pinsir, Scyther. (don't know if a grass type like chesnaught could get this...)

Example calculation:
Highest atack stat from these mons is with Pinsir: 383.
Just by the weight, pokes above 683lbs are not affected.
Below this weight, the first pokemon to be affected due to the sum (weight+base defense stat) would be Beartic taking 7dmg.
Lets say a Pichu was hit by this pinsir: it would take around 165 dmg.

I'm willing to make a fighting move "equivalent" to this if it gets approved.

Last edit:
referenced low kick.
added explanation on Close combat.
added paralisys/freeze accuracy effect.
added 8th and 9th reasons why it is the way it is.

[Ace]

Imo, this is severely complicated...And I imagine this would be hard to code.

[Psych]

This would be a pain to code, and we already have an approved Bug priority move (Swift Sting).

[godfather4]

It may not be a small code, but i think it would be simple, its a priority damage with an accuracy condition, followed by a formula with a typing+Ability condition that applies at a already specified moment. Please don't comment on the coding if you haven't read the whole thing.

As for the comment above, i know we have swift sting but this move only does true damage at the end of the turn so its clear to me that both have different purposes. This is more like a bug themed inverse low kick. I may change the name if you think its too similar.

[silverwhiteblue]

It's certainly very interesting, but i am against complications like this. this might require it's own section in a calculator . outside competitive it seems a bit off of what gamefreak might make

[Psych]

I actually like this concept, there is one thing I don't get, and it's a nitpick. Why does Close Combat make it not miss? There's no reasoning behind that imo.

At this point, 95% and 100% isn't that big of a difference for me, just make it 100%.

I looked over the move more thoroughly and this definitely differs enough from Swift Sting, and Bug needs more love in the move department.

[godfather4]

Jul 6, 2015 3:07:12 GMT 1 Psych said:

I actually like this concept, there is one thing I don't get, and it's a nitpick. Why does Close Combat make it not miss? There's no reasoning behind that imo.

At this point, 95% and 100% isn't that big of a difference for me, just make it 100%.

I looked over the move more thoroughly and this definitely differs enough from Swift Sting, and Bug needs more love in the move department.

For both your first comments, the idea is that a specific place at the opponents body is hit which requires some precision from the pokemon executing the move. This precision may be at a 100% with compound eyes/no guard/wide lens or victini. Otherwise, theres no way a poke would hit with 100% accuracy the place where the opponent has vital parts, unless they were very close to each other, or if the opponent had some move restriction. I have already changed a bit the damage calcuation when i posted this, my original idea was supposed to do more damage so it also balances the OPness of this move.

I do guess this move will need to be balanced after its approval at an in-game test, i don't really know how strong it is right now. All i can say is that this might be good at early game since most pokemon will have low weight.

should i say this is finished and tag ppl?

[The Run]

This is very well thought out, however it looks quite complex from what I first look at it.

[gelatofellatio]

Lol I can't believe this will be my first post in this forum. Ok let me say this nice and slow:
1. This move has so many unnecessary effects that it's a convoluted clusterfuck.
2. Inverted low kick/grassknot? Meh. More like inverted Heat Crash because you need your mon's and your foe's weight values.
3. If you really intended this to be an inverse lowkick/grassknot, do research what low kick/grass knot does. This I ask of you.
4. You don't have time? Ok then let me tell you the gist of it. lowkick/grassknot does not have such a damage formula. It simply has varied Base Power based on certain weight benchmarks, not some gradual shit like this.
5. Originally has 95 acc but becomes 100 acc because of a handful of shit? Close Combat? Immobolization from paralysis/freeze and trapping moves like Wrap and bind? LMAO. Crap like 5 additional acc is too little for anyone to care about. Get rid of it and just make the move 100 acc instead. No one will bat an eye.
6. Priority+1 but damage is applied after the opponent's move? Interesting, but do elaborate why he hell we need to go the extra mile for this mechanic. Personally i think the inverted low kick damage formula is enough of a quirk anyway.

Verdict: Total Revision, please.

tl;dr Personally I like the prospect of an inverse lowkick/grassknot, that's why I cared to write what I wrote above. Read it.