Find the original node first#
Read the file from your game version. Record its path, stable element ID and original value, then create a patch at the corresponding extension path. add, replace and remove solve different tasks. Replacing a whole document for one attribute increases update sensitivity and conflicts.
Learning example#
The invented document below is not a game file. Its patch changes one enabled attribute from false to true. Do not copy the sample items path into a real mod without an actual matching target document.
<items>
<item id="wiki_example" enabled="false" />
</items><diff>
<replace sel="/items/item[@id='wiki_example']/@enabled">true</replace>
</diff>Verify the selector#
Find matches, confirm the intended object and type, apply the patch and compare the effective document, then run the game and inspect the effect and log. Zero matches may mean a wrong version, path or unavailable dependency. Multiple matches may mean an overly broad selector. Silencing errors hides both problems.
Next practical step#
Read the real Elite hull example. If several mods change the same field, verify compatibility and the effective document.