Ch1pper, on 13 June 2012 - 03:07 PM, said:
With that said, why would the Text Converter assume that HxD in particular is being used? Does it matter what hex converter is used, as long as it has support for UTF-8 endcoding?
Because that's the one I used when making it, and I'm sure the copy-paste hex features of other editors might format it differently. The rather cheap way I made it basically means the values are hard coded, it'd take a while to make it properly read, say, <bh:00><bh:00><bh:00><bh:83> as one Generations letter from Translhextion, as I'd have to remake all the actions for that. I was too cheap/lazy to have all it stored in an easy to edit text file or such.
I mean, if people use those enough I can try and do that anyway, make my one contribution to Generations hacking a little more useful, but I'd prefer to stick with one hex editor's style if I can, I don't want to add support for something nobody will use if I can.
... this wouldn't even be needed though if there's a hex editor that supports tables with 4 or more bytes per letter. Thingy kinda failed for me when I tried that.