Well…. It’s been a long journey of trail and error but I’ve finally been able to correctly parse the Unique Item data file for Last Epoch. I have checked the project into a GitHub report at https://github.com/chaoscode/LEParser
Next up on the hit list? All the affix data — because you can’t build proper relationships without the full family tree.
I started by hunting through the usual suspects: TextAsset files sitting in nice, comma-delimited rows. Clean format, sure… but they were missing huge chunks of the good stuff. None of the files starting with “Asset” had the complete picture. Classic.
So I pulled the old trick from Part 1.
I extracted every single file from the resource bundle and fired up PowerShell for a targeted string search: “Melee Critical Strike”.
Boom. Found it.
The real treasure was hiding in MasterAffixesList-resources.assets-269961.dat. EHG, you sneaky legends, you almost had me.
Loaded it up, and what do you know? Same slick header structure as the Unique Items list. Flags, null terminators, list name, and item count. A quick manual conversion later and we’re looking at 242 affixes ready to be parsed.
This is going to slot right in and make the parser a whole lot more powerful.
I’m hyped to knock this out over the weekend and level up the project. The endgame goal is crystal clear: deliver a solid, open framework so the entire Last Epoch community can finally get easy access to all this juicy data for selfhosted or online hosted projects.
Down the line? I’m already daydreaming about spinning up a self-hostable API so anyone can run their own instance and pull whatever they need.
Stay tuned, the data rebellion is just getting started.
Leave a Reply