OniGalore

OniGalore:Current events: Difference between revisions

Project page Discussion

OniGalore:Current events (view source)

Revision as of 20:55, 20 April 2009

682 bytes removed ,  20 April 2009
addng advisory, removing a few ideas that would be redundant of other efforts
m (moved Current events to OniGalore:Current events: This is just where it goes! At least in newer versions of MW.)
(addng advisory, removing a few ideas that would be redundant of other efforts)
Line 20: Line 20:


Proposal for organizing things:<br>
Proposal for organizing things:<br>
*at some point, the Edition needs to document all the changes it makes, not in an informal list like "Basic features", "Coming soon enough", but in a carefully maintained page like what Loser has done beautifully [[AE:Combat system|here]] (frankly, that page right there is a lot of the work done already, the overall AE documentation would just explain a few other things and link to that page for the rest)
*update [[AE:ONK]] to make it clear that it was superceded by the AE, and move it out of the AE prefix
*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 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
*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
Line 28: Line 26:
*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 -- either a combinatory page like [[Weapons mods]] or their own separate pages -- since they are not part of the AE; 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 -- either a combinatory page like [[Weapons mods]] or their own separate pages -- since they are not part of the AE; they can be browsed there as candidates for the AE, but since they're not part of it, why leave them in that namespace?


If you're thinking, "Yeah, but who's going to do all this?", don't. Don't let the list intimidate you. Many of these steps are quick and easy; others can be chipped away at, over time. Certainly I will do what I can to pitch in when it comes to the areas of the wiki I understand. And if everyone contributes in the area they understand, we'll each gradually come to a better grasp of all the content that's on the wiki; right now, a lot of content is lurking in corners, like [[AE:Patching|this little gem]], and is just begging to have something done with it that reflects where we are in 2008. --[[User:Iritscen|Iritscen]] 00:43, 22 September 2008 (CEST)


===General wiki maintenance===
===General wiki maintenance===
Line 35: Line 32:
# If an image is neither used to illustrate a page [[Special:Uncategorizedimages|nor categorized]] (not used as an article of its own right, which can be justified in some cases), then maybe it's not getting the attention it deserves, or maybe it's useless/redundant. Feel free to do something about such "out-of-the loop" images or just point them out.
# If an image is neither used to illustrate a page [[Special:Uncategorizedimages|nor categorized]] (not used as an article of its own right, which can be justified in some cases), then maybe it's not getting the attention it deserves, or maybe it's useless/redundant. Feel free to do something about such "out-of-the loop" images or just point them out.
# Set up handy [[wikipedia:Redirect|redirects]]. These can be great time savers.
# Set up handy [[wikipedia:Redirect|redirects]]. These can be great time savers.


===Coverage of Oni content===
===Coverage of Oni content===
Line 41: Line 39:
# Some [[Chapters|chapter]] pages may have incorrect/incomplete plot summaries: they're also supposed to be concise, linking to other pages whenever the summary or the [[:Category:Added value|Added value]] section starts growing out of shape.
# Some [[Chapters|chapter]] pages may have incorrect/incomplete plot summaries: they're also supposed to be concise, linking to other pages whenever the summary or the [[:Category:Added value|Added value]] section starts growing out of shape.
# Places (like [[Regional State Building]]) and entities (like [[BGI]]) typically deserve a page of their own, meant to take some load off the Chapter summaries, both in terms of "facts" and "added value", while providing more or less technical trivia.
# Places (like [[Regional State Building]]) and entities (like [[BGI]]) typically deserve a page of their own, meant to take some load off the Chapter summaries, both in terms of "facts" and "added value", while providing more or less technical trivia.
# It would be nice to have a frame-by-frame overview/analysis of the [[1999|1999 trailer]].
====and beyond...====
====and beyond...====
# Use [[Lost Chapters]] to elaborate on what may have happened to Konoko in the time gaps between the original chapters (e.g., between {{C|12}} and {{C|13}}). You can also elaborate on sequels/prequels/interquels/paraquels, which may fit under a general philosophy (to be detailed [[Oni2|HERE]]). Depending on the nature of your stuff, it may end up as more than fan fiction, either by being implemented in the [[Anniversary Edition]] or by inspiring dôjinshi-oriented artwork.
# Use [[Lost Chapters]] to elaborate on what may have happened to Konoko in the time gaps between the original chapters (e.g., between {{C|12}} and {{C|13}}). You can also elaborate on sequels/prequels/interquels/paraquels, which may fit under a general philosophy (to be detailed [[Oni2|HERE]]). Depending on the nature of your stuff, it may end up as more than fan fiction, either by being implemented in the [[Anniversary Edition]] or by inspiring dôjinshi-oriented artwork.
# Plagiarism is not nice, but "Oni 2" can still be influenced by anime/cyberpunk/other references. See [[Oni2:Influences|HERE]] to review the influences so far, elaborate on them some more, or point out new ones.
# Plagiarism is not nice, but "Oni 2" can still be influenced by anime/cyberpunk/other references. See [[Oni2:Influences|HERE]] to review the influences so far, elaborate on them some more, or point out new ones.


===Adding to the databases===
===Adding to the databases===
# Despite its relative simplicity, [[BSL]] is vastly underdocumented. Most of the stuff is well-known to experts, but designing a comprehensive guide that will get novice scripters started and keep them going requires didactic skills and ''lots'' of patience. There are a few programming language basics that someone ought to say a few words of wisdom (like [[BSL:Functions|functions]] or [[BSL:Operators|operators]]). Long-term goals are: a cross-referenced set of mini-tutorials that document the [[BSL:Preset|preset]] functions and variables in a standalone way (see, e.g., [[ai2_allpassive]]); maybe a functional breakdown of the original scripts (see, e.g., [[BSL:Tutorial/airport1_level_logic.bsl|HERE]])
# Despite its relative simplicity, [[BSL]] is vastly underdocumented. Most of the stuff is well-known to experts, but designing a comprehensive guide that will get novice scripters started and keep them going requires didactic skills and ''lots'' of patience. There are a few programming language basics that someone ought to say a little about (like [[BSL:Functions|functions]] or [[BSL:Operators|operators]]). Long-term goals are: a cross-referenced set of mini-tutorials that document the [[BSL:Preset|preset]] functions and variables in a standalone way (see, e.g., [[ai2_allpassive]]); maybe a functional breakdown of the original scripts (see, e.g., [[BSL:Tutorial/airport1_level_logic.bsl|HERE]])
# There's still progress to be made in the field of [[OBD|binary hacking]]. Note the "OK?" column on [[OBD:File_types]]. Any page not marked with a happy face still has data stored within that file type that is not understood.
# There's still progress to be made in the field of [[OBD|binary hacking]]. Note the "OK?" column on [[OBD:File_types]]. Any page not marked with a happy face still has data stored within that file type that is not understood.
# Aside from doing actual research on Oni's binaries, you can also make sure that each [[OBD:File_types|file type's page]] in the [[OBD]] namespace actually explains what that file type is for, to help out newbies. An overview at the top of each page will make things much more user-friendly.
# Aside from doing actual research on Oni's binaries, you can also make sure that each [[OBD:File_types|file type's page]] in the [[OBD]] namespace actually explains what that file type is for, to help out newbies. An overview at the top of each page will make things much more user-friendly.
===Implementing a Category Tree===
This is a general advisory that [[User:Iritscen|I'm]] planning to finalize the Category Tree I've outlined [[User:Iritscen/CatTreeDraft|here]] within two weeks. Once it's finalized, that means that I'll be slowly engaging in the process of placing pages into the category structure it describes. Doing this will allow us to: (1) filter out and rediscover old pages that need attention (and there are a few, believe me), (2) browse pages by category (allowing a site map-like alternative to the main page), and (3) organize the images properly so they can be tracked by us moderator types more easily.
Now, since problem pages will be dealt with as they are discovered, implementing the Tree won't be a fast process. I may not even find the time to start doing it for a while, but I still want to "lock in" the plan now, so I can begin working on it as soon as the right time presents itself. That being said, if anyone thinks the Tree needs some improvement, <u>please speak up by May 4th</u>. After that, the Tree can still be changed, but I might have already started categorizing, so obviously it would be nice not to have to re-do any work.
Retrieved from "https://wiki.oni2.net/Special:MobileDiff/14204"