OBD talk:Instance file format

I want to raise a couple of questions about the instance files as they occur in Oni's original resources:

As mentioned HERE, the "flags" bitset in the instance descriptor for non-empty files are actually 0x01 00 10 00, 0x09 00 10 00, or 0x00 00 30 00. I've added a mention of those other 2 bits (0x00 00 10 00 and 0x00 00 20 00), but since they occur systematically, it would be nice to know why, or at least to confirm that the current engine ignores those two bits.

Just noting that the current version of the page does answer this page. In short, the 0x00 00 10 00 and 0x00 00 20 00 bits are only relevant in Tool mode, and retail Oni is built in Shipping mode. --Iritscen (talk) 22:58, 23 January 2026 (UTC)

Do we have a list of files (instances) that are both unnamed and unreferenced? (and will thus be discarded by OniSplit's -export? At least one known example of such "orphan" files are the unnamed TRCM of level0_Final. Has anyone come across any others, I wonder. --geyser 12:47, 21 May 2018‎

This can (hypothetically) be obtained using Kanabo by using the filter for the --list operation which shows orphaned instances (see documentation) – however as of this writing the feature is not useful because not all templates are implemented in Kanabo yet. Once 100% of the templates have been implemented, Kanabo will be able to reliably tell which instances truly are unreferenced. Until then, the tool thinks that a ton of instances are unreferenced because it's unable to see the instance pointer fields in instances which it has not been taught to read. The only reason I'm noting this here now is because I think that I'll probably forget to do so when Kanabo reaches 100% implementation (the --compliance argument will tell you how far Kanabo has gotten as of the present moment). --Iritscen (talk) 04:38, 10 October 2026 (UTC)