I was just saying that because when you use your sheets, the lines of hex are very long and not seperated each 6 characters, (which I cannot complain since you made life easier)
That is why I was curious though ^^
They're long like that because it's far easier to format them that way then the standard Word per line format, at least in terms of the Shop fixes and stuff where I'm building all the code myself. It looks messy but it doesn't affect performance and I don't feel like dropping 2 hours to make something no one will ever see look pretty.
But yes, the hex will be formatted however you drop it into the box. You want it pretty, make sure its pretty before you push the button.
The standard, as far as I've been able to tell, for those XML files, is to indent two spaces for each inner level. So:
<Patches>
<Patch>
<Description>Text</Description>
<Location>
Hex
</Location>
</Patch>
</Patches>
That'd be useful, to keep the correct formatting. Otherwise, I'd prefer doing it by hand. A big file of patches without any space indenting? D:
I can easily make the program do that for at least the tags as a quick v1.1 release when I'm less lazy.
However, this program already concatenates a new line before it adds your newest patch, so it ends up looking like:
<whatever the fucking XML header is here>
<Patches>
<Patch name="My Little Pony">
<Description>Fuck it I'm not finishing this meme.</Description>
<Location file="FUCKTHEINTERNET_BIN" offset="Yourmom0">
00000000
</Location>
</Patch>
<Patch="Glain's really picky!">
<Description>Meh, changing it's easy anyway."</Description>
<Location file="FORMATTING_OCD_OUT" offset="yuhateme">
00001000
</Location>
</Patch>
</Patches>
The only thing I wouldn't be able to make indent is the hex unless I made an infinite-entry array that split your Hex every 8 characters on a loop then concatenated spaces to it... which I guess wouldn't be hard either.
If people really care I'll add that to a v1.1 release.
