GSC Belly Drum Pt. 2

**smbcha (Derwin)** · December 13th, 2011, 07:18

Originally Posted by Whereabouts Unknown

So I was laddering GSC and I came across a strange occurence while using Belly Drum Quagsire.

Quagsire used Belly Drum!
Quagsire cut its own HP and maximized its Attack!
Quagsire's Attack sharply rose!
Quagsire's Attack fell!
Quagsire's Attack rose!

I appologise if this is accuracte with the cartridge games but I cannot test it. Though I doubt this is normal.

I couldn't get any pics of the original battle in which this occured nor did I manage to save the log because my opponent got impatient or something and quit. But I was able to replicate the glitch.

And after testing a bit with a few other Pokemon I figured out some of what the problem is. It relates to the 999 Atk cap. Some Pokemon are able to Belly Drum normally, boosting to +6 with no strange occurences. In this case, it is because it wouldn't cross over the 999 Atk cap if it does. But for a Pokemon whose Atk at +6 would be over 999, such as Quagsire, the game solves the problem, but leaves a trail of the steps it used to fix it. My theory is that Belly Drum doesn't check the cap Atk. It allows Quagsire to hit 1056 Atk. But in response, its Atk is made to drop by a level so that it is below 999. Then it adds a level, which correctly maxes it out at 999.

I'll show you what I mean:

Slowbro's Atk at +0 is 248. So at +6 it doesn't pass the cap, 999. So there's no problem here.

However, Quagsire hits over 999 at +6, so it initiates the irregularity. In response to the overshot, the Atk drops a level, then goes up a level. When it adds a level, it caps at 999 like it's supposed to. Snorlax goes over 999 by so much that it needs to drop two levels to get below 999, then it adds +1 to get to 999.

To seal the case, Marowak holding a Thick Club goes way over 999 when Belly Drumming, so:

Full log:

Sorry if this was hard to understand. If I didn't make it clear, the problem is that the game shows what it does to get the stats to max out at 999 correctly in the logs and on the screen. I'm not sure if you call this a Bug or Glitch or something else, but it's probably not correct.

Maybe it's possible to just let Belly Drum check if it needs to max out at 999?

When user has less than half HP and uses Belly Drum, it still increases attack by two stages.
I am completely sure this is not supposed to happen in the real game.

Professor Oak** · December 13th, 2011, 08:00

Originally Posted by smbcha

When user has less than half HP and uses Belly Drum, it still increases attack by two stages.
I am completely sure this is not supposed to happen in the real game.[/CENTER]

I am completely sure that you are incorrect. This is actually the correct mechanics.

There is no actual bug here, only the message bug. This forum is not for asking questions, it is for posting bugs.

Topic locked.

**eric the espeon** · December 13th, 2011, 11:11

Unlocking due to new evidence: http://www.angelfire.com/pa4/jman/belly_drum.html

In Gold, Silver, and Crystal Belly Drum also has the odd characteristic of being able to be used when the using pokemon is at or below 50% of their total HP. The message will be given that the move has failed, but there actually will still be an effect. When Belly Drum is used under these circumstances the using pokemon will not lose any health, but their attack will not increase by as much as it normally would. Instead, its Attack will increase only 2 steps on the Stat growth scale. When Belly Drum is used in this way the increase acts identical to any other 2 step increase (such as Swords Dance). This additional ability does not work in Stadium 2. Use of Belly Drum when the using pokemon is below 50% will only result in the move failing (along with the appropriate failure message).

I believe we're using Stadium 2 mechanics for GSC until we are able to do subgenerations, due to less buggyness.

coyotte508** · December 16th, 2011, 16:17

then put a confirmed tag around it!

**smbcha (Derwin)** · December 16th, 2011, 18:44

I managed to do it. Heh.

Thank you Ete for the extra info.

**eric the espeon** · December 16th, 2011, 20:19

Originally Posted by coyotte508

then put a confirmed tag around it!

I was waiting for dev confirmation on changing cart to stadium mechanics being a policy.

coyotte508** · December 16th, 2011, 22:40

shadowfist fixed it!

**Jørgen** · December 17th, 2011, 01:24

Well, that takes away a key strategic element of GSC that's been in place since all of ever. I understand that it's technically correct, but it's kinda silly to be taking away elements of the metagame that have been around forever just because of the arbitrary decision to use Stadium mechanics as opposed to cart mechanics.

/end rant

I guess I can adapt, but I don't really like it...

Oak EDIT: I fully agree.

**smbcha (Derwin)** · December 17th, 2011, 01:26

I sincerely apologize for the upcoming disadvantage. I am only doing what I can do for the server.

**Crystal_** · December 17th, 2011, 12:48

Please don't do it guys. Don't change 10 year old metas for no reason. Even if PO uses stadium mechanics, the main goal should be making it as similar as possible to GSC, because that is what has always been played. As the name says its Gold/Silver/Crystal, not stadium.

Please, wait until you do the subgenerations, or at least let GSC players decide about this.

Lamperi* · December 17th, 2011, 12:55

It has been GSC since its implementation, at least it has been supposed to be.

coyotte508** · December 17th, 2011, 13:15

Well all blame smbcha

If a GSCer reverses the change in the code, i'm ok with it and won't undo it.

**eric the espeon** · December 17th, 2011, 22:41

Or better still, we stay consistent and take this as an incentive to get subgenerations working properly, make that like a #4 priority (webclient, RBY, probably something else really urgent).

Thread: GSC Belly Drum Pt. 2

Thread Tools

Display

GSC Belly Drum Pt. 2

Posting Permissions