- This topic has 1,129 replies, 26 voices, and was last updated 10 years, 12 months ago by
.
-
Posts
-
Quote:"Z8??Qong", "Zh5ng Fei"
I had that issue when applying patch 1.3
Yuk, the patches aren't even touching the names. Very strange. Looking into it.
OK what was happening was the "unmodified" file I was using to make patch 1 was truly unmodified. I had only added zeros to make it 1MB. What I found is that when DoaEditor does the expansion it moves text around a little bit. Since Patch 1 and Patch 2 had been expanded with DoaEditor there was a mismatch that caused some problems for the IPS patching. The solution was to use the DoaEditor expansion on my "unmodified" file before making the patches.
Latest version of IPS 1.3 uploaded. No need to copy memory to fix save states but you do need to view the status page of an ally officer and re-save before viewing an enemy status page (the ally status page loads the new memory).
Quote:I have SVN set up for DoaEditor and would be glad to make you an account in case you'd like to tinker with it.If lud doesn't have the time to make major DoaEditor updates then I might be interested in this as well. Last time I looked I couldn't make much sense of the code but with the right motivation I could learn it. I think for most potential modders the guide is pretty scary. DoaEditor has always been the way that we have made the ROM more accessible to potential modders. There's so many great things we can do in the guide but can't do in DoaEditor yet. After a couple more tweaks/enhancement I would probably want to focus my attention on DoaEditor so that it can catch up to all the stuff in the guide if that's possible.
New Integral Parts for DOAEditor:, my 2 cents
*Cave Modfications and correcting the exit points to be moved to the same location.
*Shop Menu Modifier + Price Modifier
*Additional Stat Modifier ie: Politics/Vitality
New Integral Parts for DOAEditor:, my 2 cents
*Cave Modfications and correcting the exit points to be moved to the same location.
*Shop Menu Modifier + Price Modifier
*Additional Stat Modifier ie: Politics/Vitality
MiDKnighT: Added an account for you. Sent you an email with the details. Any questions about the code, feel free to ask here. That way anyone who joins the project later will have the info.
Thank you sir. Let me get my last major DoaE enhancements done then I'll start looking.
I've got Visual C# 2010 Express going and I exported the code. Looking around in it it reminds of using Visual Basic in my college days… I'll have to spend a while toying around with it before I actually try to do something in the real version.
So Niahak how do you test this thing? Do you have to compile it every time you test something?
EDIT: Nm, I see it – start debugging.
The form part is easy…
The backend code, not so much.
Yeah, you'll probably want to explore a bit with how officers are imported/exported.
One easy trick to see how things are related: look for the variable of an existing value (e.g. strText is the textbox input for strength) and see where it is modified by right-clicking then choosing Find All References.
You'll have to add LDR, VIT, POL to the officer object and figure out how to assign them and export them (ParseOfficer method and the ToBytes method on the Officer class respectively).
Unfortunately that early code is from when I didn't even use the visual editor, so the stuff you added will be different from the code that's already there.
Let me know if you have any specific questions.
I looked at Officer.cs and I thought that was for the glob of info about each officer on page 0C (name, STR, INT, etc…) but the info I'm trying to pull is in 0x7aa## where ## = officer ID. Would I still need to put that in Officer.cs or put it all in MainForm.cs ? I was thinking I'd need a new function to pull that data.
Woohoo! I got the LDR, VIT, POL boxes to populate (now I just got to get them to save):
I was able to do it by adding this in list_SelectedIndexChanged():
int ldrlocation = 0x7aa00 + (byte.Parse(o.HexPointerValue, System.Globalization.NumberStyles.HexNumber));
this.ldrText.Text = (Convert.ToByte((entireRom[ldrlocation])).ToString());
int vitlocation = 0x7ab00 + (byte.Parse(o.HexPointerValue, System.Globalization.NumberStyles.HexNumber));
this.vitText.Text = (Convert.ToByte((entireRom[vitlocation])).ToString());
int pollocation = 0x7ac00 + (byte.Parse(o.HexPointerValue, System.Globalization.NumberStyles.HexNumber));
this.polText.Text = (Convert.ToByte((entireRom[pollocation])).ToString());
Now to work on getting it to save…
Save is working now. Added this to savebtn_Click():
int ldrlocation = 0x7aa00 + (byte.Parse(o.HexPointerValue, System.Globalization.NumberStyles.HexNumber));
entireRom[ldrlocation] = Convert.ToByte(int.Parse(this.ldrText.Text));
int vitlocation = 0x7ab00 + (byte.Parse(o.HexPointerValue, System.Globalization.NumberStyles.HexNumber));
entireRom[vitlocation] = Convert.ToByte(int.Parse(this.vitText.Text));
int pollocation = 0x7ac00 + (byte.Parse(o.HexPointerValue, System.Globalization.NumberStyles.HexNumber));
entireRom[pollocation] = Convert.ToByte(int.Parse(this.polText.Text));
- You must be logged in to reply to this topic.