Thread: Development: Emerald Clock Fix!
View Single Post
  #7    
Old March 7th, 2013 (11:59 AM).
Gamer2020's Avatar
Gamer2020 Gamer2020 is offline
Accept no Imitations!
     
    Join Date: Jun 2008
    Location: Distant Land
    Gender: Male
    Nature: Bold
    Posts: 910
    Quote:
    Originally Posted by ShinyDragonHunter View Post
    Gamer2020, I don't understand how I'm suppose to assemble this, I mean you put "Offset 0200F024 may not be safe in emerald but this can be changed to anything desired." What is that suppose to even mean? If it's not safe, then why can be changed to anything 'desired'? I'm confused...
    Quote:
    Originally Posted by Gamer2020 View Post
    Memory address 0x0200F024 may not be safe. It is the same one used in the Ruby routine. This can be changed without affecting functionality.

    It means that if it turns out the offset isn't safe it can be changed to a different RAM offset and the routine will still work. The offset is the same one used in the Ruby fix but APPEARED to be free in Emerald.
    __________________

    Reply With Quote