Negative Offsets & ASM

???
It didn´t need fixing.

Yes it did... for some reason it was this before I changed it.


No Migrate God Mode [Bully@Wiiplaza/ Welohabi]
2817E372 00000002
C0000000 00000004
3D40814C 3D808000
818C2880 1D6C0280
7D4A5A14 39800001
998AD947 4E800020
E0000000 80008000
*For use with "No Migrate Master Code"*

You failed.
It was correct because I used negative offsets.
Don´t just undo random stuff you didn´t test.

What? I still don't see what you are talking about.

I used negative offsets to save a code line, that´s why it´s a C and not a B.

814C0000 - ... = address
and not 814B0000 - ... = address

So yeah, please only edit the codes that get reported. I did test everything before putting it like this.

I'm still lost man. If you did this to all the codes, you should not have asked me to look at them again afterwords, because now I'm really confused.

I'm tired of these codes....

All I know is all my personal codes work. I'm done fucking with these....

Why are you lost?
If your address´ second 16bit part is greater than 0x8000 you seem to have to do lis and ori instead of lis and stw with offset, right? This can be fixed by using negative offsets.

Example:
We want to use address 80118191

What you most likely would do:

Spoiler:

What I would do:

Spoiler:

How to:

Spoiler:

We´re done f*cking with these pretty much anyways.

Haha... this stirs up at least 100 more questions for me. Apparently I have been overlooking these negatives in HEX for a while....

So help me here....

-32751 = FFFF8011

but... lis r10,-32751 =? 0x80110000
and... lis r10,32785 =? 0x80110000

What is the difference?

There is none! It gets interpreted as the same. Look, if you convert it back, it´ll show lis r10,-32751 as instruction, even if you used the positive equivalent before.

Lol oh god... I need to go bang my head on something for a bit. I'll be back.


How do I know if I'm using positive or negative then?

You don´t.

It´s like saying:
What do I need to do, to get my number decreased by 1?

You could add -1 or substract 1. Nobody will figure out for sure what you really did...

Another example:
Which value is 0xFF?

It´s signed -1 or unsigned 255. Nobody knows what it is. It only depends on how it´s defined or what makes sense for it the most.

So how does the ASM know to use either the signed or the unsigned value?

I thought -1 was FFFF....

I don't really know what signed and unsigned mean either...

And why can't I write anything bigger than 0x7FFF in the offset ..... You would think I could go to 0xFFFF ?

I never worried about any of this until now.

Hex values can represent negative values or not. You only see the difference if you look at the decimal value. Signed means that there are negatively interpreted values and unsigned means there aren´t. Example in my post above.

You better read about signed/unsigned values on wikipedia or so then.

I don´t know why you can´t use offsets bigger than 0x7FFF but you can achieve the same if you go negative. Remember to increase your upper 16bit so that you can substract and save an instruction.

So back to the god mode....

No Migrate God Mode [Bully@Wiiplaza/ Welohabi]
2817E372 00000002
C0000000 00000004
3D40814C 3D808000
818C2880 1D6C0280
7D4A5A14 39800001
998AD947 4E800020
E0000000 80008000
*For use with "No Migrate Master Code"*

814C0000 - D947 = 814B26B9 WRONG

it is supposed to be this i think...

814C0000 - 26B9 = 814BD947 RIGHT

Nope.

You can NOT type stb rX, 0xD947 (rY) because it´s greater than 0x7FFF.
What it´s instead: stb rX, -0x26B9 (rY).

That´s why I´m right:
0x814C0000 - 0x26B9

oh shit i get it now

haha,

Guess it´s solved.
You can post anyways even if it´s closed.