I wanted to test the NTE items to see if the NTE has any rares and if its item list is the same as the list in V1, but since I can't drop items on PC or use commands on the NTE to create my own, I have no easy way to figure out which items the NTE supports. Hopefully it's possible to get commands w...

Oh i know my unitext editor can't open dc files, i striped out the console code since it was targeted at blueburst specifically for users on schtserv, I could return the console code, as ives said it read psox files and adapt it to read psodc pretty easily prob. All the text files are, are pointers ...

but i already have a working pmt builder for both gc and bb lol. Well knock yourself out i guess.

so you honestly feel like there is any benefit to opening itempmt and itemrt when neither of the files really share any commonality and do distinctly independent things.

The only reason i open the itempmt and unitext together is because one has an influence on the other when editing.

They are on later versions of pso. And well when porting the ui functions, arrays etc i prob missed a few things. I could have sworn schthacks old unitext editor which my code is based on, read console version files, i just didn't include the ability to in my program, prob wouldn't be too hard to im...

you shouldn't really be reading them as raw hex, i don't even know where they are as raw hex, i just load them all in to string lists, you realise the unitext once you decompress it is just a collection of pointers, pointing to the various groups of text. Prob easier seeing it like this so you know ...

TweapData = Record // Weapons data V2 24 bytes ID: Dword; Equip, ATPMin, ATPMax, ATPReq, MSTReq, ATAReq: smallint; Grind: byte; Photon, Special, ATAadd: byte; pad: Dword; End; TItemStarCounts = Record Weapon, Armor, Units, Item, Mag, Specials: Integer; End; TArmorData = Record // Armor data V2 24 b...

you don't, you use the id to call it from unitext_e.prs, my pmt program calls all strings from that file

any added photon colour would behave like the regular colours, it just maps them to the parts on the model with the flags set which is done by the client version, so just like changing the photon colour of a saber in the pmt, the magedit will do the same on mags. The header just seems to define the ...

btw ives the reason why i say the photon colours probably work the way they do is because on psobb and psopc, the mag colours are treated as photons and well if you edit itemmagedit.prs add a few entries it doesn't work untill you increase a simple > = check (in regards to the mags they all show as ...

nothings going to be perfect ives, honestly just getting units working and that's prob as good as you'll get from me unless you can find someone else who has the time to dissemble the exe and find things for me to just patch in quickly (it's not exactly hard, it's just really time consuming). That b...

I've fixed the photon slider, and the grid out of index issue already i think, going to take me a while to track down the unit issue though.

i can't really do much about the reductions or the bullets since they are prob tied up hard coded exe values and i really don't want to have to go digging too much for so little gain, if pso is crashing when you add a unit i prob did something wrong in the unit code rather then it actually not being...

are you using the files i provided?

check for read only on any of the files

Epic! 8-) I thought of one more thing that I'm not sure you implemented for BB: do you have a way to patch ItemKT.afs counts in pso.exe so we can add new tekking pictures? I'm guessing if you created one of these new items as a ?SPECIAL WEAPON and then tried to tek it, the picture would show up as ...

the matrix item isn't actually item, but a fail safe for pso. Let me explain, when a hex code does not exist, pso has a fail safe hex code that it redirects to as a way to stop the game crashing for all these items, so no i'm afraid not. without knowing where the texture id list is stored for pso it...

No it's not lol, i've been able to do this for years, the only difference is i have updated my gui so much so that a trained chimp could prob click buttons and add item slots. In psobb new models / textures are easy to do, in psopc not so much, the id's used for models / textures aren't in the pmt, ...

the more cynical people around here will assume i have just edited the unitext and replaced an item to make fun of ives, I assure you this item occupies item hex code slot 000108 and uses an orange photon colour i added for lolz, no offense intended by the name, ives is a bit of a little dictator so...

My first little test anyway, inserted an id just before the mags, mag names are all correct so that's a good sign
Ignore the weapon being unequipable etc for now, i set no stats, this was a name and description test.