- 3
- Posts
- 13
- Years
- Seen Apr 11, 2021
I'm currently seeing a bug in a pokefirered hack where releasing a Pokemon takes > 2 min (the game is totally frozen during this time). I haven't seen anything else that seems buggy or wrong and the changes are just to encounter tables, minor Pokemon rebalancing, and a few overworld events (nothing directly related to the PC / release code).
I've been poking around the code for releasing to try and narrow down where the issue is. My first thought was that something may have changed with the logic for deciding whether a Pokemon can be released or not, but I tried commenting out the calls to `RunCanReleaseMon` in `Cb_ReleaseMon` and the issue persisted.
Anyone have any idea where to start debugging this?
I've been poking around the code for releasing to try and narrow down where the issue is. My first thought was that something may have changed with the logic for deciding whether a Pokemon can be released or not, but I tried commenting out the calls to `RunCanReleaseMon` in `Cb_ReleaseMon` and the issue persisted.
Anyone have any idea where to start debugging this?