16
Modification Help / Re: Redefining datablocks from another add-on
« on: June 03, 2018, 05:25:31 PM »
You should never tamper with the functionality of an add-on that you don’t manage (and therefore can’t control updates and deal with cross-compatibility issues). Say you hardcode a re-definition of the datablock of say the duplicator. Now if Zeblote releases an update that changes field names or adds new fields that are required for the add-on to work, your add-on forcing the old version of the datablock could break your add-on and more than likely break Zeblote’s duplicator.
Instead you should look into forcerequiredaddon and then use inheritance to duplicate the add-ons datablock into your own custom datablock, for example:
For more info check the stickied topic about using forceRequiredAddon to avoid duplicating datablocks.
Instead you should look into forcerequiredaddon and then use inheritance to duplicate the add-ons datablock into your own custom datablock, for example:
Code: [Select]
datablock itemData(copiedDuplicator : sourceDuplicator) //substitute for correct name
{
redefinedField = “redefined value”;
};
For more info check the stickied topic about using forceRequiredAddon to avoid duplicating datablocks.