You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I just picked this game back up. Amazing mods, but the extended following for the wild area doesn't always work as it should.
If I enter wild area from Motostoke, things seem to work correctly. My Pokémon follow me around and move the same way they would on Isle of Armor. If I switch my party around and place someone else in the lead, it doesn't always work as you would expect. Sometimes it works, sometimes it sends the new Pokémon back to the initial spawn point where it's stuck on the spot, failing to follow me.
If I enter from the Wedgehurt side (Meeting Spot), my Pokémon just endlessly spins around on the spot and fails to follow me. Moving far enough away despawns it, without respawning it behind me. I can walk back over and see that it's still there, forever stuck. I can change the party lead, and it just spawns the new one in front of the meeting spot, where it's also stuck. If I enter camp, it also breaks in the same way upon exit (except the "entrance" where the lead Pokémon is stuck changes to wherever I was standing at.)
I thought it could have had to do with me not having actually unlocked the ability to have Pokémon following you from completing the dojo trials yet, I don't know how much testing has been done on this yet. So I went through it as soon as I could, but that doesn't fix anything. So I guess the mod doesn't care about that.
This happens without any romfs mods active and without any other exefs mods active, so I don't think another mod would be conflicting. This is with the latest version from January 19, to be clear, and Sword 1.3.2, in case Sword vs Shield matters.
The text was updated successfully, but these errors were encountered:
I just tried with synchro mode. When my Pokémon is stuck in place, even if I take control with L+R, it tends to be stuck and I'm unable to manually walk away either. but not always. The times where I'm able to move, if I move away and then L+R out of it, my Pokémon spawns at my feet, and immediately heads right back to the entrance of the meeting spot station where it continues being stuck.
I'm not sure if that's a problem with the synchro mod, or if that's just a symptom of this same problem, but maybe that helps pinpoint the issue.
So I just picked this game back up. Amazing mods, but the extended following for the wild area doesn't always work as it should.
If I enter wild area from Motostoke, things seem to work correctly. My Pokémon follow me around and move the same way they would on Isle of Armor. If I switch my party around and place someone else in the lead, it doesn't always work as you would expect. Sometimes it works, sometimes it sends the new Pokémon back to the initial spawn point where it's stuck on the spot, failing to follow me.
If I enter from the Wedgehurt side (Meeting Spot), my Pokémon just endlessly spins around on the spot and fails to follow me. Moving far enough away despawns it, without respawning it behind me. I can walk back over and see that it's still there, forever stuck. I can change the party lead, and it just spawns the new one in front of the meeting spot, where it's also stuck. If I enter camp, it also breaks in the same way upon exit (except the "entrance" where the lead Pokémon is stuck changes to wherever I was standing at.)
I thought it could have had to do with me not having actually unlocked the ability to have Pokémon following you from completing the dojo trials yet, I don't know how much testing has been done on this yet. So I went through it as soon as I could, but that doesn't fix anything. So I guess the mod doesn't care about that.
This happens without any romfs mods active and without any other exefs mods active, so I don't think another mod would be conflicting. This is with the latest version from January 19, to be clear, and Sword 1.3.2, in case Sword vs Shield matters.
The text was updated successfully, but these errors were encountered: