This post indicates nothing other than that I can use Rom Corruptor

Experimenting is good. :thumbsup:

Heh, cool.
Man, I didn't know you were into romhacking, I remember when I was a wee Animutation fanboy years and years ago...

Good to see you attempt to hack Ages.  BTW just about everything has been found by me, so really if you have any questions about how the game really works, let me know.  BTW, dungeon data is actually a bit different than overworld data.  Overworld just uses single tiles, but dungeons actually use macros.  How it works is that there are about 16 pages of tiles that are arranged into 15 tile wide strips.  How it works is that the room starts with a control code that specifies whether the following data are single tiles, or macros, which are represented by 2 byte values.  The 2 byte values sort of act like pointers and RLE data together.  If I recall correctly, the first nybble of the first byte is the page number.  So if the macro is on page 16, then it would be an F.  The second nybble of the first byte is where on that row the data starts.  If you want to grab tile data from the 3rd byte in, the entire byte would look like F2.  The first nybble of the second byte is the length of the tile macro.  The minimum is 0 tiles + 3, and the maximum is 16 tiles +3.  If the length exceeds the length of the macro, data from the next line will be used as well.  Also if the macro exceeds the game boundries on screen, the remainder of the data will also start on the next line down.  Keep in mind that the 16th column in the game is never displayed although data can be deposited there.  You will notice that most of the macros all have 00 as the 16th byte in the row.  Finally, the last nybble of the second byte is what row on the page to use.  To sum it up, say you want to get a row of wall tiles.  Now, you could always just defind the tiles individually, but you can only do it 8 tiles at a time, and it costs 9 bytes.  Instead, you could find the row of tiles you need and use them.  Say a suitable row of tiles exists on the 8th page, and the 9th row.  Say also that the row of tiles starts about 2 bytes into the row, and ends 14 tiles into the row.  That should mean the byte pair you need should look like "72 78".  So if the row looked like this:

B9B0B1B1B1B1B1B1B1B1B1B1B1B0BA00

The code is telling the game to do this:  B1B1B1B1B1B1B1B1B1B1B1

Remember that whatever the value you grab, it always grabs + 3 more tiles.  After all, it's compresson, and the least amount of bytes you can save has to be at least 1.

Only a bookmark full of offset goodies for both seasons and ages.  Name your interest, and I should be able to deliver.  Right now I'm going out, but I'll be back later on tonight.  I also know some Z80 ASM, so finding loading routines should be easy to do as well.  In the mean time, do you have Hex Workshop?  I can e-mail the bookmarks to you.  Of course I'd still need to explain stuff, but at least it gives you a general idea of where stuff is.

For that, I can tell you right off the bat that the game's areas are divided into different "dungeon maps".  Each of those maps contain specific attributes, such as level number, graphics sets to load, music, and other special attributes such as if it's under water or not.  In OOA, believe it or not, the graphics of the treasure chests are determined by a bit in this attribute data.  If a specific bit is set, then the chest looks like a chest from the past.  Also the bank of the level data is set too in this attribute table.  I'll e-mail the data now.

Edit:  Er, I need your E-mail so I can send you stuff.  Also don't use the e-mail in my profile as I don't use that one anymore.

Okay I sent the files.