XML:XML Modding Lessons
- This article builds on this general introduction to modding.
The XML namespace is devoted to explaining Oni's data types in plainer language than the technical documentation at OBD and also provides tutorials in XML-based modding.
Oni's resources could be separated into one of two categories: media (such as models, textures and sounds), and non-media (such as character class data). Most of the non-media data can be exported to XML. This allows much easier modding than the hex-editing of the old days (compare the two methods here). Some media resources can also be "edited as XML", referring to the fact that an XML file will be created alongside the media file(s) when the resources are exported from the game data, and this XML companion file will contain metadata about the media files that allows OniSplit to re-import them properly when you are done editing them.
To learn what all the resource types do, and to see which types can be edited through XML, see the link to the database below. Though XML modding can generally be done with nothing more than OniSplit's command line interface and a text editor, the tutorials linked below are written with the Anniversary Edition in mind because the AE provides modding tools (including a GUI for OniSplit) and a framework for testing your mod package, and globalizes more of Oni's data so that it can be used in any level.
Working with XML files
EXtensible Markup Language is a plain-text file format designed to be both human-readable and machine-readable. It stores data in-between tags, e.g. <TagName>Some data here</TagName>, and these tags can be arranged in a hierarchy to keep things organized. The only technical difference between a normal text file and an XML file is that the file name ends in ".xml" instead of ".txt" and that it typically begins with the string <?xml version="1.0" encoding="UTF-8" ?>. You can thus edit an XML file in any text editor, such as Notepad in Windows and TextEdit on the Mac.
- See the tutorials below to learn how to extract game data as XML, modify it, and get it back into Oni.
- Capitalization matters: OniSplit is case-sensitive when it processes the XML.
- Text indentation: Most tags have some indentation (tabs). It is not required by OniSplit but it helps one get an understanding of the hierarchy. Two examples:
<Instance id="4" type="IGSA"> <Strings> <Link>#7</Link> </Strings> </Instance>
<Instance id="4" type="IGSA"><Strings><Link>#7</Link></Strings></Instance>
- Code folding: A simple text editor (and good use of the search function) is actually enough to work with Oni's XML. But big files might be easier to handle with what programmers call "code folding". Code folding allows you to collapse tags in order to get a better sense of the overall file structure, and is found in IDEs like Microsoft Visual Studio (Windows) and Xcode (Mac). Both programs are free.
- File comparison: For comparing two versions of an XML file to find the changes, you can use WinMerge (Windows) or FileMerge (Mac, comes with Xcode). Note that if one of the two files has passed through Oni and been re-exported, the data may have been totally reordered and cannot be diff-gazed effectively.