WiiRd forum

Wii & Gamecube Hacking => Wii Game hacking help => Topic started by: benny3t3 on November 20, 2010, 07:34:28 PM

Title: Is it okay to accidentally make a code?
Post by: benny3t3 on November 20, 2010, 07:34:28 PM
While I was searching for the function that makes you lose half of your beads  (the currency in Epic Kirby) after falling in Kirby's Epic Yarn (Please don't take it) I found that nopping the divwu did nothing. I don't really understand that... maybe that was just to find what half of the current value was and then it was subtracted with sub later on was what I thought.
Is there something special about blah. rX,rY,9999 I kept on finding 9999 after many functions that change values..

However, even after nopping any 1 or all of the add/sub codes, I found that nothing changed except that afterwards, I would lose ALL of my beads after falling.

That code couldn't be dangerous/noob-ish would it? the # of beads is stored in r0 and the code I nopped was
divwu r0,r3,r0 or divwu r3,r0,r3
but r3 held 00000000...

and for that matter... why couldn't I find that value?
Title: Re: Is it okay to accidentally make a code?
Post by: dcx2 on November 21, 2010, 03:15:39 AM
Are you sure your breakpoint was set on the right address?  Does a write breakpoint hit after you fall?  Does the value being stored to memory match what you expect it to be (i.e. half of your current beads)?  You can right-click the Step Into/Over buttons or the Show Mem button, to peek at the current load/store address and value.

The 9999 stuff is probably making sure you don't get more than 9999.
Title: Re: Is it okay to accidentally make a code?
Post by: benny3t3 on November 21, 2010, 04:51:01 AM
I saw three different addresses, this one is the one that actually wrote to the value, but after poking, it goes right back to the original value.

It doesn't just flash, it counts down to the value, which means there is something always writing to the value.

Basically I have 3 values:

The one I can write to and see that difference, and that is written to when losing or gaining beads (this is the one I already tested), and two others that are constantly written to...
I 'll take a look at those, and at the previously made infinite beads code.
Title: Re: Is it okay to accidentally make a code?
Post by: dcx2 on November 21, 2010, 03:27:57 PM
So far so good.  Did you set a write breakpoint on that address, and then initiate the action that results in your loss of beads?   If you did, please copy and paste the Breakpoint Registers view into this thread (change it to Text View so you can copy it)

After pasting, while still at the Breakpoint, go to the disassembly tab and right-click the instruction you are on and then click "Copy Function".  Paste that into a spoiler here; functions can be quite long sometimes.
Title: Re: Is it okay to accidentally make a code?
Post by: benny3t3 on November 22, 2010, 09:46:28 PM
I'm trying... It is for some reason hard to get the adress often...

Oh, and I will need to post an image, I cannot copy/paste from inside x11/mono to outside... I don't know what to do for the copy function, we will see.

P.s. how do I insert a picture on WiiRD?
Title: Re: Is it okay to accidentally make a code?
Post by: benny3t3 on November 22, 2010, 10:14:16 PM
I don't know... I think there is something weird about Epic Kirby... I tried using Skiller's infinite beads code (in stage) and it just froze the game... and I cannot find the value for the beads anymore.
Title: Re: Is it okay to accidentally make a code?
Post by: benny3t3 on November 22, 2010, 10:32:19 PM
Same problem that I was having before, I cannot figure it out, I cannot find a static adress.

How can I find where the value is being held if the adress is always changing?
Title: Re: Is it okay to accidentally make a code?
Post by: dcx2 on November 22, 2010, 10:48:51 PM
Did you try both MEM1 and MEM2?
Title: Re: Is it okay to accidentally make a code?
Post by: benny3t3 on November 22, 2010, 10:51:41 PM
Yes.
Title: Re: Is it okay to accidentally make a code?
Post by: Skiller on November 22, 2010, 11:30:25 PM
Quote from: benny3t3 on November 22, 2010, 10:14:16 PM
I don't know... I think there is something weird about Epic Kirby... I tried using Skiller's infinite beads code (in stage) and it just froze the game... and I cannot find the value for the beads anymore.

it will freeze your game if u poke it with the wrong ASM value .. i was telling u to Breakpoint Exacute off the address not just poke it with a random value ..
Title: Re: Is it okay to accidentally make a code?
Post by: benny3t3 on November 23, 2010, 03:23:55 AM
Thanks Skiller. Sorry, I didn't realize that asm was so different.
Title: Re: Is it okay to accidentally make a code?
Post by: benny3t3 on November 24, 2010, 06:04:28 PM
bump?

Can I still take you up on that offer dcx?
I am still puzzled, and I could use the help. I'll post a pic of the registers and their values and the function if you are still willing to help me.

Sadly, I cannot just copy/paste out of mono yet. The copy/paste clip board for mono has not yet been integrated with the osx clip board and so copy/paste is limited to one application...
Title: Re: Is it okay to accidentally make a code?
Post by: dcx2 on November 24, 2010, 06:28:01 PM
Could you copy and paste the text into the Gecko.NET notepad, and save it as a file, and then open the file using a regular text editor that can copy/paste to the browser?
Title: Re: Is it okay to accidentally make a code?
Post by: benny3t3 on November 24, 2010, 07:26:46 PM
I already thought about that, but when I have tried it, the right click function would not work at all on the notepad. I will try it again soon hopefully, but I have some chores. Usually, the right click menu for somereason gets hidden behind EVERY OTHER window so I need to make the window size the smallest possible and right click on the right edge of the window to see it.

I will try that.

In short, I will have to see if I can even copy/paste to the notepad.
Title: Re: Is it okay to accidentally make a code?
Post by: benny3t3 on November 30, 2010, 10:44:18 PM
I have Windows XP again! So, I will be getting you that info now.

EDIT: err, I mean tomorrow, I don't know the password.
(...rrrrrrr...)