Could you please explain how it works? Does it actually solve the problem of limiting a mod to a certain adventure (and, particularly, excluding it from vanilla). If not, is there another mechanism that does that?1.03 wrote:Added “extends” attribute for extensions (extension only loaded for given adventures)
George: how does 'extends' attribute work
- alterecco
- Fleet Officer
- Posts: 1658
- Joined: Wed Jan 14, 2009 3:08 am
- Location: Previously enslaved by the Iocrym
There was a discussion on IRC about limiting mods to only some adventure extensions, and I seemed to recall there was a way. After sifting through the changelog I fell over this:
-
- Developer
- Posts: 2998
- Joined: Thu Jul 24, 2003 9:53 pm
- Contact:
The extends= attribute takes a list of adventure UNIDs (separated by semicolons). If present, then the extension only works with the given set of adventures.
[Note: There are two UNIDs associated for an adventure. There is an UNID on the adventure itself (in the <TranscendenceAdventure> element) and there is an UNID in the adventure descriptor (<AdventureDesc>). Right now this attribute expects the UNID of the adventure itself, but it in the future it will accept either one.]
[Note2: I have not tested it, but if you specify:
I believe the extension will only work on vanilla.]
[Note: There are two UNIDs associated for an adventure. There is an UNID on the adventure itself (in the <TranscendenceAdventure> element) and there is an UNID in the adventure descriptor (<AdventureDesc>). Right now this attribute expects the UNID of the adventure itself, but it in the future it will accept either one.]
[Note2: I have not tested it, but if you specify:
Code: Select all
... extends="0"