Kodewerx

Bits 12 and 14 (0x1000 and 0x4000, respectively) are unused. I am not certain why Nintendo decided to skip those. Perhaps it's due to the way they setup the hardware and/or they had additional switches configured in the early design stages.

_________________
I have to return some video tapes.

Feed me a stray cat.

What about the Mic? Do you think that it could send out like a High Pitch and Low Pitch flag with 0x1000 and 0x4000?

_________________

That be nice if we could use the mic as an activator.

_________________

I could just see the code potential in that.

"Scream for full health"

_________________

LMAO

_________________

If you sneak in a "voice chat always on" code into the "scream for health" code....

You will have abundance in lulz!

_________________


<EggWerx> MetalOverlord: Dsman and lemmayoshi will be used for taco meat, ask mo he knows me.

I dont understand how to combine buttons together. could you please explain?

Seems clear to me!

How do you use bitwise AND with hex

we figured it out, we don't need help any more

Windows Calculator in Scientific Mode and/or learn your bitwise arithmetic.

The mic is not on the button registers, nor is the touch screen.

_________________
I have to return some video tapes.

Feed me a stray cat.

Just use Baphomet's or My programs to create a joker code for you

as for hex

http://www.lyzrdstomp.com/binary/hex1.html

thx but i figured out bitwise AND finally

Any way to perform an 8-bit compare (==) other than padding the 16-bit if statement with 2 0s.

That won't work actually.

Example:

Addr Val
0000 ff
0001 00

8-bit compare to 0x00 will return true, but if you do a 16-bit compare with the 0-pad (0x0000), it will return false.

Yes, 8-bit conditions are supported with the 'mask' portion of the value. Use 0xFF00 as your mask, as it will mask out the upper byte, or use 0x00FF as the mask to mask out the lower byte. (Remember, the mask is inverse. Logically it will be ~0xFF00 or ~0x00FF) And you must keep the address aligned to 16-bits, or you will have some weird shifting problems with the data.

_________________
I have to return some video tapes.

Feed me a stray cat.

Thank you again Parasyte.

can you hack the d6~d8 codetypes so that they do not modify the offset?

I could, but it would be 'easier' (and compatible with all AR versions) if you used the DC code to add 0xFFFFFFFF (0xFFFFFFFE, 0xFFFFFFFC) to the offset right after the D8 (D7, D6) codes type.

ok, thats what I have been doing. I Also have a problem with a code I am trying. I know I have the right address because I have modified it with one of the constant write codes. here is my code so far:

The lowest 3 bits of the value at 22188479 hold the ammo. The upper bits hold some status flags and info that CAN NOT be written to without affecting the game play. If I ORR the value with 0x7 (111b) then the lowest 3 bits will always be on and ammo will be maxed out. there are 50 units so I loop 50 times to get them all (I have also tried this without a loop on one single unit with no luck). I applied the DB code fix and loaded the value into the data register ORRed it and write it back. The next unit's data is 0xE (14) away. The DB increments the offset by one and then I add 0xD (13) to the offset to get a total of 0xE (14).

Is there a flaw in my logic? or is there a flaw in the way I set up my code? When I run the game with this code, absolutely nothing happens to my ammo. Its like the 'Dx data' is not getting written back into the address. It also causes some black lines across the screen

Just for info, what game is that code for ?

Edit :
Also, you shouldn't loop 50 times, but 49. The number in the C code data is the number of time to repeat.

For exemple 0x00000000 means no repeat (it doesn't mean 'skip codes', so the codes are still executed once).
0x00000031 (=49) will mean : execute the code once, then repeat the codes 49 times, so in the end the codes will be executed 50 time.

(But I doubt this is the actual problem that makes your code not work properly)

Edit 2 :
Erm... That 22188479 address seems quite wrong... I guess it should be 02188479 ?

Yes. I find that people are getting confused quite a lot about the code types being a part of the address.

_________________
I have to return some video tapes.

Feed me a stray cat.

Also, be aware that one thing that still could prevent the codes using the hacks I made from working properly would be the game having a 'custom' (m) code. As I don't know what game you're using, I can't verify that. But a 'custom' (m) code should (would) mean that the code handler moved from its default place, hence the hacks I made won't work (as they are patching the 'default' location of the code handler, which is used when no (m) code is entered).

As we speak I still haven't gotten what the values of the custom (m) code do (even if I tried more than once...), so I don't know where the code handler is located when a custom (m) code is used. But I'll surely get more infos about that once I'll have the trainer toolkit in my hands !

And, well, even if I tested my hacks, their are still chances that they won't work properly for every cases. I recall having tried the ORR code on Parasyte's universal activator 2 address, and I didn't get the expected results (it was like the ORR hack wasn't applied, so the D4 code type was still using ADD), but - shame on me - I didn't bothered checking what was the problem back then :/... I might try some new tests soon to verify everything is working as expected.

Awesome, It wasn't that I meant to add the code 'type' into the code, I just copy pasted and plain forgot about the codetype (can you tell I am a true programmer at heart?). I 100% guarantee that is most likely the problem. There is no M code and this is for advance wars ds. Will post an update if thats the problem. also, thanks kenobi for the heads up on the loop amount too.

EDIT: Fixed the problem, BUT I still get the black lines across the screen so I'll try putting it in a joker code

Anything that screws with the screen is typically the code handler taking too long to finish its job.

And your signature is HUEG LIEK XBOX. It is eating my screen. Fix it!

_________________
I have to return some video tapes.

Feed me a stray cat.

Fixed the code by adding a joker so it only glitches when it's used. Also fixed the sig. Z3R0 made me one, then the other shortly after and I couldn't see it go to waste as he is my Bro was big though...

Good to hear the code worked.
About the black lines, you might want to make a custom asm routine to make the job, it'll take way less cpu time and could fix the problem...

Would you mind sending me an AIM or ICQ or IRC via PM for discussion about things like these later as to not clog the forums? While my questions do pertain to the 'code types' I don't think it belongs here and since you and para are usually the only ones able to answer these types of questions it is probably better to do so over IM than create a new thread or clog up this one.

About the ASM routine, I don't know how to find a free area to place it. care to explain?

I honestly think this thread is a good place to discuss about AR codes creation/problems. There are no clogging or whatever, as any inportant information I'll add will be updated in the very first post. Also I'm always reachable using PMs if you prefer it that way.

Now, no need for free space for the asm routine, just use the hack #4 I made (one of the listed advantages of this hack is "- no need to find free space to store your asm routine."). If you need a step by step, I can provide it.