- This topic has 1,129 replies, 26 voices, and was last updated 10 years, 12 months ago by
.
-
Posts
-
Found the problem. I DIDN'T want to click yes when the dialogue for banks came up. It essentially erased all the portraits and sprites by clicking yes. Fixed now.
Hmmm, expanding the rom didn't move addresses around did it? I was in the process of mapping what addresses changed what colors in the towns/castles/forts etc, but now those addresses don't seem to exist at the values I mapped out!
— Changing Town Colors
Credit: MiDKnighT
Town colors can be changed by playing with the pallettes at 0x3C665 to 0x3C66F. Simply use the NES color palette to know the colors:
These don't exist at these addresses anymore. They've been moved somewhere else :)
Same for sprite color, its been moved!
Yes those were on the system page before which has moved. You'll have to make the changes at 7C… and FC… (both).
Something is royally messing things up. ALl the portraits go crazy and sprites start changing and I go through warps only to be transported to different towns all over the map! Give me a sec to see if it was something I did…
Hmmm, must be my savestates. They don't seem to like the new rom code!
Oh ya… I forgot to tell you that. The new mapper will break all your existing save states. :|
Hey Niahak,
Any word on whether DoaEditor will support the new text banks (0A and 0B). I wouldn't think it would be too hard for you. Just the same text bank code but using two additional locations. Although we'd only want to use these text banks if the ROM was 1MB.
Let me know if you have any questions with it.
Not impossible to do by any means. I've been sick lately so I haven't had the motivation to work on DoaEditor or my newest side project. Hopefully I can get the chance to look at 0a and 0b this weekend.
Ouch, I had a nasty cold a week or so ago. Fortunately I had a flu shot so didn't have to deal with that. I hear ya on the motivation thing. I go through phases… Sometimes I'm all gung ho about it and sometimes looking at assembly is the last thing I want to do.
Quote:Sometimes I'm all gung ho about it and sometimes looking at assembly is the last thing I want to do.I hear ya. I'm stuck trying to figure out a Chapter 8… I've been on it for weeks trying but not finishing it. Just can't seem to finish those last 6 or 7 battles! Took the day off today and didn't do any editing…
Quote:I hear ya. I'm stuck trying to figure out a Chapter 8… I've been on it for weeks trying but not finishing it. Just can't seem to finish those last 6 or 7 battles! Took the day off today and didn't do any editing…With a huge project like that it's hard to get over the finish line. You get burnt out. I worked on my music cd in whatever free time I had for 6 months. It was so hard to get it done in the end.
Hey guys,
I did a pretty major refactor to support the new text bank and I want to make sure that it still works well with your ROMs.
There is no new support in this release – it should function identically to the last – but it's important that this get tested independent of the new text bank so that I can verify everything works before I add it…
I'd like you to open and save, then make sure the text is still correct afterward. If you have a way to diff files, that'd be ideal. Naturally I've tested it myself, but I can't guarantee it'll work 100% of the time.
The faster I hear back on an "OK" the faster I can add the new bank :)
Well, it froze the rom after expansion and attempted to access the duel text if that is what you're asking. It might not be a problem w/ DOAEditor, it might be a problem w/ MiDKnighT moving the code… as it ALWAYS freezes at the end of the duel no matter what text shows up.
- You must be logged in to reply to this topic.