19,524
edits
(my proposal) |
(fixing my logical error) |
||
Line 28: | Line 28: | ||
*put all WIP mods under [[:Category:Modding projects]] | *put all WIP mods under [[:Category:Modding projects]] | ||
*either delete [[AE:ONK]] or replace it with a historical blurb citing its accomplishments before it was superceded by the AE, but either way, move it out of the AE prefix; if it's not deleted, leave it in the "Outdated modding projects" category; in any case, move the page's links to mods that were produced by the ONK to a their own pages, and integrate them with the categorization system discussed in the next point | *either delete [[AE:ONK]] or replace it with a historical blurb citing its accomplishments before it was superceded by the AE, but either way, move it out of the AE prefix; if it's not deleted, leave it in the "Outdated modding projects" category; in any case, move the page's links to mods that were produced by the ONK to a their own pages, and integrate them with the categorization system discussed in the next point | ||
*gradually bring wiki documentation of finished mods into | *gradually bring wiki documentation of finished mods into sync with the [http://mods.oni2.net Mod Depot]; because the Depot is strictly categorized, it makes more sense to start there and copy that structure to here; as we see files get added there, we add pages here, or for smaller mods add them to one combinatory page, and link back to the actual files on the Depot for download | ||
*the Main Page's "For Modders" section will guide the reader's approach to modding; it will look like this: | *the Main Page's "For Modders" section will guide the reader's approach to modding; it will look like this: | ||
:*Intro to modding -- a short explanation of where to start if someone is totally new so they know whether they should start by reading a tutorial, or browsing a database, etc. | :*Intro to modding -- a short explanation of where to start if someone is totally new so they know whether they should start by reading a tutorial, or browsing a database, etc. | ||
Line 34: | Line 34: | ||
:*OBD Database | :*OBD Database | ||
:*BSL Database -- of course we can provide a link to the BSL tutorials from here, but those pages should be in the same domain as the other tutorials | :*BSL Database -- of course we can provide a link to the BSL tutorials from here, but those pages should be in the same domain as the other tutorials | ||
:*History of modding -- link to what's currently the first part of the Modding Oni page | |||
*the link "Mods" under the "For Players" section will look like: | |||
:*The Mods | :*The Mods | ||
::*By Platform | ::*By Platform | ||
Line 40: | Line 42: | ||
::*By Mod Type | ::*By Mod Type | ||
::**... -- you get the idea if you've seen the Depot; since a mod's page can have more than one category, mods can be categorized by Platform as well as Mod Type, as well as Install Method if desired and we just link to those mods in their different groupings using this submenu-style structure | ::**... -- you get the idea if you've seen the Depot; since a mod's page can have more than one category, mods can be categorized by Platform as well as Mod Type, as well as Install Method if desired and we just link to those mods in their different groupings using this submenu-style structure | ||
*write an interlocking (interlinking!) page for OBD (called something like [[Overview of file types]]) that explains in plain English what each file does; this puts it all in one place, unlike putting summaries at the top of each page so that a newbie has to follow each file type link to that page to read about the file type; for the format would be something like: | *write an interlocking (interlinking!) page for OBD (called something like [[Overview of file types]]) that explains in plain English what each file does; this puts it all in one place, unlike putting summaries at the top of each page so that a newbie has to follow each file type link to that page to read about the file type; for the format would be something like: | ||
:"==QXRF== The QXRF type is for tracking the hats the characters are wearing; hat geometries are stored in <span style="color:#0000ff">VPRW</span> files. At level-load, Oni scans the QXRF array and loads the VPRWs. Then, it textures them with the hat textures stored in <span style="color:#0000ff">BINA/LDWF</span> and applies them using the UV maps in that BINA resource that are in the <span style="color:#0000ff">FLSJ</span> format." -- each four-letter type links to an subheading on the <u>same page</u> that explains that type more fully but without any technical details; until this is done, the hard work performed in reverse-engineering these files is shadowed in obscurity for newbies because of the lack of plain English in the OBD pages | :"==QXRF== The QXRF type is for tracking the hats the characters are wearing; hat geometries are stored in <span style="color:#0000ff">VPRW</span> files. At level-load, Oni scans the QXRF array and loads the VPRWs. Then, it textures them with the hat textures stored in <span style="color:#0000ff">BINA/LDWF</span> and applies them using the UV maps in that BINA resource that are in the <span style="color:#0000ff">FLSJ</span> format." -- each four-letter type links to an subheading on the <u>same page</u> that explains that type more fully but without any technical details; until this is done, the hard work performed in reverse-engineering these files is shadowed in obscurity for newbies because of the lack of plain English in the OBD pages |