After catching a trainer's Pokemon, their next appears lower than it should

Rot8er_ConeX · Jun 22, 2015

My game has two possible scenarios where you can attempt to catch a trainer's Pokemon without the trainer deflecting the Pokeball. One - which is in default Essentials - is if the Pokemon in question is a Shadow Pokemon (I removed the Snag Ball requirement). The other is if the Pokemon is of a specific species and has a certain flag active - this relates to a sidequest/event in my game.

Other than changing the conditions under which you can catch a Trainer's Pokemon - a single like of code that's the start of an if statement - and adding an after-battle condition that forces you to send a party member to the PC if you successfully caught the sidequest Pokemon and have a full party, I edited nothing in regards to catching Pokemon. Therefore, I assume this is an error that is in either basic Essentials or the Gen VI Pack, which is what I'm using.

When I catch a trainer's Pokemon, the battle goes on as planned. However, their next Pokemon will spawn lower than it should, as seen in the picture below.

What's causing this?

Rot8er_ConeX · Jun 27, 2015

Acquiescence · Jun 28, 2015

Does it occur no matter what the next pokemon is, or does it only occur for that Glaceon? Try making the next poke something different and try again?

Rot8er_ConeX · Jun 28, 2015

It occurs no matter what the next pokemon is. Regigigas spawns so low the player's battle info box covers all but the legs.

Acquiescence · Jun 28, 2015

And this issue does not occur outside of when you catch a trainer Pokemon?

Rot8er_ConeX · Jun 28, 2015

Acquiescence said:
And this issue does not occur outside of when you catch a trainer Pokemon?

Correct. It might happen when catching a wild Pokemon, but because in that case there isn't a next Pokemon to spawn, I wouldn't know.

Rot8er_ConeX · Jul 3, 2015

Bump. This is now the only issue I'm having with my game.

Rot8er_ConeX · Jul 11, 2015

Bump. Noticed that snagging Pokemon ivolved some variables named "x" and "y". Thinking that may have something to do with this, I renamed them "xy" and "yy", but that didn't fix anything.