Points of Required Attention™
Please chime in on a proposed restructuring of the ROM hacking sections.
Views: 88,501,470
 Main | FAQ | Uploader | IRC chat | Radio | Memberlist | Active users | Latest posts | Calendar | Stats | Online users | Search 04-29-24 03:12 PM
Guest: Register | Login

0 users currently in SMW Hacking | 1 guest

Main - SMW Hacking - RAM Address To Mario's OW Direction? New thread | New reply


Sparx
Posted on 08-16-07 06:32 AM (rev. 2 of 08-16-07 06:53 AM) Link | Quote | ID: 62842


Cheep-cheep
Level: 33

Posts: 198/198
EXP: 220685
Next: 8494

Since: 02-24-07
From: San Diego, CA

Last post: 6101 days
Last view: 665 days



Also posted this on SMWCentral, but:

Does anybody know the RAM address to which direction Mario's goes after he beats a level? Because it's very easy to activate multiple events on beating a level (my 1st level has four different exits, each activating a separate event), but Mario can't actually move. I'm just curious, because my alternate method would be to Enable the other two directions at the start, then have a Silent Layer 1 event connect a 3rd and fourth path to the level. So, yeah?

And on a completely unrelated note, why do RAM addresses to X and Y positions usually take 2 bytes?

____________________
Don't even think about it!
Think about what?
*Shoves iPod in mouth*

Current SMW Hack Level[Redrawn Hack]: Sandy Shoreline 2

mikeyk
Posted on 08-16-07 08:10 AM Link | Quote | ID: 62857


Paragoomba
Level: 22

Posts: 51/74
EXP: 49991
Next: 8359

Since: 06-11-07

Last post: 6050 days
Last view: 4126 days
Posted by Sparx
And on a completely unrelated note, why do RAM addresses to X and Y positions usually take 2 bytes?


A byte can only have values from 0-FF. That's only 256 possibilities. We need more than 256 possibilities to keep track of something like Mario's position in the level.

Main - SMW Hacking - RAM Address To Mario's OW Direction? New thread | New reply

Acmlmboard 2.1+4δ (2023-01-15)
© 2005-2023 Acmlm, blackhole89, Xkeeper et al.

Page rendered in 0.018 seconds. (339KB of memory used)
MySQL - queries: 42, rows: 63/64, time: 0.015 seconds.