Purpose of manager_version2?

**leozelig** · August 13th, 2015, 22:30

I am layering my custom ruleset on top of CoreRPG, and I am trying to figure out if I need a "manager_version2" file that is unique to my ruleset. What is the purpose of this file? It seems like it converts (or deletes) existing data from older versions of the ruleset to the latest version. I have posted a couple of updates, but I don't think I have made changes that would require that.

Am I understanding this file correctly?

**Trenloe** · August 14th, 2015, 04:32

Yep, it's to do with version handling - the main things being:

Changes in the campaing database
Changes to characters imported from an older version export.

The gotcha with this is that you'll need to have tracked the ruleset "release" version in the <root> tag of the ruleset base.xml tag.

If you haven't made any changes to the database structure (PCs, NPCs, items, etc.) then you won't need this (yet). But it will be good to make sure you have a specific "release" version set now so that you can tell for future version updates.

**leozelig** · August 14th, 2015, 12:31

Thanks, Trenloe. What would the contents of that file be with nothing to track at this stage?

**Trenloe** · August 14th, 2015, 17:50

There'd be no need for it. Remove the <script> reference from the ruleset base.xml.

**leozelig** · August 15th, 2015, 00:07

Got it, I think I misunderstood your post.

Thread: Purpose of manager_version2?

Thread Tools