OBD:Oni Binary Data: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
Line 10: | Line 10: | ||
*[[OBD:BIP|The Binary Improvement Project]] : fixing up Oni's levels, characters, AI, weapons... | *[[OBD:BIP|The Binary Improvement Project]] : fixing up Oni's levels, characters, AI, weapons... | ||
*[[OBD:OUP|OniUnPacker (OUP)]] : actually ''modding'' Oni | *[[OBD:OUP|OniUnPacker (OUP)]] : actually ''modding'' Oni | ||
*[[OBD:OME|OniModelsExtractor (OME)]] : extracting Oni's models (has just begun) | |||
---- | ---- |
Revision as of 08:06, 10 November 2006
This is mostly about Oni's static binary resources (DAT/RAW files), but also about runtime variables and processes.
I'm thinking of a better way to organize the DAT/RAW database, with a few templates maybe...
Binary resources
- SSG's Oni Stuff : first DAT/RAW database ever
- File types in Oni's DAT/RAW archives : wiki port of SSG's database
- The Binary Improvement Project : fixing up Oni's levels, characters, AI, weapons...
- OniUnPacker (OUP) : actually modding Oni
- OniModelsExtractor (OME) : extracting Oni's models (has just begun)
Runtime hacking
I really think their place is in the OBD namespace :
- OniFly
- Oni Trainer...