19,584
edits
OniGalore:Current events: Difference between revisions
→Organizing the modding side of the wiki: removing things I did
m (→and beyond...: page -> cat) |
(→Organizing the modding side of the wiki: removing things I did) |
||
| Line 25: | Line 25: | ||
Proposal for organizing things:<br> | Proposal for organizing things:<br> | ||
*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 | ||
::New idea: use the <nowiki><onlyinclude></nowiki> tags on explanatory paragraphs at the start of each file type article. Then, transclude every article onto the [[Overview of file types]] page, or whatever it'll be called, and only the explanations will get carried over and compiled into one page. The only catch is that this method would only allow the blurbs to link between other file type pages, or other sections of that overview page; we couldn't have it both ways. | |||
:::Actually, there's a way to get either kind of link depending on where the text is being transcluded: using an #if: statement in league with the <nowiki>{{PAGENAME}}</nowiki> variable. <nowiki>{{PAGENAME}}</nowiki> actually looks at which page the data appears on, not where it's transcluded from. Voila! | |||
*add to [[AE:Weapons]] (which still has the ONK image branded on it) any items on [[AE:New weapons]] that have definitely been adopted for the AE; the rest should then be moved to a more logical root-level name -- maybe a combinatory page like [[Weapons mods]]; they can be browsed there as candidates for the AE, but since they're not part of it, why leave them in that namespace? | *add to [[AE:Weapons]] (which still has the ONK image branded on it) any items on [[AE:New weapons]] that have definitely been adopted for the AE; the rest should then be moved to a more logical root-level name -- maybe a combinatory page like [[Weapons mods]]; they can be browsed there as candidates for the AE, but since they're not part of it, why leave them in that namespace? | ||
===Coverage of Oni content=== | ===Coverage of Oni content=== | ||