Jump to content

Recommended Posts

Posted

Hi, I was wondering if there's a way to disable the Rotom Dex nuisance entirely and permanently? I just beat Guzma at Malie Garden in the game and it won't shut up with its "advice". I couldn't find an option for doing so in the PKHex event flag editor, and google showed no answers for me. Would be happy just to have a black bottom screen again, don't care about lotos or need the map there. Thanks.

Posted
bool __fastcall Savedata::FieldMenu::IsVisibleRotom(int a1)
{
  return (*(a1 + 0x30) & 0x8000000) != 0;
}

FieldMenu save chunk is at 0x4600 in US/UM. add 0x30 (-0x4 for memory object) results in 0x462C.

Data[0x462F] &= ~(0x08);

set the 4th bit of that offset (0x462F) to zero in a hex editor

ie 4F -> 47

  • 2 years later...
Posted
On 2/14/2018 at 1:32 PM, Kaphotics said:

bool __fastcall Savedata::FieldMenu::IsVisibleRotom(int a1)
{
  return (*(a1 + 0x30) & 0x8000000) != 0;
}

FieldMenu save chunk is at 0x4600 in US/UM. add 0x30 (-0x4 for memory object) results in 0x462C.

Data[0x462F] &= ~(0x08);

set the 4th bit of that offset (0x462F) to zero in a hex editor

ie 4F -> 47

What exactly does this solve?

I changed the value of 0x462F from 57 to 47 and I'm not seeing any changes.

Rotom is still terrorizing me with his advice.

I know it's been almost three years and I'm sorry. It's just that I couldn't find any other clues anywhere.

Posted
58 minutes ago, PorgoLorgo said:

What exactly does this solve?

I changed the value of 0x462F from 57 to 47 and I'm not seeing any changes.

Rotom is still terrorizing me with his advice.

I know it's been almost three years and I'm sorry. It's just that I couldn't find any other clues anywhere.

If 57->47 was done in decimal

Spoiler

You weren't zeroing out the he used in his example
image.png

(also other bits changed..)

 

If 57->47 was in hexadecimal

Spoiler

image.png

 

His example:

Spoiler

image.png


Regardless of which value you did, you reduced the wrong bit...

Posted (edited)
20 hours ago, theSLAYER said:

If 57->47 was done in decimal

  Hide contents

You weren't zeroing out the he used in his example
image.png

(also other bits changed..)

 

If 57->47 was in hexadecimal

  Hide contents

image.png

 

His example:

  Hide contents

image.png


Regardless of which value you did, you reduced the wrong bit...

I see. Not that I get the knowledge behind all this, but this makes it a lot clearer.

I was using HxD editor to edit the file, but that didn't show the single bits. I'll try it with something different.

Thank you.

 

edit.

So I tried it out.

I changed this

image.thumb.png.11b2883a36dde1e773e07d578f4ea417.png

to this

image.thumb.png.986a99d423789973d2133635e81913b6.png

 

That should do the trick right?

I changed one bit to 0 and  got 47, but my 4th bit was 0 to begin with so I'm not sure.

I don't know why mines not 4F but 57 though.

Edited by PorgoLorgo
  • 3 years later...
Posted

For anyone who stumbles upon this, the offset is 0x27CC. Use a hex editor and change the value from 80 -> 00
This will revert the bottom screen to a black screen as it was pre-obtaining Rotom. Finally, it will no longer spam chat messages at you.

The FieldMenu save chunk located at 0x4600 seems to only be for the button menu that opens up when pressing X. There are a few stored values here related to Rotom's affection and Roto-loto (source: [USUM] Rotom Pokédex - Pastebin.com) but the actual flag to disable Rotom on the bottom screen is at 0x27CC.

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...