hex editing - need help

#1
Ok, it bothers me that I cannot figure this out.

I assume John or Ben could probably answer this in a split second so I will just go ahead and ask.

If I open a prf with xvi32 and want to edit its contents, I have always been sure to name my .mdo's the same length as the model I am writing over for example...

If in the prf I have a section that says: ‎ 
Weapon: Excellector (1) 00 00 00 00 00 00 00 i997.mdo

it has x number of characters for the name, a certain number of spaces then 4 characters for the model name. ‎  suppose I am running out of ixxx.mdo numbers that will fit and I just want to call it whatever the name of the model is...so maybe something like this:

Weapon: Silvarion 00 00 00 00 00 00 00 silvarion.mdo
No matter how I try, this never works, if I dont keep the proper number of characters in the weapon name followed by x number of spaces and x number of characters for the model name the file breaks. ‎  I can assume this is because SOM is searching for a specific hex slot for the item type and so on, but I guess my question is, do either of you know an easy way to plug in the name you want and the model name you want without breaking the file? ‎  If I just have to remove some of the 00's between the name and the model to get the rest of the file to be on the same hex then thats cool, I can figure that out, but I just thought I would check.
- Todd DuFore (DMPDesign)
Site Founder
Reply

#2
SoM doesn't have that limitation as far as I know. How exactly does it 'break'? Some hex editors do screwy stuff like replace 00 with a normal 'space'. If you can post a broken PRF, I can probably tell you what's going wrong. ‎ 
Reply

#3
Well when i copy a weapon prf and straight up modify it the prf still registers the item but in the editor it does not act as though its a weapon.

I will post an 'original' and 'broken' prf when i get home and my other pc is up and running.
- Todd DuFore (DMPDesign)
Site Founder
Reply

#4
I tried again to be sure, and didn't seem to have this problem. Maybe the Hex editor is inserting bytes rater than overwriting them?
Reply

#5
Did you ever get this solved?
Reply





Users browsing this thread:
3 Guest(s)