OBD:File types: Difference between revisions

From OniGalore
Jump to navigation Jump to search
No edit summary
mNo edit summary
Line 4: Line 4:


<B>@geyser: Stop destroying my artwork. Please wait until I've finished it. Btw., this site sucks totally.</B>
<B>@geyser: Stop destroying my artwork. Please wait until I've finished it. Btw., this site sucks totally.</B>
Dear ssg,
#"this site" is a wiki, so :
#*it's ''nothing'' like a "site"
#*it doesn't suck totally : it only feels like it does if you're misusing it
#*even if it ''did'' suck totally, please note that I'm not the one technically running the MediaWiki engine.
#*so ''that'' comment is not BTW at all, and it should have read '''@ Alloc : this site sucks totally.'''
#Wiki pages are not the best place for private communication, but may I in turn ask you to ''please'' stop (note the "please") :
#*Capitalizing common nouns (or other words) that are not part of acronyms or similar. You don't have any overcapitalization ''in'' your tables, so why should you have any elsewhere?
#*Putting the word "File" (capitalized or at all) everywhere. We know they're files, not potatoes. I'd only put "file" or "files" when the grammatical construction requires it, and omit them otherwise.
#*Creating files of the same type (namely, BINA) as standalone wiki pages. I strongly suggest the use of subpages.
#Additionally, you shouldn't be offended by people experimenting on your work. There are two recommended attitudes :
#*either your stuff is a "work of art", something perfect and complete (and what's more, you think it looks ugly when displayed on a wiki). In that case, just keep it on your site. We can provide minor feedback via mail or IM if needed, and your state-of-the-art database will be linked to from here as it is now.
#*or you allow other people to reconsider the presentation of your work. If I think the big list of file types is not too convenient, I may feel like experimenting with a more hierarchical layout. If I think the <== and ==> links allowing one to browse ''only to the next and previous resource in alphabetical order'' is not right, I may try and add an alternative browsing scheme.
#Actually, I wonder if porting your whole database to the wiki is much of a priority right now : adding data interpreters for known stuff to Alloc's OUP looks like a greatly needed task to me...
#If it ''must'' be ported, I'd invite you to reconsider the ''way'' you do it :
#*As you've noticed, your tables are, so far, the object on this wiki most prone to vandalism (or just unconsiderate edition). Luckily I'm someone you can reason with, but can you tell a dozen unidentified IPs to " stop destroying your "artwork" "?
#*The major point here is that whereas some people will check their guesses before filling in an ''unknown'' field, others will have ''wrong guesses'' and screw up your tables in no time.
#*Maintaining the whole database will be a pain even for someone who's 100% familiar with the existing information (and don't count on me to log in, check "recent changes", see that an unidentified IP has changed the interpretation of some field, load the reference, on your site, run Oni...). Maintenance here requires a quick response, you're the only one who can do it reliably, ''but'' need I remind you about your famous Oni-at-home-and-internet-at-the-university problem? Will you be able
#*You're making a ''major reference'' (much larger in size than, say, the Combat move database) available for edition to the public. I only want to point out that every amendment to such a database should be required to go through a checking procedure. That long-term maintenance will be a problem. And that I will continue to look at the backup rather that on the wiki-powered version anyway...
#Basically the way it happened back on the forum was fine, and it ''can'' be ported to the wiki. Here's my suggestion :
#*Linking to the database on your site should be well enough, and actually better. We keep the Fyle-type hierarchy we already created, and on every page, we put a link to the corresponding page on your site ''and that's all'' (no duplicates of the GIFs, no duplicate of the hex breakdown)
#*After browsing your site, if we think anything is wrong or incomplete on page such-and-such, we add a minor comment to an otherwise almost empty page (link to your reference version of the moment + our comments ''or guesses'' : occasional proofreading remarks, comments of the type "I ''think'' 0x###### is such-and-such")
#*The reference source data stays out of reach on your server.


The table below shows all of Oni's file types.
The table below shows all of Oni's file types.

Revision as of 01:20, 31 December 2005

Main Page >> Oni Binary Data >> File Types

OK, I've tried to organize it a little bit. The first little table is in alphabetical order, and the other ones are thematic. The thematic grouping is subject to change and further hierarchisation.

@geyser: Stop destroying my artwork. Please wait until I've finished it. Btw., this site sucks totally.

Dear ssg,

  1. "this site" is a wiki, so :
    • it's nothing like a "site"
    • it doesn't suck totally : it only feels like it does if you're misusing it
    • even if it did suck totally, please note that I'm not the one technically running the MediaWiki engine.
    • so that comment is not BTW at all, and it should have read @ Alloc : this site sucks totally.
  2. Wiki pages are not the best place for private communication, but may I in turn ask you to please stop (note the "please") :
    • Capitalizing common nouns (or other words) that are not part of acronyms or similar. You don't have any overcapitalization in your tables, so why should you have any elsewhere?
    • Putting the word "File" (capitalized or at all) everywhere. We know they're files, not potatoes. I'd only put "file" or "files" when the grammatical construction requires it, and omit them otherwise.
    • Creating files of the same type (namely, BINA) as standalone wiki pages. I strongly suggest the use of subpages.
  3. Additionally, you shouldn't be offended by people experimenting on your work. There are two recommended attitudes :
    • either your stuff is a "work of art", something perfect and complete (and what's more, you think it looks ugly when displayed on a wiki). In that case, just keep it on your site. We can provide minor feedback via mail or IM if needed, and your state-of-the-art database will be linked to from here as it is now.
    • or you allow other people to reconsider the presentation of your work. If I think the big list of file types is not too convenient, I may feel like experimenting with a more hierarchical layout. If I think the <== and ==> links allowing one to browse only to the next and previous resource in alphabetical order is not right, I may try and add an alternative browsing scheme.
  4. Actually, I wonder if porting your whole database to the wiki is much of a priority right now : adding data interpreters for known stuff to Alloc's OUP looks like a greatly needed task to me...
  5. If it must be ported, I'd invite you to reconsider the way you do it :
    • As you've noticed, your tables are, so far, the object on this wiki most prone to vandalism (or just unconsiderate edition). Luckily I'm someone you can reason with, but can you tell a dozen unidentified IPs to " stop destroying your "artwork" "?
    • The major point here is that whereas some people will check their guesses before filling in an unknown field, others will have wrong guesses and screw up your tables in no time.
    • Maintaining the whole database will be a pain even for someone who's 100% familiar with the existing information (and don't count on me to log in, check "recent changes", see that an unidentified IP has changed the interpretation of some field, load the reference, on your site, run Oni...). Maintenance here requires a quick response, you're the only one who can do it reliably, but need I remind you about your famous Oni-at-home-and-internet-at-the-university problem? Will you be able
    • You're making a major reference (much larger in size than, say, the Combat move database) available for edition to the public. I only want to point out that every amendment to such a database should be required to go through a checking procedure. That long-term maintenance will be a problem. And that I will continue to look at the backup rather that on the wiki-powered version anyway...
  6. Basically the way it happened back on the forum was fine, and it can be ported to the wiki. Here's my suggestion :
    • Linking to the database on your site should be well enough, and actually better. We keep the Fyle-type hierarchy we already created, and on every page, we put a link to the corresponding page on your site and that's all (no duplicates of the GIFs, no duplicate of the hex breakdown)
    • After browsing your site, if we think anything is wrong or incomplete on page such-and-such, we add a minor comment to an otherwise almost empty page (link to your reference version of the moment + our comments or guesses : occasional proofreading remarks, comments of the type "I think 0x###### is such-and-such")
    • The reference source data stays out of reach on your server.


The table below shows all of Oni's file types.

Appearance Meaning
BLAH Absent from the binaries
BLAH Level 0 file
BLAH Level file
BLAH Character file
3CLA ABNA AGDB AGQC AGQG AGQM
AGQR AISA AITR AIWA AKAA AKBA
AKBP AKDA AKEV AKOT AKVA BINA
CBPI CBPM CONS CRSA DOOR DPge
EDIA ENVP FILM FXLR GMAN HPge
IDXA IGHH IGPA IGPG IGSA IGSt
Impt IPge KeyI M3GA M3GM M3TA
Mtrl NMSA OBAN OBDC OBLS OBOA
OFGA ONCC ONCP ONCV ONFA ONGS
ONIA ONLD ONLV ONMA ONOA ONSA
ONSK ONTA ONVL ONWC OPge OSBD
OTIT OTLF PLEA PNTA PSpc PSpL
PSUI QTNA QUDA SNDD StNA SUBT
TMFA TMRA TRAC TRAM TRAS TRBS
TRCM TRFT TRGA TRGE TRIA TRIG
TRMA TRSC TRTA TSFF TSFL TSFT
TSGA TStr TURR TXAN TXCA TXMA
TXMB TXMP TXPC TxtC UUEA UVDL
VCRA WMCL WMDD WMM_ WMMB WPge

Misc files

Main Page >> Oni Binary Data >> File types

Unsorted

Type Description Notes
BINA Binary Data Start file
FILM Film -
IDXA Index Array -
M3GA Geometry Array -
M3GM Geometry -
Mtrl Material 0 byte file
OBAN Object Animation -
PNTA 3D Point Array -
SNDD Sound Data -
TXAN Texture Map Animation -
TXCA Texture Coordinate Array -
TXMB Texture Map Big -
TXMP Texture Map -
VCRA 3D Vector Array -

Message files

Type Description Notes
IGPA IGUI Page Array -
IGPG IGUI Page -
IGSA IGUI String Array -
IGSt IGUI String -
IPge Item Page not in all levels
OPge Objective Page -
PSpc Part Specification -
TSFF Font Family 0 byte file
TxtC Text Console -

Defunct files

Type Description Notes
3CLA RGB Color Array -
AGQM Gunk Quad Material -
AIWA AI Imported Waypoint Array -
EDIA Edge Index Array -
FXLR FX Laser Effect -
GMAN Geometry Animation -
M3TA Triangle Array -
NMSA Network Spawn Point Array -
Type Description Notes
OBLS Object LS Data -
QUDA Quad Array -
TMFA Float Array -
TMRA Template Reference Array -
TRFT Totoro Facing Table -
TXPC Texture Procedure Data -
UUEA Error Binding Array -
UVDL UV Data List -

Level 0 files

Type Description Notes
CONS Console -
DOOR Door -
DPge Diary Page -
HPge Help Page -
IGHH IGUI HUD Help -
KeyI Key Icons -
OFGA Object Furn Geom Array -
ONGS Oni Game Settings -
ONLD Oni Game Level Descriptor -
ONVL Oni Variant List useless?
OSBD Oni Sound Binary Data -
PSpL Part Specification List -
PSUI Part Specifications UI -
StNA String Array -
Type Description Notes
SUBT Subtitle Array -
TRGE Trigger Emitter -
TRIG Trigger -
TSFL Font Language -
TSFT Font -
TSGA Glyph Array -
TStr String -
TURR Turret -
WMCL WM Cursor List -
WMDD WM Dialog Data -
WMM_ WM Menu -
WMMB WM Menu Bar -
WPge Weapon Page -
- - -

Level files

Unsorted

Type Description Notes
ABNA BSP Tree Node Array -
AGDB Gunk Quad Debug Array -
AGQC Gunk Quad Collision Array -
AGQG Gunk Quad General Array -
AGQR Gunk Quad Render Array -
AISA AI Character Setup Array -
AITR AI Script Trigger Array -
AKAA Adjacency Array -
AKBA Side Array -
AKBP BSP Node Array -
AKDA Door Frame Array -
AKEV Akira Environment -
AKOT Oct Tree -
AKVA BNV Node Array -
CRSA Corpse Array -
ENVP Env Particle Array -
Type Description Notes
OBDC Door Class Array -
OBOA Starting Object Array -
ONFA Imported Flag Node Array -
ONLV Oni Game Level -
ONMA Imported Marker Node Array -
ONOA Object Gunk Array -
ONSA Imported Spawn Array -
ONSK Oni Sky Class -
ONTA Trigger Array useless?
ONWC Oni Weapon Class 0 byte file
OTIT Oct Tree Interior Node Array -
OTLF Oct Tree Leaf Node Array -
PLEA Plane Equation Array -
QTNA Quad Tree Node Array -
TXMA Texture Map Array -
- - -

Character files

Type Description Notes
CBPI Character Body Part Impacts -
CBPM Character Body Part Material -
Impt Impact Tree 0 byte file
ONCC Oni Character Class -
ONCP Oni Character Particle Array useless?
ONCV Oni Character Variant 0 byte file, useless?
ONIA Oni Character Impact Array useless?
TRAC Animation Collection -
TRAM Totoro Animation Sequence -
Type Description Notes
TRAS Totoro Aiming Screen -
TRBS Totoro Body Set -
TRCM Totoro Quaternion Body -
TRGA Totoro Quaternion Body Geometry Array -
TRIA Totoro Quaternion Body Index Array -
TRMA Texture Map Array -
TRSC Screen (Aiming) Collection half 0 byte file
TRTA Totoro Quaternion Body Translation Array -
- - -

BIG table

Main Page >> Oni Binary Data >> File types

  • BLAH* means that there are no BLAH files in Oni's binaries and that they're probably defunct (same as BLAH above)
Type Description Notes
3CLA* RGB Color Array -
ABNA BSP Tree Node Array Level file
AGDB Gunk Quad Debug Array Level file
AGQC Gunk Quad Collision Array Level file
AGQG Gunk Quad General Array Level file
AGQM* Gunk Quad Material -
AGQR Gunk Quad Render Array Level file
AISA AI Character Setup Array Level file
AITR AI Script Trigger Array Level file
AIWA* AI Imported Waypoint Array -
AKAA Adjacency Array Level file
AKBA Side Array Level file
AKBP BSP Node Array Level file
AKDA Door Frame Array Level file
AKEV Akira Environment Level file
AKOT Oct Tree Level file
AKVA BNV Node Array Level file
BINA Binary Data Start file
CBPI Character Body Part Impacts Character file
CBPM Character Body Part Material Character file
CONS Console Level 0 file
CRSA Corpse Array Level file
DOOR Door Level 0 file
DPge Diary Page Level 0 file
EDIA* Edge Index Array -
ENVP Env Particle Array Level file
FILM Film -
FXLR* FX Laser Effect -
GMAN* Geometry Animation -
HPge Help Page Level 0 file
IDXA Index Array -
IGHH IGUI HUD Help Level 0 file
IGPA IGUI Page Array Message file
IGPG IGUI Page Message file
IGSA IGUI String Array Message file
IGSt IGUI String Message file
Impt Impact Tree Character file, 0 byte file
IPge Item Page Message file, not in all levels
KeyI Key Icons Level 0 file
M3GA Geometry Array -
M3GM Geometry -
M3TA* Triangle Array -
Mtrl Material 0 byte file
NMSA* Network Spawn Point Array -
OBAN Object Animation -
OBDC Door Class Array Level file
OBLS* Object LS Data -
OBOA Starting Object Array Level file
OFGA Object Furn Geom Array Level 0 file
ONCC Oni Character Class Character file
ONCP Oni Character Particle Array Character file, useless?
ONCV Oni Character Variant Character file, 0 byte file, useless?
ONFA Imported Flag Node Array Level file
ONGS Oni Game Settings Level 0 file
ONIA Oni Character Impact Array Character file, useless?
ONLD Oni Game Level Descriptor Level 0 file
ONLV Oni Game Level Level file
Type Description Notes
ONMA Imported Marker Node Array Level file
ONOA Object Gunk Array Level file
ONSA Imported Spawn Array Level file
ONSK Oni Sky Class Level file
ONTA Trigger Array Level file, useless?
ONVL Oni Variant List Level 0 file, useless?
ONWC Oni Weapon Class Level file, 0 byte file
OPge Objective Page Message file
OSBD Oni Sound Binary Data Level 0 file
OTIT Oct Tree Interior Node Array Level file
OTLF Oct Tree Leaf Node Array Level file
PLEA Plane Equation Array Level file
PNTA 3D Point Array -
PSpc Part Specification Message file
PSpL Part Specification List Level 0 file
PSUI Part Specifications UI Level 0 file
QTNA Quad Tree Node Array Level file
QUDA* Quad Array -
SNDD Sound Data -
StNA String Array Level 0 file
SUBT Subtitle Array Level 0 file
TMFA* Float Array -
TMRA* Template Reference Array -
TRAC Animation Collection Character file
TRAM Totoro Animation Sequence Character file
TRAS Totoro Aiming Screen Character file
TRBS Totoro Body Set Character file
TRCM Totoro Quaternion Body Character file
TRFT* Totoro Facing Table -
TRGA Totoro Quaternion Body Geometry Array Character file
TRGE Trigger Emitter Level 0 file
TRIA Totoro Quaternion Body Index Array Character file
TRIG Trigger Level 0 file
TRMA Texture Map Array Character file
TRSC Screen (Aiming) Collection Character file, half 0 byte file
TRTA Totoro Quaternion Body Translation Array Character file
TSFF Font Family Message file, 0 byte file
TSFL Font Language Level 0 file
TSFT Font Level 0 file
TSGA Glyph Array Level 0 file
TStr String Level 0 file
TURR Turret Level 0 file
TXAN Texture Map Animation -
TXCA Texture Coordinate Array -
TXMA Texture Map Array Level file
TXMB Texture Map Big -
TXMP Texture Map -
TXPC* Texture Procedure Data -
TxtC Text Console Message file
UUEA* Error Binding Array -
UVDL* UV Data List -
VCRA 3D Vector Array -
WMCL WM Cursor List Level 0 file
WMDD WM Dialog Data Level 0 file
WMM_ WM Menu Level 0 file
WMMB WM Menu Bar Level 0 file
WPge Weapon Page Level 0 file

Main Page >> Oni Binary Data >> File types