Overview of individual PatchOperations PatchOperationAdd Generally only used in testing to see if a Sequence is working correctly, should never be used in published mods.
Rimworld prepare carefully patches Patch#
Never - This patch operation always fails. This used to be used in PatchOperationSequences to test the negative of a PatchOperationTest you should now use on PatchOperationConditional Invert - Errors are considered a success and success is considered a failure. This used to be used in PatchOperationSequence along with PatchOperationTest in order to conditionally run patches, but is now obsolete. it suppresses all errors that might have occurred. Always - This patch operation always succeeds, i.e. Note that use of this tag should be considered obsolete its use was common before PatchOperationConditional was implemented, but it should no longer be required and can cause confusion as it can suppress legitimate errors from showing up. node determines how errors are handled, usually in a PatchOperationSequence. XPath is a well-documented industry standard (good resource, too) there are plenty of resources available on the subject ranging from exhaustive tutorials to simple StackOverflow questions. If we want to replace texturePath, we have to replace it with /new/path/to/textureįor more info, see this Thread. texturePath/ to specify the content of the texturePath node. We select the child node "texturePath" from this node. We narrow down from "all TerrainDefs" to only those with the child "defName" node whose value is "WaterDeep", which should give us exactly one node because defNames must be unique. All child nodes of the root node called "TerrainDef" are selected. If we use the example from the lead, we get a specific path:ĭefs/TerrainDef/texturePath Once the root is selected, the XPath lets the system walk down specific branches of the tree. Starting with /Defs/ or */ works, but it is not recommended because it incurs additional overhead due to the way the XPath resolver works. Since the root node of all Defs is enforced to be, our xpath always starts with Defs/. Note that these "paths" have zero relation to the file path or folder structure: They follow the structure of the XML nodes. It will follow each part of the path from left to right. An XPath is a "path" for the patch to follow when trying to find XML nodes matching the description. PatchOperationFindMod tests for the presence of another mod, and can do different operations depending on the result.Įach PatchOperation must specify an XML node to modify. PatchOperationConditional tests nodes, and can do different operations depending on the result. PatchOperationTest tests nodes, which is useful inside a PatchOperationSequence. 
Three allow for conditional operations:.PatchOperationSequence contains a set of other PatchOperations, and aborts upon any operation failing.PatchOperationSetName changes the name of a node.PatchOperationAddModExtension adds a ModExtension.Three allow for more complex operations:.PatchOperationAttributeRemove removes an attribute for the selected node.PatchOperationAttributeSet sets a provided attribute for the selected node, overwriting the attribute value if the attribute name is already present.PatchOperationAttributeAdd adds a provided attribute to the selected node if and only if the attribute name is not already present.Three do basic operations on XML attributes:.PatchOperationReplace replaces the selected node with the provided node.PatchOperationRemove deletes the selected node.PatchOperationInsert inserts a provided sibling node above the selected node.PatchOperationAdd adds a provided child node to the selected node.These are the available PatchOperation types:
4 Overview of individual PatchOperations.1 Overview of available PatchOperations.
0 kommentar(er)
