Acmlm's Board - I2 Archive - Rom Hacking - megaman 6 editor?
| User | Post |
dan
Posts: 600/782 |
Yes, the values are slightly off, because I may have been looking at Ice Man's data instead. I thought you already knew about the enemy table, so I never included it. |
NetSplit
Posts: 48/117 |
At $1C308 you have the table for the first checkpoint. This table controls which screen Mega Man respawns on, after he dies.
This table actually starts at $1C2FB, since the starting point in the level is a checkpoint; it's important to keep this in mind because if you move the Wily stages, this data needs to be changed.
At $1C2E5 you have the table for the screen numbers which activate the checkpoint.
This table actually starts at $1C2E4. I wasn't aware what it did, only that it was pretty much a copy of most of the table at $1C2FB and that it needed to be kept the same for things to work properly. 
At $153BD you have a table which contains the scroll byte to start at.
This table actually starts at $153B0.
At $1540B you have a table which contains the first screen ID in the scroll byte selected for the checkpoint.
This one starts at $1540A. It's another one that's pretty much duplicate data, so I've just been using values identical to the table at $1C2FB.
At $15423 you have a table which contains a value that is the screen ID (as used in the table at $1540B), plus the amount of screens in the scroll byte selected for the checkpoint.
I didn't know about this table at all since I didn't know what the duplicate tables did and thus didn't even know this table was necessary. If I had to venture a guess, I'd say it actually starts at $15422.
Some of this information may be slightly inaccurate, as it's been a while since I worked with this data.
Where's the table at $153D3 in your list? It tells the game where the enemies start at for the checkpoint; these values should be set to the slot number of the last enemy on the checkpoint page. That way, it knows where to start when you go to the next screen as well as what enemies to place on the checkpoint screen when you beam in. FF means no enemies are before or on the checkpoint stage.
Heh, all of your tables were slightly off. I think it's kinda odd you kept missing that first byte, since it's the byte for Cut Man. It's not so odd that you missed the earlier values (where the table was off by more than 1), though, since they're not AS important. I think my data is all correct; if not, then it's probably off by 12 decimal, but this shouldn't be the case. Thanks for letting me know what those 2 tables did and about that third table. Oh, also, some of the tables overlap because the last 2 bytes are pretty useless. I'm pretty sure the game doesn't use any of this data for stages 0A or 0B. |
Fx3
Posts: 22/80 |
Yes, once the user touches the stage scroll info, b00m... :| It's a _must_fix_ issue. |
dan
Posts: 597/782 |
Ok. Here's how it goes:
At $1C308 you have the table for the first checkpoint. This table controls which screen Mega Man respawns on, after he dies.
At $1C2E5 you have the table for the screen numbers which activate the checkpoint.
At $153BD you have a table which contains the scroll byte to start at.
At $1540B you have a table which contains the first screen ID in the scroll byte selected for the checkpoint.
At $15423 you have a table which contains a value that is the screen ID (as used in the table at $1540B), plus the amount of screens in the scroll byte selected for the checkpoint.
Some of this information may be slightly inaccurate, as it's been a while since I worked with this data. |
Fx3
Posts: 19/80 |
You were completly off-topic! 
Well, Megaman1 is weird, due to its ROM size (go figure), hence it's very compacted. On other side, Capcom opened the eyes for Megaman2 - much easier to understand its structure and... uncrunched. I'd say it's a lot easier to support MM2 than MM1 in a _same_ romhacking tool. |
NetSplit
Posts: 45/117 |
Right, they have a thickness of 0. They show up in Visine, though, probably due to the way Fx3 has it draw them. Those special objects are pretty unique; you can't use them for anything but what they're currently being used for because there's some code that prevents it. It's pretty strange. They're also similar to the popping block special objects, which can't be used for anything but popping blocks because of the way popping blocks work. Weird stuff.
And as for checkpoints, well yeah, there's the stuff that tells it where the checkpoint actually is, but I thought that was a given.  I wasn't aware that it had a list for which room order byte to start at; are you sure that's not the same byte as the location of the checkpoint in the level (making it only need 3 lists of values instead of 4)? |
dan
Posts: 594/782 |
Yeah, Rock and Roll uses the room pointers. I figured Visine did, but I guess that would explain the lack of editing for the room order on those stages. There are the two bytes you mentioned for the checkpoint, one for the scroll byte to start at, and the enemy data to start at.
There are also another two at least, one of those is for the room order data to start at, and one is to set which room activates the checkpoint. (I believe, I don't have the data in front of me at the moment)
There's also one for which room you appear in after you die, but I think that is supported by Visine. (It's either that one, or the checkpoint activation byte) I don't know about a byte for the special object data, so I should really look into it sometime.
I don't know about the special objects in Fire and Wily 1 stage are for. (I never even noticed them to tell the truth, I only thought there were a few special objects - left/right door, g-block) That'll be another thing to look into, as I think Rock and Roll's special object editing may be too rigid to support unknown values. (I knew that would bite me in the ass  )
Edit - I know now why I didn't see them before, the dimensions of the objects are really tiny. They have zero height. Not sure what that is all about really. They also seem have the ID of right-sided doors.  Bizarre. |
NetSplit
Posts: 42/117 |
Well, it probably was set up without using the list of pointers for where each screen is located; in Cut/Wily 1, those pointers are out of order, so ignoring the list means room order editing wouldn't work properly. They're probably out of order in Guts/ending, too, but I'm not sure about that. As for checkpoints, there should only be 2 sets of values you need (each set having 36 values for all 3 checkpoints in al 12 stage IDs, if I recall correctly) for scroll byte and enemy number to start at, and another set which is optional depending on some other data which controls special objects. This is, of course, in addition to which screen to start on at each checkpoint and the Y coordinate to beam down to.
Speaking of special objects, did you ever figure out what those special objects underneath fire pillars in Wily 1 and Fire Man's stages are for? I haven't a clue. Everything seems to work the same regardless of whether those special objects are there or not. Any ideas? |
dan
Posts: 589/782 |
I didn't even know that Visine had a room order editor. Although, it seems strange to me that it lacks Cut, Guts, Wily 1 and ending though. Their ordering is fine and easily supportable.
As for the scroll settings I was talking about, were related to the checkpoints. I can't remember the details very well, but there seem to be 5 or 6 values related to scrolling/checkpoint/room ordering. (Some of which are supported by Visine, some of which aren't)
I also forgot that Rock and Roll has the ability to change the sprite pattern table/palette loading data for various screens. |
NetSplit
Posts: 41/117 |
You can change the room order in Visine using P and Shift-P in all stages but Cut, Guts, Wily 1, and the ending (probably because they had 'weird' screen ordering originally and Fx3 never bothered to support them). Visine does, though, lack proper checkpoint editing, since it doesn't support the list of values for which enemy, scroll byte, and special object to use (the last of which is pretty useless, anyway, but the game still needs it because the game's programmers were stupid). And what kind of other scroll settings are there? I'm interested in finding out what you mean. |
dan
Posts: 588/782 |
Rock and Roll was heavily based on Visine (well the data anyways). However, Rock and Roll also has new features that weren't found in Visine, such as the room order editor, the ability to tweak more scroll settings, the advanced enemy editor that allows you to fix the old problems with enemies at checkpoints when changing the scroll in Visine, and enemy addition/deletion that doesn't corrupt the ROM. (At least, the version I tried, always had problems with it) To say that it is no better than Visine, would be incorrect. 
If you need any of that data for your updated Visine, just ask, or take it from the datafiles in the Rock and Roll data directory.
As for Windows ports of old editors, that's something I was very interested in at one time. I just wasn't sure if there was any interest from anyone else. |
Jigglysaint
Posts: 182/215 |
It would be very nice to see updated ports of old DOS editors. One of the troubles, I think, about old editors is that it discourages people from making newer ones for that game. I mean, why re-invent the wheel?
Personally I'd love to see windows ports or remakes of all the old level editors, especially the Zelda 2 one and the Goonnies 2 editor. With the advances of NES hacking, a better editor could be coded to take more advantage of new developments. For example, the Zelda 2 editor doesn't have warp editing, cave editing, or other various things. A better editor can lead to the potential of better hacks. After all, what's a bigger deterent than having to hex edit by hand? I mean, it's great for small hacks, but for the big ones, it's hard to do.
|
Googie
Posts: 373/624 |
Well, hopefully we'll see some up to date MM editors in the near future that'll work good for Win XP like Rock & Roll and that japanese Rockman 2 editor. |
Vurano
Posts: 26/42 |
YES! I can't wait for a windows port of your'e editors, if you ever get around to it. I love the MM series. |
Fx3
Posts: 17/80 |
Yes... inspiration. Or whatever a feedback means... |
turtleman
Posts: 117/119 |
Soo was this thread kind a like inspiration or somthing for ya? |
Fx3
Posts: 16/80 |
Okay, visine wasn't work here in my PC too... until I compiled it with MinGW (Win32). Well, sixtans is as great as visine, but with less features (of stats). Anyways, get ready for a Win32 console version (ya, that's the right words). |
turtleman
Posts: 107/119 |
yes thats the first thing i tried,on account of it workin for me lots of other times too |
Roneo Strife
Posts: 13/60 |
ok but did you try dosbox? |
turtleman
Posts: 104/119 |
Uhm that isnt the problem,IT doesn't run at all on my computer  |
| This is a long thread. Click here to view it. |
|
hukka
