PDA

View Full Version : Export Engine request



Samarex
September 6th, 2020, 00:02
Would it be possible to get the export Engine (/export) to be in line with PAR5E in the way it names tags.
I.E
This item would export as <thisitem> instead of <id-00001> or a 3 rd level feature named Test Feature would come out as <testfeature_3> instead of <id-00001>.

Sometime there are things that change in a ruleset that requires this to be made in a campaign and exported for a conversation because it takes time to get PAR5E updated for the new changes. For new things this would not be a issue but for fixing older content that was made in PAR5E, it would require manually renaming all the tags so they match original content so it doesn't break existing links in campaigns.

Example, We made changes to the SFRPG ruleset to fix lag issue in the current state. This required rebuilding how the Classes were presented in the core rule book. It didn't change anything in the game it just had the Class record pre built instead of the ruleset building it inside. Worked great and completely fixed the loading lags of the system. But since the were built in FG and exported to be replace the existing Class records in the Core Rule Book, It requires me to go through and rename all the <id0000> tags so existing characters will still work.

LordEntrails
September 6th, 2020, 00:21
So you want the core program to change to support a third party application that is no longer supported or even available? And the rename problems you go through would then affect everyone but you?

Add it to the Wish List, that's the place the Devs request that feature enhancements be added and tracked.

Moon Wizard
September 6th, 2020, 00:39
Rulesets should generally not be built with the assumption that something is named a specific way in the database. We had some early assumptions in the 5E ruleset regarding classes that did this; but we patched the code to no longer assume that. Especially for something that is expected to be built as custom records, such as Classes.

Regards,
JPG

NOTE: Also, moved thread to workshop.