Guide On Making Button Activators for All Games (Nooby-friendly)

[REDSOXROX]

Since several people have asked for one. If you don't understand it I'll go into more detail.

How To Find Button Activators

Alright, today we will find button activators for Wii

games.

To get started, please boot a Wii game (any one, I suggest

an earlier release, some good ones would be Super Mario

Galaxy, Smash Bros Brawl, MK Wii, etc)

Now please open up WiiRD. Alright, assuming it hooked right

you can search for things now, which we will do in a

second.

Next open your Windows Calculator.

Now we have all the tools we need. We must use some

resources now.

These are the tables for the button values for all Wii

games.

GCN[Wired]   Wii[And Nunchuck] Classic Controller
L 0001      L 0001      U+ 0001
R 0002      R 0002      L+ 0002
D 0004      D 0004      Zr 0004
U 0008      U 0008      X  0008
Z 0010      + 0010      A  0010
R 0020      2 0100      Y  0020
L 0040      1 0200      B  0040
A 0100      B 0400      Zl 0080
B 0200      A 0800      R  0200
X 0400      - 1000      +  0400
Y 0800      Z 2000      -  1000
S 1000      C 4000      L  2000
              HOME 8000            D+ 4000
                             R+ 8000

Here's how we will find the controller values. In the WiiRD

known search box, type in the value for A on the controller

you want to find. Make sure your search type is 16 bits! In this case, I will use 0100, and a

Wired Gamecube Controller in the first slot. Hold A down

and search for it's value. Now, assuming you have quite a

few results, hold another button down on the same

controller and search for its value. Repeat.

Eventually you should get one result. Left click and poke

this, then copy the first 32 bits. (The first 8 numbers

before the space)

Now we have our controller's code. Let's say we tested it

on Super Smash Brothers Brawl USA and we get 0x804DE4B0 as

the first wired GCN controller's adress. This is correct.

Use this method to find the button activators for all

games. The controller's adress will change from game to

game, HOWEVER THE BUTTON VALUES REMAIN CONSTANT. [See chart

above]

Before you go compiling the address into a code you need to look at the codetypes.

You can either use the 20 or 28 codetypes.

28 has more sanity checks (although 20 should work too) so we'll use that.

After switching the 80 for 28 you'll get 0x284DE4B0



PART 2: IMPLEMENTING INTO CODES

For this part we will be using a code I've made for SSBB

USA, to make it easy for me to explain. Here is the code:

99 Lives (Press L) [REDSOXROX]
284DE4B0 FFBF0040
4A000000 81000000
1428AE64 00000063
E0000000 80008000

Okay. Here is the lines of the code by itself that would

always keep you at 99 lives.
4A000000 81000000
1428AE64 00000063
E0000000 80008000

We don't need to worry about that, just see another guide

on making codes for how to do that.

Here is the button activator line.

284DE4B0 FFBF0040

The first 8 digits is the controller code we found earlier.

You'll recognize 0040 as the "L" button on a Wired NGC

controller.

So, for making a button activator, all you must do is in

the first line of the code, Add the controller's adress,

and then 0000yourbuttoncodehere

Now you can press that button and your code activates.

But, it is usually nice to make codes a bit cooler/safer.

What does this FFBF line in the earlier code do?

It makes it so that you may only press L to activate it.

So, if you press and hold A then L, the code won't

activate.

And, when you want to make  more than one button activate a

code, just add the button values together in a hex

calculator (windows calculator is fine) and implement them

like 1 button.

To find the FFBF, I clicked "not" in the calculator.

For more info on making advanced button combinations please

see http://wiird.l0nk.org/forum/index.php?topic=53.0


But you will need to understand this first.
Edit: Realized I forgot something important on searching for the address

[Thomgame]

Good tutorial, i have already understand but great for others wii hacker  :cool:

[hetoan2]

what are you trying to say paprika?

[Blaster99]

Hi,

he tried to say that the mentioned '0x284DE4B0' in his quote is not an adress, because there is no 80/81/... after the 0x.
0x28 is a codetype.

Bye
  Blaster99

[hetoan2]

oh. I fixed it. Hope he doesn't mind :|

feel free to remove it RSR

[REDSOXROX]

oh. I fixed it. Hope he doesn't mind :|

feel free to remove it RSR

Thanks! Sorry bout that! Nice catch paprika!

[asianking]

this is very useful but FFBF doesn't work for me... i got the button work without FFBF.

[g6flavor]

Eventually you should get one result.

Just like to make a note that there is always more than 1 address for the buttons, to test the address, click on the Memory Viewer tab
tick the ON/OFF box, then push the buttons and compare them to their corresponding values

[REDSOXROX]

Eventually you should get one result.

Just like to make a note that there is always more than 1 address for the buttons, to test the address, click on the Memory Viewer tab
tick the ON/OFF box, then push the buttons and compare them to their corresponding values

Thanks g6 I'll add that when I'm on my laptop
And asianking that's fine codes can be made
Differently :)

[hetoan2]

Moved to collective for easy access.