-
September 18th, 2014, 08:26 #1
Restricting An Extension to CoreRPG v3.0.8 (And Above)
Hi Guys,
Stupid question, but what values do I need to put in my Extension File to restrict the Extension to only be used with the CoreRPG v3.0.8 and above.
I know the code:
Code:<properties> <ruleset> <name>d20</name> <minrelease>12</minrelease> </ruleset> </properties>
CheersDulux-Oz
√(-1) 2^3 Σ Π
...And it was Delicious!
Alpha-Geek
ICT Professional
GMing Since 1982
NSW, Australia, UTC +10
LinkedIn Profile: www.linkedin.com/in/mjblack
Watch our games on Twitch: www.twitch.tv/dulux_oz
Support Me on Patreon: www.patreon.com/duluxoz
Past Games, etc, on my YouTube Channel: www.youtube.com/c/duluxoz
-
September 18th, 2014, 09:18 #2
Supreme Deity
- Join Date
- Mar 2007
- Posts
- 20,563
You have to use the release number in the ruleset base.xml file.
I have typically only been incrementing this release number when the database structure changes, not when any part of the ruleset is changed. The reason is that the version number has primarily only been used for data migration code.
Communication in the extension thread has been the main way to let people know which version.
A better version management system would be great, but causes some backward compatibility concerns and requires dev design/code time to make sure it works well in the FG client. Given current Unity push, it's not in the cards short term.
What specific capabilities in 3.0.8 are you using?
You might just need to remind me to increment internal release number if necessary.
Regards,
JPG
-
September 18th, 2014, 09:27 #3
I'm primarily using the Extension package - you know, the new getExtensions() and getExtewnsionInfo() functions
CheersDulux-Oz
√(-1) 2^3 Σ Π
...And it was Delicious!
Alpha-Geek
ICT Professional
GMing Since 1982
NSW, Australia, UTC +10
LinkedIn Profile: www.linkedin.com/in/mjblack
Watch our games on Twitch: www.twitch.tv/dulux_oz
Support Me on Patreon: www.patreon.com/duluxoz
Past Games, etc, on my YouTube Channel: www.youtube.com/c/duluxoz
-
September 18th, 2014, 09:30 #4
Actually Moon, while I've got you online - do we need to do anything "special" to get the Extension "registered" with the Extension package - cause I can't seem to get any data back out of get Extensions()
Dulux-Oz
√(-1) 2^3 Σ Π
...And it was Delicious!
Alpha-Geek
ICT Professional
GMing Since 1982
NSW, Australia, UTC +10
LinkedIn Profile: www.linkedin.com/in/mjblack
Watch our games on Twitch: www.twitch.tv/dulux_oz
Support Me on Patreon: www.patreon.com/duluxoz
Past Games, etc, on my YouTube Channel: www.youtube.com/c/duluxoz
-
September 18th, 2014, 10:30 #5
OK, I've got the data retrieval sorted - all except Ruleset Dependencies. The following is in the Extensions.xml file:
Code:<properties> <name>Test Extension</name> <version>1.0</version> <author>Matthew James BLACK.</author> <description>An Extension to Test the Extensions Module.</description> <ruleset> <name>d20</name> <minrelease>12</minrelease> </ruleset> <ruleset> <name>My Ruleset</name> <minrelease>2</minrelease> <maxrelease>12</maxrelease> </ruleset> <dependency> <name>Locations</name> <minversion>1</minversion> <maxversion>3</maxversion> </dependency> </properties>
Oh and what are exclusiongroups and how do we use them?
CheersDulux-Oz
√(-1) 2^3 Σ Π
...And it was Delicious!
Alpha-Geek
ICT Professional
GMing Since 1982
NSW, Australia, UTC +10
LinkedIn Profile: www.linkedin.com/in/mjblack
Watch our games on Twitch: www.twitch.tv/dulux_oz
Support Me on Patreon: www.patreon.com/duluxoz
Past Games, etc, on my YouTube Channel: www.youtube.com/c/duluxoz
-
September 18th, 2014, 11:41 #6
I have also noticed that ruleset dependency information is not provided by the Extension package, but does that really matter because you cannot select the extension in launcher in the first place if deps are not ok.
exclusiongroups can be used to say only one this type of extension can be allowed. For instance in SW we have lots of theme extension which change outlook. We use <exclusiongroups>theme</exclusiongroups> in all of them so when you're in launcher you can select only one theme-annotated extension. If you try to select more, then only latest of you selection remains, other are marked off."Alright, you primitive screwheads, listen up: THIS... is my BOOMSTICK!" -- Ash Williams, Army of Darkness
Post your SavageWorlds ruleset feature requests and issue reports here!
-
September 19th, 2014, 00:40 #7
Given how an update of a ruleset can effectively break an extension to that ruleset, it makes perfect sense to be able to say this extension only works with versions A through B, or some such. Until we have a more robust extension programming model, it seems to me like data issues are really only half of the problem with versioning.
-
September 19th, 2014, 06:19 #8
The major issue setting up <maxversion>x</maxversion> is that you must be able to predict your project's future and determine when extension becomes incompatible! This is nearly impossible unless you have pre-made plans but still. That definition would only be useful if extensions could be updated automatically to everyone via FG updater, because people might not know when to download new version manually.
"Alright, you primitive screwheads, listen up: THIS... is my BOOMSTICK!" -- Ash Williams, Army of Darkness
Post your SavageWorlds ruleset feature requests and issue reports here!
-
September 19th, 2014, 06:28 #9
-
September 19th, 2014, 06:59 #10
If you know for sure that your extension works up to a specific version, that would be your maxversion. Once you verify that your extension works with a newer version of the ruleset, you would bump up your maxversion for your extension. I don't see any other way around that. Alternately, you could just leave maxversion blank until you determine that a ruleset change has broken your extension. It's really a band aid for the current issues though. A much better solution would probably be more extensive peer review of extensions, and some open-source-ish way to community improve the rulesets so that popular extensions can be integrated directly in. But I'm sure even that has it's own issues...it's a hard problem.
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks