Forum Replies Created
-
Posts
-
Re: the text differences, it's probably something that happened in translation. The chest/party glitches are most likely in the original game(not that I'd expect anyone to check), because reprogramming everything is usually a bit out of scope for an NES game localization.
I don't think the translation team is even in the credits for the game. That's a shame, since it's a very readable script for its time.
That said, the dictionary system was probably added in translation.
So I guess the conclusion I'd come to is more than two programmers and more than two translators.
Game teams only have to be big if you are going all-out (orchestral score, etc). If you look at the credits, most of those people are voice actors, composers, sound technicians, motion capture people – very few actually do the same things they did for a game like DOAE. A 2-d game can still be made by very small teams (like Spirit Engine 2 which was made by two people).
I updated the first post, but just in case you'd rather check here:
Quote:so 0x30D70 begins the list of battles in sequence and ends at 0x30EFF, but noticing Lu Bu's ID is B5 but the battle sequence places him here as B7, a couple others appear like this too.Pang Tong 9A shows up 9D
General 05 shows up as general 08, I edited the character so I forgot who it is.
Several generals have multiple sequential numbers that are acceptable for referencing them. Liu Bei has three, for example.
I never did figure out why those exist. DoaEditor always uses the minimum allowed number, but keeps track of which ones are allowed.
Resolved (and tested). Both were pretty quick fixes and simple oversights on my part.
Sorry about the lost progress :( I assume it's a side-effect of the hex officer names. I guess I never anticipated people wanting to use two-digit numbers (or even hex) as names for generals.
Let me know if there's anything I can do.
Ah, now that I take another look – it saves the currently selected line on export (similar to why it's saved on switching to another line of dialogue). It's horking on whatever that line was for some reason.
I need to go through and add better error handling so you don't lose much/any work when these things happen.
Quote:I can change those yeah, but one thing I found to be quite obnoxious, but I dont know if it does it anymore, is that if I change the name of an officer, it changes EVERY instance of that officer in the text, whether I want it to or not. With changing officers names to the hex values, it might be fine now.This is pretty much unavoidable, since what's stored in the text is actually a pointer to the officer rather than the officer's name in plaintext. I'm trying to come up with a good metaphor for it – it's like the text contains a bunch of labels printed with the name of each officer, and when you change the officer's name all of those labels automatically update.
Quote:Oh, and about our ghost-editing, it tends to edit the line directly next to the current line being edited, but if you click on the new "ghost-text" it reverts to the previous line that was there, but not sure how it gets exported to the rom.Is the other line being 'edited' before or after the selected line? This is actually kind of relevant… I think I may know what's going on and it's related to how the list is updated when you edit a line, but the behavior is kind of confusing to me.
Looks like it's this line that's causing the issue:
"Lu Su, son of
Huang Gai, found
you unconscious[>]
and brought you
back here. You
should go to[>]
[ChangSha] Castle
to thank him. You
might even learn[>]
something about
Sima Yi's magic.
[EVENT-4134]"
The underlying issue is actually very exotic – which is why it hasn't been noticed before.
As my editor goes through a line to turn it into hexcode, it converts officer names, then places, dictionary words, and so on. The issue is that, because as a work-in-progress, your mod has an officer named 13 (multiple, in fact). The editor picks up on the 13 inside EVENT-4134 and replaces the 13 with the code to index that officer's name… and things go downhill from there.
And, since line saving is automatic in the text editing tab, it's not an easy fix :/ I tried changing the order in which I save things and it screws up the text somehow. So I don't want to try and release anything without thinking it through.
In the meantime, could you use an obviously non-hex name for unused officers? It can be anything, as long as it contains a non-hex officer (so if you want to keep them at the top, for example, 0Unused13 or 0U13 would be fine – as long as the entire string is highly unlikely to pop up inside an event code.
OK. I've reuploaded at the same link:
http://www.niahak.org/images/DOAE/DoaEdv098c.zip
Try it once more. This one should pop up an error dialog in all cases.
Does the issue happen on a fresh rom, or only on one you've been working on for some time?
So it's the reverse. Your machine is more of a powerhouse than my own, so I'm unlikely to be able to reproduce your issue.
I switched IDEs/compilers between the last 0.97 and the first 0.98 version. That might be a part of it, but it seems unlikely to be anything you can touch.
Did you try out the new version? It should be printing a message when you run into the error… unless it's somewhere I'm really not expecting, I suppose.
I've uploaded a quick release for troubleshooting that'll provide a better error message when that sort of thing happens, so I can figure out exactly what's going on.
http://www.niahak.org/images/DOAE/DoaEdv098c.zip
It sounds like you're running into some weird timing issues with line editing. Are you on a pretty slow machine?
Whoa. Can you give me detail on what happened when you ran into the "stopped working" bit?
How many lines is it editing at a time? Is this in the taunt/closer section, where you can actually edit both the taunt and closer at the same time?
Sorry about the crash. I'll see what I can do based on the info you provide.
