• Just a reminder that providing specifics on, sharing links to, or naming websites where ROMs can be accessed is against the rules. If your post has any of this information it will be removed.
  • Ever thought it'd be cool to have your art, writing, or challenge runs featured on PokéCommunity? Click here for info - we'd love to spotlight your work!
  • Which Pokémon Masters protagonist do you like most? Let us know by casting a vote in our Masters favorite protagonist poll here!
  • Welcome to PokéCommunity! Register now and join one of the best fan communities on the 'net to talk Pokémon and more! We are not affiliated with The Pokémon Company or Nintendo.
    Register

[Pokeemerald] Following Pokémon

IvanPrikolist said:
After exiting Fiery Path onto the Route 112 on a bike, it becomes impossible to move and the camera becomes bugged. After opening and closing the bag you can move, but the camera is still bugged.
Click to expand...

I just took another crack at this bug, and I got it fixed! For some reason, when I moved the berry trees' object events to the end of this map's list of object events, the bug no longer occurred. I don't know why that fixes the problem, but it does. Just pushed that to the repos.
 
Hey there,

I just got this working in my decomp and I absolutely love it! However I seem to have run into a bug where any gen 4 pokemon sprites appear fragmented and playing the wrong animations (looking left to down repeatedly):

https://imgur.com/Pez6RCE
https://imgur.com/y9Pm0U2

Gen 3 pokemon are fine however:
https://imgur.com/zsrwBgS

I can 100% believe that this is a problem on my end, but I'm unsure about where in the code the problem lies. My initial thought is somewhere in oject_event_anims.h, but nothing so far.

Any help is appreciated!

EDIT:

Of course I figure it out almost right after I post this lol. My spritesheet_rules.mk must've gotten reverted at some point - copying a fresh copy from your repo fixed it.
 
Last edited:
Just pushed a couple of fixes:

- When the player is standing on stairs one tile north of the follower, the player was effectively standing on the follower's head. A similar bug to this, where the player and follower's positions were switched, was fixed awhile ago. Both versions of this elevation issue are fixed now, thanks to Karl once again for noticing and fixing this other case.
- The follower_face commands had a potential for softlocking the game if they were used while another object event that had the same local id as the follower was on screen. This no longer happens. Karl pointed this one out to me as well, and I was able to fix it.
 
Hello wiser, thanks a lot for this wonderful mod. But there's a major game-breaking bug that I've noticed. It happens more often on other emulators than mGBA. It happens on mGBA too so its not an emulator specific bug.

When there's too much sprites on the screen (overworld) and you open and change the first party Pokemon, it corrupts the game and you start walking on buildings. It registers you being at other location so collisions and warp stuff gets offsetted too. Also I've noticed that it happens when I switch a small sprite Pokemon (like mudkip) to bigger sprite Pokemon (like rayquaza). My guess on this is, the mountain exit bug you've fixed on previous version happened because of this too. There's too much sprites on mountain's exit and it causes the bug. Moving the berries was a temporary solution and it worked. But this can happen everywhere in the game because new following pokemon can be spawned everywhere in the game, and when is is spawned where there's too much overworld sprites are shown, the game may get bugged. I don't have an idea on how to fix this, but checking the code of changing following pokemon on overworld might help. By the way, the bug is recreatable. I will post the steps when I'm available.
 
Just pushed a more efficient version of the daycare fix and fixed a graphical bug that would occur if you tried to rapidly get on and off of a bike and kept on making the follower go into/pop out of the pokeball over and over.
GokhanP said:
When there's too much sprites on the screen (overworld) and you open and change the first party Pokemon, it corrupts the game and you start walking on buildings......
Click to expand...
I'll see if I can find a fix for this bug. Thanks for pointing it out!
 
GokhanP said:
When there's too much sprites on the screen (overworld) and you open and change the first party Pokemon, it corrupts the game and you start walking on buildings....
Click to expand...
I think I've fixed this now. I just pushed a couple changes, one of which being how the local id of the follower is handled. Hopefully that clears up this problem. The other change was more cosmetic, where the follower now goes into its pokeball when deposited at the daycare.
 
Hey, thanks for making this! I'm having new person issues getting it working, though and was hoping I could get some help. I've started with a fresh pokeemerald install, cloned and pulled the 1-3 branch as per the acquisition step and then accepted all changes from the incoming branch using Visual Studio Code's merge tool before committing. When I run the make command, I get the pictured error [PokeCommunity.com] Following Pokémon
I'm very new to this so no doubt I've missed something that's should probably be pretty obvious. Any help would be massively appreciated!
 
j5225766 said:
Hey, thanks for making this! I'm having new person issues getting it working, though and was hoping I could get some help. I've started with a fresh pokeemerald install, cloned and pulled the 1-3 branch as per the acquisition step and then accepted all changes from the incoming branch using Visual Studio Code's merge tool before committing. When I run the make command, I get the pictured error View attachment 167155
I'm very new to this so no doubt I've missed something that's should probably be pretty obvious. Any help would be massively appreciated!
Click to expand...
This is happening because I haven't updated the repo to the most recent version of pret's vanilla-pokeemerald repo. They updated the name of the function CameraObjectReset1 and CameraObjectReset2 to instead be called CameraObjectReset and CameraObjectFreeze.

To fix this, you can either change every instance of CameraObjectReset1 to be CameraObjectReset and every instance of CameraObjectReset2 to be CameraObjectFreeze, or do the opposite. You just have to make all uses of this function use the same name.
 
You must log in or register to reply here.
Back
Top