I'm sorry, but WHAT THE HECK IS ALL THAT CRAP ON YOUR PAGE? Dearly, LightspeedX 00:28, 30 December 2009 (UTC)
Your userpage should be deleted, it has the marked for deletion template... Seriously, what's the point of putting random junk onto your page? --SpiritCrusher 08:36, 31 December 2009 (UTC)
I know, but it's useless anyway. --SpiritCrusher 12:19, 1 January 2010 (UTC)
drafting huge response to main page talk section here
so I don't end up conflicting with another edit and having to deal with that
Note: Editors, etc, refers to SRB2 editing, not the Wiki.
I am of the opinion that the Wiki is indeed not as useful as it could be at the moment. However, I don't think deleting mod pages, etc, is the way to go here. The Wiki isn't just for editing, guys. We went over this way back when. Many people use these for emblem locations, secrets, list of map numbers, etc. As for SOCs: We should have one big list of SOCs page. Each SOC in the releases section of the SRB2MB (This includes SOCs released with level packs, etc, even if that level pack already has a real page) would have a section with a small sentence describing what it does, and a chart similar to the Technical Data section for maps that lists the frames, objects, and custom sprites used. It should become a standard on the SRB2MB to not conflict with a prior SOC to be moved to the releases section. Of course, a SOC that's meant to build on another would be allowed to overwrite one of the latter SOC's states/objects, although I've never heard of something like that. EXE Mods would have the same sort of page, except with versionnumbers to go with the MS reform. Characters? Characters can go suck cocks, but if you insist, you might want a page with their OBJCTCFG (did i spell that right?) IDs, although I don't know if any problems are actually caused if two overlap.
EDIT: As an afterthought, have another page like this for level packs so they don't overlap.
As for part 2 of my super wall of text, what I believe should actually be done to assist in editing:
- Every linedef and sector should have a redirect page like LD123 or ST456 (I think we might have this already, I can't be bothered to check). This is so that if an editor already knows the special they want, they can just type in the URL.
- Never redirect a user to another page for information on how to use a special. For example, chains should have information on how to be made on both the linedef page, the sector (do chains use sectors, i forget) page, and the thing page. In some cases, there should be a more detailed tutorial with its own page, but it would be with the short tutorial on the specials page as a "See also:"
- The Main Page should have a drop down menu for linedefs, sectors, and things. This should be arranged by what the special does - editors who already know the linedef number can just use the URL or the Go function.
Your User Page
For what it in your User Page. @Router 13:29, 23 September 2010 (UTC)