Originally Posted by
Trenloe
The main complication is that it means possibly more work to make the extension compatible if (when) future FG versions are released that affect the XML in question. That is, the extension will need to be changed to use the new XML, plus the changes needed for the extension, to keep compatibility with the latest FG release.
Or, there are more chances of a clash with other extensions.
As you noted in post #1, the ideal solution is to use the merge rules, but you can't because the label control is not named - hopefully your request to add this will be addressed in the next release.
If merge rules are not possible, then the next step is to override the whole <windowclass> entry where the control resides. The rest of the XML file where that <windowclass> is specified is not needed, nor is "the entire character sheet". The more information you include, the more chances you have of a future FG release breaking it, or the extension clashing with another community extension.
My recommendation would be to just include the modified <windowclass name="charsheet_main"> XML section in your extension, as I mentioned in post #6 of this thread.