Jump to content

Recommended Posts

Posted (edited)

So I'm trying for to add this memory to the Pokemon

1.jpg.7f02de83aea05a907eafd002490e6fb9.jpg

but once its transferred over to the game it shows

2.jpg.f1d1c05608979ed46be8db183d32c46d.jpg

Is there something else I need to do for it to work for me?

Edited by DayDreamerTori
Posted
9 minutes ago, DayDreamerTori said:

So I'm trying for to add this memory to the Pokemon

1.jpg.7f02de83aea05a907eafd002490e6fb9.jpg

but once its transferred over to the game it shows

2.jpg.f1d1c05608979ed46be8db183d32c46d.jpg

Is there something else I need to do for it to work for me?

Just a few lines of questions that needs to be answer:

What is the origin game of that mon?
Did you set the edits into the PC?
Did you export the edited save from PKHeX?
Did you restore the edited save into your game?
Are you using EmuMMC/Emunand?

Posted (edited)

What is the origin game of that mon?

Shield


Did you set the edits into the PC?

I traded them using a sysbot


Did you export the edited save from PKHeX?

I don't think so


Did you restore the edited save into your game?

no


Are you using EmuMMC/Emunand?

niether

Edited by DayDreamerTori
Posted
7 minutes ago, theSLAYER said:

I injected the Charmander you sent me, and the memory correctly says it grinned. Try receiving another one from Sysbot.

I just tried it again and it still says the same thing as before when I talk to the memory guy.

Posted
8 minutes ago, DayDreamerTori said:

I just tried it again and it still says the same thing as before when I talk to the memory guy.

If you uploaded the correct file, then it is probably sysbot that messed up memory. I'm unsure if it's limited to the server you are using, or the issue is present in all current versions of sysbot.

In any case, this isn't a PKHeX issue..

 

Posted
12 minutes ago, theSLAYER said:

If you uploaded the correct file, then it is probably sysbot that messed up memory. I'm unsure if it's limited to the server you are using, or the issue is present in all current versions of sysbot.

In any case, this isn't a PKHeX issue..

 

That could be, thank you i'll check on that

Posted
12 hours ago, DayDreamerTori said:

That could be, thank you i'll check on that

So here's an answer I got from a dev:

Sysbot doesn't write memories, however receiving a mon via trade does update it's memories.

So the memory you got is probably due to you receiving it via trade..

 

edit: I was told how trading updates memories is how the game behaves normally. So if you want a specific memory, you gotta save edit.

  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...