This repository has been archived by the owner on Sep 10, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fixed Offsets for the new Game Update.
- Loading branch information
DarkIrata
committed
Nov 22, 2016
1 parent
6fe6153
commit ddf27ab
Showing
4 changed files
with
13 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When the hell did the game update!? Why the hell did they have to change offsets too damn it? Oh well... Just a minor setback I guess... Btw, I will also start assisting with development if you don't mind
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Und, bist du Deutscher? Ich spreche ein wenig.
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dont now. Some people reported problems. Looked into it, and that's what it found.
I'm appreciating every help i get, since i dont have much time working on this project.
And yes, i'm from germany.
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So I'm going to assume that I don't have to start finding new offsets then. Sweet! I am trying to get the offsets for armor and equippables now and I will make a pull request with a file that contains the offsets. I'm not that good with C#... I've been learning with your code
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No problem, we all have to start somewhere. :)
The accessory offsets should be around the first block after the colors.
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know the armor is right near the first quick slot because I've edited armor before. I will get my dump/inject workspace ready and start testing
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And I've also seen the first slot of accessories too
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also have one more thing to say. Be VERY careful when editing the header of the file. You can crash your Wii U if you edit the wrong thing
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Already have the Header informations. 1 Byte looks like is the save version number.
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the offset for a 1 character name for the save version number?
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
0x01 => (MAYBE) Save Version
0x02 => Name Length
0x03 => Name start
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
0x01 is 15 for a 1 character name. Is this what you have for that offset?
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope. 0x02 is name.
0x01 is 15 for all chars from the new version. Last version was 13
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have 01 at 0x02 though. That can't be right
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copy me your bytes from 00 to 0F
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
00150131000100000100640064000000
The character's name is 1 btw. I was testing with name lengths
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's correct. 31 => Char for 1 and 01 at 0x02 is the length of the char name. 1 char
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to ascii, the start of the name is at 0x03
I will also copy over the first line of my other test characters to show you that 0x02 was correct when you first had it
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Name: 12
Hex 00 - 0F: 00150231320028000001006400640000
Name: 123
Hex 00 - 0F: 00150331323300040000010064006400
Name: 1234
Hex 00 - 0F: 00150431323334002C00000000640064
Name: 12345
Hex 00 - 0F: 00150531323334350014000001006400
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
http://i.imgur.com/r2ca2gF.png
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So 0x02 is name length and 0x03 is the start of the name depending on it's length. Well, that sure as hell helps when dealing with the inventory and trying not to crash the Wii U LOL
ddf27ab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep. That's why it's a hell of a fun to work with the offsets for this game... and why i dont use hardcoded offsets except for the name length and name start offset.