Skip to content

Add and fix 3.30 exports - #10454

Open
vaisest wants to merge 5 commits into
PathOfBuildingCommunity:devfrom
vaisest:330-export
Open

vaisest wants to merge 5 commits into
PathOfBuildingCommunity:devfrom
vaisest:330-export

Conversation

@vaisest

@vaisest vaisest commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Description of the problem being solved:

This PR exports the new 3.30 data. Arcane link and fireball of radiation are included. Radiation seemed to have the stats mapped right out of the box, but for Arcane Link I just copied the flame link definitions. I didn't do in-depth testing for them but afaik this is enough? There were some other supports added, but I don't really know what they are for as they seemed weird.

The first commit contains all of the meaningful changes. The second one contains the results from running the export scripts.

The foulborn map is not updated here since it is based on wiki information. I'll have a look at it at some later time.

Some of the quirks fixed here:

  • bossData: Atziri's skill level rows now start with a level-1 row. The fix points Atziri at the second row
  • essence: the new belt-only CurrencyEssenceUber1 has no mods for the other slots. essence.lua now skips empty slots.
  • legionSprites: AlternateTreeArt went from 6 keys to 4 and lost its frame-art keys. The spec was updated and the script looks the Abyss frames up by Id.
  • bases: BaseItemTypes lost a bool
  • Stat descriptions: the files were renamed .txt → .csd. All references now use .csd, except skillpopup_stat_filters.txt, which seemingly kept its old name.
  • statdesc: GGG typo 1|99# in stat_descriptions.csd crashed the limit comparison. Both parsers now strip the stray #.
  • There were a lot of new stat description functions (someone at GGG seems to like them). This means a lot of small tables contain the strings which are now exported in statdesc.lua:getDescriptionFormatterNames()

Some of these fixes were Opus 5.5 assisted and coded. Especially the spec changes were completely automated.

Steps taken to verify a working solution:

  • Tests pass (except that one broken test)
  • Nothing explodes

Based on #10437

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant