StrategyWiki talk:Community Portal

http://media.strategywiki.org/images/4/49/SW_CP_Banner.png

This page is for discussion of general community issues; if you just want to ask a question to more experienced users of the site, please use the staff lounge. To start a new thread [ click here]. Resolved threads are gradually archived; see the archives box to the right. As this page is for the community of StrategyWiki, it is required that you are registered and logged in before editing here.

A new skin is under development. If you have any suggestions, please add them to the list

Promising Guide of the Month
None of the guides there are in the positive. Please nominate some promising guides (strong team of writers or nearing completion) and vote on them. Votes on the Collaboration of the Month would also be helpful. -- Prod (Talk) 11:29, 2 December 2007 (CST)
 * Guys, Gals, assorted hermaphrodites, we're going to need to have a new 'most promising' up soon - we're a week into January already and still no most promising on the main page. So, speak now and forever hold your peace, else either Drift City or Golden Sun: The Lost Age will be 'most promising guide of the month'.--Froglet 22:00, 6 January 2008 (CST)
 * This type of site activity requires a level of community participation. We've discussed it at the staff meeting, so I won't rehash the arguments about anonymous edits, but continuing to support anonymous edits takes away from the community aspect of the site that helps promote this type of activity.  Lately, site support as been more autonomous and individual, so I'm not surprised that guides haven't been voted on.  Hopefully some of the server improvements will see the return of more community based behavior.  Procyon (Talk) 08:57, 7 January 2008 (CST)
 * Golden Sun: The Lost Age is PGotM; Drift City is CotM. Someone please write up the pages for these as I do not have the time this week or next.  Next months CotM is Super Mario Galaxy, so that can be written up as well (PGotM isn't voted on enough yet). -- Prod (Talk) 10:15, 11 January 2008 (CST)

Requiring registration
As you can probably tell, anons now appear to be able to edit every page now, whereas before we required them to register before being able to edit with the exception of a few unlocked guides. Now, I'm bringing this up because I'm wondering whether we should go back to the way it was regarding registration or allow anons to edit as well. I'm actually for anons to be able to edit everything. Looking through the Recent Changes, it appears that anons that would've added tons of content may have been turned away by the requirement to edit. Of course, we'll get vandalism from the anons too, but we already got that through registered users. So, what do you all think? -- 10:08, 23 December 2007 (CST)
 * Seems great to me.-- The preceding signed comment was added by Rocky (talk • contribs). 10:17, 23 December 2007 (CST)
 * I know that we're going to get a ton more edits by allowing it, and probably more active users too. Luckily we can toggle anonymous edits quite easily.  -- 17:15, 24 December 2007 (CST)
 * Also, I suggest we preemptively block IP's that have a history of vandalism on Wikipedia, such as various public schools in the US. -- 17:27, 24 December 2007 (CST)
 * I'm against that. We should only block an IP when it actually does do something bad. Plus, how many of those vandals are going to come here anyway? -- 18:03, 24 December 2007 (CST)
 * +1 --DrBob (talk) 19:20, 24 December 2007 (CST)
 * So that's why I've been seeing IP addresses in recent changes. Sure, this all sounds good. Baejung92 12:32, 25 December 2007 (CST)
 * I am moved to weigh in on this discussion. I've been trying to stay out of it since I am generally not in favor of this idea, and I appear to be outvoted, so I didn't want to put a damper on the decision.  But I've been looking at the quality of our anonymous edits, and they appear to range anywhere from moderately obvious at best, to ridiculously immature at worst, and the immature contributions are far more common.  I'm against this for two reasons.  One is the obvious issue that sysops are going to have patrolling all of these edits, but if that is something that some of you are prepared to deal with, then so be it, because I don't relish the idea.  The other reason, however is with regards to a difference between SW and, say, WP.  While WP has a well established community, community is not really WP's primary goal.  It's not ours either, but it is a focus.  Allowing anonymous edits sort of provides a method for people to bypass the community aspect of our site (in addition to providing unaccountability).  Some of you may feel that the benefit of the additional edits outweighs the lack of growth to the community, but I would disagree.  Anyway, I'm not suggesting that we change the policy (yet), I just wanted to throw my thoughts out there as food for thought.  Procyon (Talk) 16:45, 25 December 2007 (CST)
 * While I do agree the quality of anonymous edits is not as good as those of our registered users, I do feel that giving them a taste of editing before we push them to create an account might be beneficial as well. Accountability-wise, I feel that anons actually have a tad more accountability than registered users, because they cannot evade bans as easily (of course, 99% of them don't realize that, which is where the vandalism issue comes in with anons). Patrolling-wise, I try to patrol edits as much as I can while I'm online, and I know a few other sysops are as well. Of course, this does divert attention from other necessary tasks as well... although I know of an extension that can automatically assign rights to users, so perhaps letting users at least x days old and with at least y edits become autopatrolled would help alleviate some of that load. As for the community aspect, I do agree with you on that, as having a good, solid community is the only way to collaborate on some tasks. Also, I've revised our EditSubpages extension (the thingy with MediaWiki:Unlockedpages) to work a bit better (still needs more work, though), and I can probably add a toggle to it that allows any sysop to enable/disable the extension (and thus enable/disable anonymous editing) with a simple edit of some MediaWiki page, so if we change our minds a few times, we don't need someone to go edit our LocalSettings.php a hundred times. -- 19:15, 25 December 2007 (CST)
 * This is not working. The quality of these anonymous users is degrading.  We've had our first major spammer, and I just undid some racist's idea of fun.  All that I am seeing is increasingly leading me to conclude that we need to go back to registration.  I don't see the value in allowing anonymous edits if the majority of what we get in return is crap.  This will definitely be on the agenda for the next staff meeting (Jan. 5th).  Procyon (Talk) 10:25, 29 December 2007 (CST)
 * Agreed, I've got the updated EditSubpages extension, so if whoever is able to install it would meet me on IRC, I'd appreciate that. -- 10:44, 29 December 2007 (CST)
 * I feel that we should disable anonymous editing; the bad really outweigh the good right now. -- 21:22, 7 January 2008 (CST)
 * There were two resolutions made at the staff meeting last weekend. One was that Prod and Skizzerz would like more time to implement some more anti-vandalism measures, and they would be given another month to improve the situation.  The other is that ness feels that the site performance has been detering better edits.  Now that the site has been given a nice shot in the arm, we can look to see if that is indeed the case and revisit the matter next month.  Procyon (Talk) 21:34, 7 January 2008 (CST)
 * The reason I haven't been editing or patrolling is because it takes (or did up until a minute ago) 5 minutes for SW to load a page. -- 22:22, 7 January 2008 (CST)
 * I Have to say I am on Procyon's side. From what I've seen, the anonymous users editing the bigger articles are the ones doing the most harm. A few days ago (as you may have seen) we had an orchestrated vandal attack on the MapleStory/Monsters page (from what I've learned, this was a deliberate move led by a known troll from a forum) and I've had to lock that particular page so that only Sysops may edit. I was thinking, why not just Semi-protect entire guides of high traffic? Is there perhaps an easy way to semi the whole guide, or if not, is it something that could potentially be scripted? I know that larger guides might be how to get new users started, since it's more likely they came here to see that, but the amount of vandalism that's occurring is somewhat ridiculous. I'm just thinking this would make it easier, rather than having false information for the 12 hours I'm asleep or at school (which has actually been hurting our credibility :--IsaacGS 19:38, 18 January 2008 (CST)
 * I am currently in the process of writing an extension that can protect all subpages of a page. I should have a working prototype done in a week or two. -- 20:59, 18 January 2008 (CST)

Hmm, the anonymous edits for Flash Flash Revolution/Tokens have been VERY productive... I agree that the only way we can have anonymous edits is to restrict/"secure" them with the various proposed CVN methods. I think the strangest cool thing I've seen come out of anonymous edits is anonymous signing their summaries with an alias - lawl. -- 01:41, 11 January 2008 (CST)

CVN
I've started a page here, so feel free to add suggestions and voice your opinions. Please allow some time for input before actually assigning and enacting the ideas though. -- 17:45, 8 January 2008 (CST)

Vandalism Warning in Edittools
I've made a request to add foo to Edittools on MediaWiki_talk:Edittools because of the recent vandalism. Hopefully this will help in addition to a captcha or whatever is decided on to stop spambots and to encourage acceptance of anon editors. --Tathar (talk | contribs) 16:08, 20 January 2008 (CST)
 * IMO I don't see the point in this. Giving everyone easy access to a template that only should be used in cases of obvious vandalism on the vandal's talk page wouldn't really be very beneficial. The Edittools really should only be used when there are templates and such that actually help with making guides, not with telling other people off. -- 16:16, 20 January 2008 (CST)
 * In that case, do you have any suggestions where it should go instead? --Tathar [[Image:Tathar.jpg|32px]] (talk | contribs) 17:21, 20 January 2008 (CST)

WikiNode
Hi, I've started the WikiNode here (looks like some other guy created it before which got deleted). Right now the only other wiki I made SW connect to is the Bulbapedia, since last I stirred up conversation around here it has an official partnership with SW. Currently the AliceSoft Wiki (which SW's Sengoku Rance guides outsources to) has its WikiNode points here, and I'd like to request permission/consensus of the SW community to add the AliceSoft Wiki to the SW WikiNode (WikiNodes don't have to be mutual, so it's up to you guys to decide what to link or not link to).

For examples, see:
 * Wikipedia's WikiNode
 * AliceSoft Wiki's WikiNode.

-Afker 01:28, 26 December 2007 (CST)


 * Someone correct me if I'm wrong, but I believe the general attitude towards partnerships and linking is that we only do it to information that is relevant, but outside the scope of SW. Instead, we (should) provide the same information; again, when possible and necessary.  -- 07:20, 6 January 2008 (CST)

Next staff meeting
Hello everyone. The next staff meeting will be held in the usual place on January 5th, 2008, at 2pm EST/7pm GMT. As usual, please add anything that you like to the agenda below in advance of the meeting. Procyon (Talk) 10:36, 29 December 2007 (CST)
 * I added in a proposed third item. I know it's been a point in pretty much every other meeting, and not much ever gets decided in regards to the second sentence, but getting some new ideas in the mix may help. -- 12:13, 29 December 2007 (CST)
 * Sorry, I won't be able to be there- The preceding signed comment was added by Rocky (talk • contribs). 10:55, 2 January 2008 (CST)
 * Sorry I missed it. I didn't see the notice because I've been pretty inactive all of December and January so far - lack of contribution interest and SW loading so slow. -- 07:23, 6 January 2008 (CST)

Agenda

 * 1) Debate the continued allowance of anonymous edits (see section above).
 * 2) Recent caching failure, and efforts to restore it.
 * 3) Evaluate how the ads are performing. Discuss ways to increase revenue.

Infoboxes
Whats wrong?



What with the image part of the infobox? Lunar Knight (Talk to me + Contribs) 12:25, 5 January 2008 (CST)

3 Left Nav Bar additions
I was thinking that there are some very useful community areas that I don't think a lot of people see or know about. Sections such as: Requested guides, Promising Guide of the Month and Collaboration of the Month. I'm suggesting that we either 1) combine it with the current navigation, or 2) create a separate, smaller navbar section lower (beneath the donate button perhaps; a split similar to Wikipedia's). I rarely go to those pages simply because they are only linked to during community discussions, when there are no CotMs or PGotMs, and on the Community Portal. Since those are major areas of our community (especially requested guides), we should be advertising them more! -- 15:29, 11 January 2008 (CST)
 * The pages are rarely used, and don't really warrant addition to the sidebar. I can live with "Requested guides" but the other two do not belong there. -- Prod (Talk) 15:36, 11 January 2008 (CST)


 * Rarely used (for the reason that no one sees it), but extremely vital to our community. -- 16:08, 11 January 2008 (CST)
 * I think Requested guides should be there but I'm not sure about the others. But if we do put requested guides there, can we please edit the template at the bottom as many people are getting it wrong.-- The preceding signed comment was added by Rocky (talk • contribs). 16:57, 11 January 2008 (CST)
 * I just updated it. Well I think the other two should be there because its not just for sysops, especially 'cuz most of us deal with cleanup rather than content so we miss guides that others see a lot of...  Thus, not many guides have been voted upon (also probably because we don't have a lot of collaboration or massive guide improvement across many guides).  -- 19:35, 11 January 2008 (CST)


 * User:Notmyhandle's idea is excellent. Advantages include: existing members who have spare time will be drawn in; even better, some players who are googling for material about game X will be more likley to find StrategyWiki, and some will think "Hey, I can do that". Philcha 17:46, 12 January 2008 (CST)
 * I would be OK with adding a link to the requested guides page, but I think voting for CotMs and PGotMs should be something only more active members should do (as they've got the best idea of what's going on), and so I don't think the main menu is an appropriate place for the CotM and PGotM pages. --DrBob (talk) 18:46, 12 January 2008 (CST)


 * I always organize those three together as a group based on what their content looks like (requests/support/comments), and so perhaps we would like custom header nav that links to each of the three? I'm just trying to make it easier to find them first off (I have to search through random links in community portal and such, and often don't even remember them until the following month when we have a delayed CotM or PGotM when the link to the page appears...).  We need to utilize these better for our community - do we have them linked in the welcome message? -- 19:59, 12 January 2008 (CST)

More flexible guide structure needed
This arose out of a not particularly friendly exchange initiated by Ryan Schmidt (see User talk:Philcha and User talk:Ryan Schmidt). Ryan insists that articles about turn-based strategy games must be structured under 2 main headings, "Getting started" and "Walkthrough". He also jawboned someone else into re-assembling into 1 long page ( Master of Orion II/Getting Started) what I'd written as 3 sub-pages of "Getting started". This is simply not adequate for a complex TBS game like MOO II or Civilization III. And this is not just my opinion - I've edited bits of Total Annihilation and Starcraft, and the structure I found before I started was not just "Getting started" and "Walkthrough" (and I haven't changed it, only built on it).

My reasons for thinking a rigid framework of "Getting started" and "Walkthrough" is not enough for such complex games are:
 * Walkthrough" generally means mission / level "solutions", and using it in a wider sense will confuse new readers. It's quite unsuitable for games that do not have pre-defined missions / levels. It's even worse for games that have both pre-defined missions / levels and one-off skirmishes / standalone games (e.g. Total Annihilation and Starcraft), which need both mission / level "solutions" and a general strategy guide. In such cases the general strategy guide should come first, as it will explain points that are relevant to the mission / level "solutions", e.g. how to pump production so that you get the key units in time, or how to win battles with minimal losses (I hate limited-forces missions!).
 * "Getting started" can be a pretty complex topic, and Master of Orion II illustrates this in several ways:
 * The risk of malfunctions under Win 2000/XP/Vista is so high that the odds favour going straight to the MS-DOS version under DOSBox.
 * The MS-DOS version under DOSBox is the preferred option for multi-player, and makes it possible to use a patch and some mods developed by a very savvy group of enthusiasts.
 * Starting a single game requires a lot of decisions which the prospective player can't even understand with having an overview of the game's basic principles first. For example custom race design is very important in MOO II - and in more recent games such as Empire Earth. But that's incomprehensible unless you have a basic idea of how economies and research work in such games.
 * In a game as complex as this I think the main page should link to the "game overview" page so that potential players can look and see if they fancy the game enough to acquire and install the game and then learn all the principles.

So the sort of structure I think is needed is something like:
 * Main page (with link to "game overview" page if appropriate)
 * ToC
 * Getting started, possibly split into:
 * Downloading and installing
 * Game overview
 * Starting a game, possibly split into sub-pages:
 * Single-player
 * Multi-player
 * Strategy and tactics. Optional, as some games consist only of fixed levels / missions. May be split into many sub-pages, but the structure depends on the game. Common topics for TBS and RTS will include:
 * Race design
 * Initial build and research orders (which may partially depend on race design or choice - in Starcraft the 3 races differ some much that their build orders are very different - and critical if you're planning to rush.
 * Managing the economy
 * Rushing, raiding, porcing / turtling, etc.
 * Combat unit design, if the game has that option (MOO II has it in spades; so do a few other futuristic TBS games; and IIRC so do a few RTS games).
 * Knowing when to expand, when to keep making units at the current level and when to tech up.
 * Combat tactics - which will often have a lot of sub-pages.
 * Walkthroughs. Optional, as some games have no fixed levels / missions.
 * Solution to each specific level / mission. Philcha 17:41, 12 January 2008 (CST)
 * Let me first make it very clear that there is no way we can reorganise things to the extent that the "Walkthrough" page disappears completely; too much depends on it. However, I appreciate that the concept of a "walkthrough" doesn't necessarily map well to an RTS or TBS, and I've thought about this problem before. The best solution I've come up with for an RTS/TBS game which doesn't have predefined missions or levels is to have a short walkthrough page which explains how to start a game (whether it be a random scenario, or what) and gives directions for first establishing your team in the game, before linking to the various strategies you might need (i.e. linking to the "Strategy" page). This means that the "Getting Started" page shouldn't have much/any information on it about starting a game, and should just link to the "Walkthrough" page. If the game does have predefined missions, then the "Walkthrough" page should link to walkthroughs for them as you say. Other than that, I'm generally in agreement with what you say, and I'm hopeful that we can make this work and get some good guidelines for future guides put in place. --DrBob (talk) 18:23, 12 January 2008 (CST)
 * Just to clarify, I only was pushing for the "Beginning the game" subpage to be moved to "Getting Started", not every subpage under that heading. Both of the pages "Getting Started" and "Walkthrough" are integral parts of our navigation templates, although they certainly don't have to be well-developed, they just have to be there in some way/shape/form (even a redirect would be fine, really). Your format works well for your game, and if you wish to use it, go ahead as it still integrates the key pages that must be present (namely the Main Page, ToC, Getting Started, and Walkthrough; although a Controls page would be beneficial as well). I also agree that the structure of these types of games really need fleshing out, but I'm not being a horse's hind end on the entirety of the guide structure, just the very basic required components. Also, I edited out my siggy from your initial comment, please do not use it in your texts, but just a simple name or perhaps the user template. -- 20:12, 12 January 2008 (CST)
 * Indeed it was my choice to subpage the random content from the mainpage to Getting Started, and it looks like all of it applies (all basic concepts that don't relate to specific parts of the game, and since each section is so small and perhaps isolated from future subpages with a larger scope (i.e. units) it was in my best interests to promote slight redundancy. Considering the getting started page acts as both a ToC header and an actual page full of content, "game overview", "beginning", "installation", etc. all fit under that category.  -- 20:26, 12 January 2008 (CST)


 * Re length and internal structure of parts of Master of Orion II/Getting Started, we seem to have 2 votes for keeping it in 1 page ( Safety Skizzerz and Notmyhandle; and 2 for splitting it into sub-pages (the other one is Rocky, see  User talk:Philcha). I've already stated the reasons for my view, so I'll let that part of the debate run.
 * I'm seriously concerned about DrBob's comment that "there is no way we can reorganise things to the extent that the 'Walkthrough' page disappears completely; too much depends on it." The word "Walkthrough" has a specific meaning that is inappropriate and confusing for a game like MOO II. It looks like StrategyWiki has boxed itslef in with the way it has configured WikiMedia or the templates currently in use. I've done quite a lot of software development and in this situation the usual action is to fix the root problem and convert content / data where necessary, before the size of the problem gets larger. I don't have any previous experience with configuring WikiMedia, but I'd be willing to have a go if someone will provide the necessary info - config files and templates that are fundamental to StrategyWiki, how these lin together, and about 10 guides that I should use for testing on my own PC - I have plenty of spare disk space and can set up a test bed on my PC (I've developed in PHP, so that's a start).
 * As a short-term fix I'd suggest for games like MOO II a pro forma "Walkthrough" section that simply redirects to "Strategy and Tactics". Then there's probably a bot that can identify "Walkthrough" sections that only redirect (it might even be possible to use a standard link checker such as Xenu) and delete them after reconfiguration has removed the site's dependence on them.
 * PS I'm all in favour of standard layouts, provided they can support the full range of content. Philcha 04:51, 13 January 2008 (CST)
 * The problem is not just in the fact that many templates depend on the "Walkthrough" page existing, but also in the fact that all the documentation would have to be rewritten, and everybody would have to relearn everything. That's not a small thing to ask people, and if there's a way to fit a "Walkthrough" page in nicely with RTS/TBS games, I think it's worth pursuing. What are your thoughts on the rest of my proposal for using the "Walkthrough" page in RTS/TBS guides? --DrBob (talk) 06:12, 13 January 2008 (CST)
 * I appreciate the re-learning and conversion may be non-trivial, but the experience of the whole IT world indicates that it's better to face such problems before they grow even bigger.
 * Coming back to (temporary) work-rounds, is there any problem about creating a "Strategy and Tactics" "chapter" at the same level as "Getting Started" and "Walkthrough"? If there is no problem, that's what I'd prefer - and for missionless games like MOO II the "Walkthrough" page should just link to "Strategy and Tactics".
 * If having a "Strategy and Tactics" "chapter" is a problem, then something needs to be done about Total Annihilation and Starcraft), which both have a "Strategy and Tactics" "chapter". Starcraft currently has both "Strategy and Tactics" and "Walkthrough", which I think is right because Starcraft has missions; and IMO "Strategy and Tactics" rightly precedes "Walkthrough" because the later missions are complex and require plenty of economic management and combat techniques. Total Annihilation has no "Walkthrough", which I think is a mistake because Total Annihilation has missions. As I pointed out above, I did not create the current struture of the Total Annihilation and Starcraft guides, and I think that's evidence that someone else was unhappy with putting general guidance in "Walkthrough". Philcha 07:29, 13 January 2008 (CST)


 * I have to agree with what DrBob said earlier on the walkthrough being a rundown of the basics of how the gameplay/strategy works. Personally, I would put everything that goes into installation and setup (before the game is to the point of even running) in “Getting started”. Especially for a game that sounds like it has some fun and/or required downloadable stuff and is played over the internet.


 * In walkthrough I would put game setup (choosing your race and setting variables, ect) or go over general beginning strategies that are the foundation of becoming a decent player. The things veteran players do automatically without thought but could take a while for a beginner to pick up. These strategies would be things that are universal between the races like “how to efficiently produce and manage resources”. If anything is “advanced” enough in the subpages to make no sense to a novice then these top category links are perfect for clarifications or quick summaries of whats below.


 * Do note that while large amounts of a guide haven’t been subpaged they normally live in places like the walkthrough page. Worst case scenario the still unorganized info could hang out there and I bet it will be obvious how to use the page once everything has a home (hmm, what’s left? Does that need explaining? Is it really clear what Those sections are?). --Zaiqukaj 06:46, 13 January 2008 (CST)
 * You can have whatever headings you want (you don't even need Walkthrough in the Table of Contents, you can replace it with "Strategy and Tactics" and just make Walkthrough redirect there. The only requirement is that the page exists, not that it has to have anything in it besides a redirect. As for Getting Started, don't assume that I voted for having it long. I just wanted the Table of Contents-type thing originally in Getting Started moved to the real Table of Contents and the contents of "Beginning the game" moved to "Getting Started" because the two page names are synonymous with each other. If you don't like it that long, go ahead and split it up into sub-pages. As for config fixes, everything format-wise is done at the wiki level, there is nothing that dictates how the guides are layed out that's actually in the filesystem. -- 08:52, 13 January 2008 (CST)
 * Zaiqukaj has done a good job of re-iterating and explaining my point, and I'm still not sure why you haven't directly addressed this idea, Philcha. There's no problem with creating extra pages such as "Strategy and Tactics" pages, but we can't remove the "Walkthrough" page. The redirect on Total Annihilation's walkthrough page was actually created by me, so that until someone wrote walkthroughs for the missions in the game, people reading the guide would at least be able to easily find the strategy information, instead of being presented with a big red link for "Walkthrough". That redirect can – and should – be deleted as soon as someone writes some proper walkthroughs for the game's missions. --DrBob (talk) 10:59, 13 January 2008 (CST)

Simplification
I think this topic has gotten out of hand mainly because of misunderstanding on Philcha's part. Here's the section you should take a look at: Guide/Organization. I think you should be able to easily understand that the Walkthrough section is a standardization policy of SW's and its content definitely varies from game to game, and DEFINITELY does not contain an entire game's walkthrough. -- 19:58, 13 January 2008 (CST)


 * Thanks. From my point of view the wording of Guide/Organization indicates that it was designed for e.g. FPS or RPG without taking much account of TBS or of the skirmish and multi-player aspects aspects of RTS (especially those that generate random maps, e.g. Age of Empires, Empire Earth). But I noticed the words "The redirect on Total Annihilation's walkthrough page was actually created by me, so that until someone wrote walkthroughs for the missions in the game, people reading the guide would at least be able to easily find the strategy information, instead of being presented with a big red link for 'Walkthrough'" in DrBob's post of 10:59, 13 January 2008 (CST) under  More flexible guide structure needed. I think that implies that permanently redirecting "Walkthrough" to "Strategy and Tactics" is OK for games that have no pre-defined missions, and that games that have both skirmish / multi-player and pre-defined missions should have both "Strategy and Tactics" and "Walkthrough" - which is what I thought would be a good approach. Philcha 05:15, 14 January 2008 (CST)


 * No, it's definitely NOT a permanent thing, as DrBob said in his post - after you actually create pages for the levels, then we can create suitable content for the walkthrough page to help link to the various ways the game is set up (by you or whoever). Please see StarCraft's ToC for campaign split ups.  A page for general strategy is fine.  The "walkthrough" section of any guide exists for larger guides mainly to introduce the walkthrough and explain how the walkthrough is split up and written (thus the walkthrough section is more effective when it is created at the end of the guide writing process, otherwise it is quite lacking).  For no predefined missions whatsoever, then yes the Walkthrough section will either become a general strategy page (debatable) or a place for redirection (links to whatever subpages).  Strategy and Tactics is definitely a good section to have, I don't see why you can't add it, did anyone ever stop you from doing that part?  -- 06:10, 14 January 2008 (CST)

Sections on Halo
Maybe see if you guys can strike up a partnership with Halopedia in the same manner you guys have one with Bulbapedia for Pokemon stuff. Just a suggestion. --Arrow Windwhistler (talk) 10:39, 14 January 2008 (CST)
 * I'll contact them (I know a few of the admins there), but I can't guarantee any results -- getting partnerships with Wikia wikis are iffy at best. -- 15:26, 14 January 2008 (CST)
 * Make sure to keep the Guide/Partnerships page updated. --DrBob (talk) 00:27, 15 January 2008 (CST)

It turns out they already have walkthroughs for all the games, so this partnership wouldn't really work out, as we don't have anything that they don't have (I DID talk to some of the admins of Halopedia on IRC, they came to that conclusion as well). On the plus side, they're GFDL... -- 17:38, 23 January 2008 (CST)

Total Annihilation Units
I've had disussions (see User talk:Notmyhandle) about the layout and content of Total Annihilation/Units. We started from the idea that: there's no point in listing ARM and Core units separately since over 80% are the same apart from a few % difference in cost and / or performance; and combining them makes it easier to describe any differences that are significant. I've also added material on the strengths and weaknesses of some. I'd be grateful if people could review this and leave comments at my Talk page. My main concern is the potential length of the article. I see no point in just listing all the units as that tells the reader nothing apart from their names. The options I can see for dealing with this (other ideas welcome!) are:
 * Split them into separate sub-pages of Total Annihilation/Units (within Total Annihilation/Getting Started for each category (Kbots, vehicles, aircraft, etc.)
 * Move the lot to Total Annihilation/Tactics and Strategy Guide, with separate pages for each category (Kbots, vehicles, aircraft, etc.), and simply  say in Total Annihilation/Units that the manual (give download link) provides basic descriptions and pictures. Make the result a "Unit Tactics" group of pages and incorporate existing unit tactics content from  Total Annihilation/Tactics and Strategy Guide.

The other question I'd like comments on is whether to list on a separate sub-page the units added by the Core Contingency expansion pack (about a dozen per faction IIRC), or combine with the original units and simply note "this is a Core Contingency unit". Philcha 03:27, 17 January 2008 (CST)
 * The expansion pack elements will be covered in a separate page under the expansion pack (once the expansion pack page is created, we'll help create an adequate ToC to reflect navigation between the main game and expansion pack). For an example, see Diablo II/Table of Contents.  -- 19:12, 18 January 2008 (CST)
 * Thanks for clearing up the expansion pack issue.
 * I'd still like some comments on my question about unit descriptions for OTA. Philcha 11:01, 21 January 2008 (CST)


 * I would normally put Units under an Appendix, but given a focus on adding tactical information for the units moving them to the appropriate section makes sense. I'm currently working on getting together some of the unit stats to fill out the existing information (which may also help with comparisons of the units between ARM/CORE; thankfully with a game that's been so thoroughly modded, the tools to pull the stats straight out of the game are readily available). Of course, I'm also trying to figure out which stats are actually useful, because no one needs the full list of stats just formatted and displayed here (obviously a ship is either a floater or underwater, we don't need the stats to tell us that). -Vizeroth

Header Nav |custom revamp
After noticing quite a few usages of the |custom parameter of Header Nav in guides for things such as arcade fighting games, I've come to the conclusion that this parameter is badly thought-out. The pages in a guide typically aren't going to each have different custom page lists in the HN — they're all going to have the same page list, so it's pointless to have to include it each time. I propose that we replace all such usages of |custom with functionality in Header Nav to transclude a standard page per-guide (if it exists) which would provide the custom links. So for example, we'd put all the custom links on "Guide name/Guide Navigation" (CamelCase to differentiate it from normal guide pages; suggestions for a better name welcome), and the HN would transclude that. This would allow us to get rid of templates like " ", and potentially allow us to get rid of the |custom parameter completely, unless anyone can think of a legitimate use for having different links in the HN for each page. --DrBob (talk) 07:05, 20 January 2008 (CST)
 * Check out MapleStory for something that uses something entirely different for the |custom in the Header Nav for each section of pages. But I do agree that it would be better if we could move some of this guide-specific stuff out of the template namespace (like the HN links, and those MapleStory availability charts). -- 09:51, 20 January 2008 (CST)
 * Of course, even MapleStory can be adapted to use that central navigation, it would just take quite a few #ifeqs. -- 09:56, 20 January 2008 (CST)
 * It's difficult to answer this in context since there are two parallel conversations taking place here and on StrategyWiki_talk:Move_lists_project, but I feel that this problem affects more than just fighting game guides specifically. I think one of the points that WretchedSpawn made to me that resonated most with me was that certain types of game guides, namely Fighting, Puzzle, and Sports, do not need, nor contain a Walkthrough.  And yet we know that we have, as DrBob points out, architected the site around the Walkthrough page which in truth is needed for a majority of games.  The problem is, we don't deal with the exceptions very well, and we try to shoehorn them into our format.


 * Now I'm not proposing that we change our format, but I do think the flexibility of our guide format does need to be examined (as it was raised above, although for a slightly different, and predominantly misunderstood reason.) I would like to propose that Header Nav remain as is, and that we make a few exception navs for, say, Fighting, Puzzle, and Sports games.  The navs for Fighting games can point to BASEPAGE, TOC, Characters, and Moves.  The navs for Puzzle games can point to BASEPAGE, TOC, and Rules.  The navs for Sports games can point to BASEPAGE, TOC, and Teams.  Something along these lines that reflects a more intuitive navigation that users might be inclined to be seeking.


 * Now, obviously, the Walkthrough page should exist for every guide that we create, but it can easily be redirected to one of these alternate genre page names, so the page won't disappear from usage, and the alternate genre games don't stray from our required usage. This is something that I would like the members of the site to consider, and see if it wouldn't be terribly difficult to develop.  Procyon (Talk) 14:23, 21 January 2008 (CST)
 * That shouldn't be hard at all to develop, it would just be hard to get used to :P (after all, we USED to have a different nav for each game, then bundled them all up into the AGN, then renamed that to the HN, and now we're talking about splitting it up by genre now... seems perfectly normal given past history). Although, we could probably change the links automatically by testing what category the game belongs to -- if it belongs to a certain category, then certain links are displayed custom-fit for that genre. -- 16:25, 21 January 2008 (CST)
 * That's an even better idea Skiz! You could test for it, but if a game belongs to multiple genres (rare, but possible), you end up in stick situations.  I would say it's just as easy to feed it by optional parameter, so that you have something like , which would automatically replace the Walkthrough link with something more appropriate.  Again, I'm not suggesting that we do away with the Walkthrough page at all, it has to exist, but there's no reason why it can't be a #REDIRECT to something more purposeful.  Procyon (Talk) 16:51, 21 January 2008 (CST)
 * Well, I'd be using a #switch statement except testing categories if we do decide to go along with that, so the first genre it matches is what links are displayed or the default if none are found. The reason why I mentioned the automatic way is because of the fact that it's entirely automatic and doesn't require user input from every subpage. The extension is CategoryTests btw, I'll revise it soon to allow testing of other pages :) -- 17:52, 21 January 2008 (CST)


 * I won't support the use of automated nav's unless it is as flexible as hardcoded edits. What about games that have cross elements, like a puzzle game with characters or what not?  Or a fighting game with a walkthrough (can anyone say Mortal Kombat: Armageddon?)? -- 19:01, 21 January 2008 (CST)

The automation by genre would be in addition to the custom links that DrBob suggested so that each game can have all the important links in the header nav and have it custom-fit to each game. Also, I added that functionality to the CategoryTests extension, it can now test other pages. -- 20:34, 21 January 2008 (CST)


 * The HN is used on 99% of the pages on the wiki, and should be as simple as possible. For the original topic of this thread, I would say we use Game/NAV, but keep the |custom parameter.  If we do that, I'd suggest getting rid of those navs instead of hacking up the NAV page with #if's.  The other option is using 'BASEPAGENAME instead.  That way pages below MapleStory/Jobs get MapleStory/Jobs/NAV; MapleStory/Quests would get MapleStory/Quests/NAV.  I am very much against the HN depending on the main page.  If someone edits the ToC in a big guide, it affects the job queue.  Main pages are the most visible and therefore major vandal targets, and that would actually affect us.
 * As for the other genre specific things, the simpler the better. I'm mostly against it in general, since Walkthrough should be synonymous with guide.  That's why Getting Started is optional, if it can all go under walkthrough, you don't even need the GS section. -- Prod (Talk) 23:32, 13 February 2008 (CST)

Two features - do we have them, and if not can we get them?
First, I've just noticed that on Wikipedia there's a new option in your preferences that will put section edit links in for section 0 (the header). Can we can get those for SW, either as an option or standard for everyone? It would make things a lot faster for editors who just need to edit the intro, as well as save a considerable amount of bandwidth over time as we wouldn't have to download and then re-upload the entire article (multiple times if you count previews) just to change a small section of the article.

Second, the file upload page has a link to Special:MultipleUpload, though it is red. Can that feature be activated? It would be a huge time saver for those of us who have to upload a lot of images at once. If not, that sentence should probably be removed from the page. - Koweja 18:25, 20 January 2008 (CST)


 * I believe the extension is currently not compatible with the new version of mediawiki (correct me if I'm wrong), so we must wait. -- 20:26, 20 January 2008 (CST)
 * Reply to first part: actually, it uses MORE bandwidth to only edit a section, as the entire page text must first be loaded, and then cropped to only that section. And upon the save the section has to be re-inserted into the page text and the entirety of it saved again, so no bandwidth saved at all there. I'll look into seeing how we can get options for that though.
 * Reply to the second part: MultipleUpload is broken for 1.11+, so all we can do is wait (I'll take it off the upload form text tomorrow, g2g to bed now >_>). -- 22:19, 20 January 2008 (CST)
 * Okay, I though the software saved each section of an article as separate entries in the database and just put them all together when needed. Good to know. Thanks for the fast replies.- Koweja 23:23, 20 January 2008 (CST)
 * If only we got paid for them ='( -- 18:54, 21 January 2008 (CST)

Ok, I've created a small script repository, one of the scripts is that edit-the-first-section-link modified for use on StrategyWiki. -- 15:41, 22 January 2008 (CST)
 * Holy crap, that search script is awesome. Thanks! - Koweja 18:41, 22 January 2008 (CST)
 * The MultipleUpload extension has been updated to work with 1.11+ (with one minor patch), so it'll probably be re-enabled next we update MediaWiki. -- 20:14, 14 February 2008 (CST)

Featured guides
Hey, I just wanted to see if you think we're ready to promote two of our featured guide requests. Red and Blue as well as Midway look really slick and have lots of support. echelontalk 23:43, 21 January 2008 (CST)
 * If you or any sysop feels that a guide is ready to be featured, just do it ^_^ Here's a step-by-step process:
 * Move the featured nomination section from Featured guides/Current requests to Featured guides/Successful requests
 * Add a blurb to Featured Guide/2007-08 (follow the directions in comments in editing mode)
 * Add featured to the /Table of Contents sub-page of the featured guides.
 * Change the num parameter to 5 in the Header Nav on the guide's main page.
 * 11:59, 22 January 2008 (CST)
 * Decided to get off my lazy and do it myself ^_^ -- 17:18, 23 January 2008 (CST)

Glitch in new version of image upload
When uploading a new version of an image, the warning script blocks you from submitting unless you add categories. I'm able to get around this, but I bet others are not (I have an add-on for Firefox that lets me disable javascript on the fly). Any way we can fix this?-- 16:55, 22 January 2008 (CST)
 * Yes, you put a category into the image summary (actually, only "[[Category:" is needed). The categories aren't applied anyway on re-uploads. -- 16:26, 23 January 2008 (CST)
 * Good to know, but it's still a useless prompt... I hate the bug reporting process =/ -- 22:03, 23 January 2008 (CST)

Halo 4 rumeors
There is some rumors going around that bungie is making halo 4 they broke off with Microsoft so they mite have to make a new halo also if they do its not going to be for the 360 cause they want to get back at them so people looking for a good ps3 game look no further its supost to come out in summer 2009 VvarlockVvarlock
 * Nobody cares . This place is for discussion about StrategyWiki, not for random game chat. If you want to chat about games, go to ABXY. -- 11:57, 24 January 2008 (CST)
 * Or IRC!. -- 12:27, 24 January 2008 (CST)

Series template sub-series listing "policy" needed
After the discussion on Template talk:Mario, I was about to add all the series to the template and then I just became really conflicted as to what to do. Do we want every sub-series listed there and on other game series templates, or do we have some way to differentiate between them? Right now there are 8 series (and Luigi, is Missing, Kart, Paper, Party, RPG, Super Strikers, and Tennis). If there is a sub-series, it should be listed right? But like, Paper Mario us a sub-series of RPG so you might think oh we don't need to include it... Or like  Super Strikers and Tennis - I had this idea that we could congregate those into a category called "Mario Sports" which would include all of the miscellaneous games (Baseball, Basketball, DDR? lol). I dunno what to do. -- 18:16, 24 January 2008 (CST)
 * Uh, why not just include them all? It's not like we're putting anything under the series nav anyway, so there is really nothing to worry about in terms of a huge nav. If things get too big, we can start listing categories instead of games, but I don't think it'll ever get to that point. -- 20:47, 24 January 2008 (CST)
 * For any problem like this, the solution has always (unofficially) been to not include recursively. In this case, this would mean only linking to the categories which are direct subcategories of Category:Mario. That's what I've always done. That whole category is a bit of a mess though, so you might want to re-think all the subcategories anyway. --DrBob (talk) 01:29, 25 January 2008 (CST)

Move Lists Project
I'm wondering if maybe someone can write up something for the Move List Projects page. Currently there's no info there and I think it can use maybe a guideline on how the Move Lists work. (It confuses me... I was thinking about working on something for Smash Bros. pages, but I don't know how the standards).-- Duke  Ruckley Talk 16:45, 25 January 2008 (CST)


 * I know that this will sound ridiculously ironic, but as good as I feel I am at writing video game guides, I don't feel that great about writing writing guides. But I suppose I really should accept responsibility for this task, since I'm one of the principal architects.  I'll see if I can force myself to stop adding game content and take some time to write this.  Off-hand, I would not think that Smash Bros., as a series, is really applicable to the fighting games move list project since there aren't any joystick motions you have to learn, just direction and button combinations.  However, that may just be me being short-sighted, and they may lend themselves very nicely to one another.  Procyon (Talk) 18:05, 25 January 2008 (CST)


 * If Smash Bros. doesn't really fit the mold, then that's fine. Like I said, I'm not sure exactly what is involved with the movelists and (more importantly, I think) how it's organized.  Take your time on it too...  It's not really something extremely important right now anyway.-- Duke  Ruckley Talk 20:03, 25 January 2008 (CST)


 * Indeed, smash bros's system is very simple, however it could be set up the same way as other fighting games. Although there are no combos, they could still be laid out in the same table format - however SSBM has additional details that are very useful and I don't think converting it would do any good at all.  -- 03:40, 26 January 2008 (CST)

Where is the new game guide button?
I want to start a game page for Final Fantasy Crystal Chronicles for the gamecube, but I can't find that button on the page.

I looked at the guidelines for making a new page and it tells me about this new game guide button.

I can't seem to find it anywhere.


 * If you go to an empty page and click edit, you'll see 4 small gray boxes above the edit box labeled as "Main game page", "Guide page", "Company page", and "Table of Contents." I'll add a screenshot to the guide this evening.  -- 04:27, 5 February 2008 (CST)

Command & Conquer 3 Unit Template
I can get to work on that, but a template would be nice to organize data better, including
 * Type (Armour, infantry, building)
 * Attack type
 * Cost
 * Special abilities

Stuff like that to supplement a description. --Arrow Windwhistler (talk) 09:18, 6 February 2008 (CST)


 * Should be brought up on the C&C 3 talk page... -- 00:06, 7 February 2008 (CST)

Also on that Template for infantry and other CNC 3 Units we need the following things.


 * Numbers for an infantry squad like 6 for the Riflemen Squad
 * Role like Heavy Assault
 * Armour like heavy for tanks

(MrSue 00:56, 7 February 2008 (CST))

Common.css
Do the Chrono Trigger specific styles really belong in there... I understand the reason for putting it there, but it's specific to a single guide (everyone loads the css for the <1% that'll actually use it?) -- Prod (Talk) 10:32, 6 February 2008 (CST)
 * All of the guide specific template css changes to global were for the idea of multi-skin friendly templates - however I'm not sure if this is a good idea anymore, considering the files continue to grow in size, and alternate skins are only used by like .0002% of our viewers. Is SW really just a blue-cloud friendly wiki?  -- 21:17, 6 February 2008 (CST)

Appendices: Footer Nav Prev/Next Page Standardization
I doubt this has been addressed, but since we created the ToC layout structure I've always felt that the pages listed under Appendices shouldn't have their footer navs have previous and next page links, considering the appendices should be unrelated to one another (otherwise we group them together). However! I have no problem allowing appendices to have these navigation links. I would like to establish a policy for handling it though - does every appendix need these links? If so, we have many pages to do... What do you guys think - should we keep things logical, or provide readers with increased ease of use?

Additional/Summary thoughts:
 * The links provides additional navigation between subpages.
 * The footer nav already allows the entire ToC to be visible.
 * Appendices are primarily unrelated to one another (i.e. not in a series). -- 14:30, 8 February 2008 (CST)


 * IMO they should have an FN and use the prevpage/nextpage parameters. This allows someone without javascript enabled to easily navigate through the guide in sequential order (based off the ToC), as well as facilitate people that are too lazy to show the ToC itself (two clicks and perhaps a scroll versus one click). Plus, it looks really dumb when you have two links to a guide's main page within 50 pixels from each other. -- 15:07, 8 February 2008 (CST)


 * The FN is a standardization of ALL subpages, regardless. Also, I've noticed that some people don't realize there is a "show" button on the HN/FN.  I think adding it will add useful redundancy.  Anyone opposed to this (adding prev/next pages) to ALL footer navs?  Additionally we need to come up with a standard way of linking to and from columns (groupings).  Since we have it go Getting Started to Walkthrough, it only makes sense to link by row, not column - i.e. the last walkthrough page will link to the first appendices page (or section of the ToC in that location).  The problem then, is when a guide is developing, the pages get moved around a lot - thus maybe we should reserve this standardization to only level 4 guides and above...  -- 23:14, 8 February 2008 (CST)

Guide ToC
After a bit of discussion on my talk page, I've decided to bring this up on CI. Anyway, the current ToC for the guide is rather lacking in terms of thought when the appendices section was arranged. Therefore, I've started up a test in the sandbox for everyone to rearrange as they think right (although discuss it here to let people know WHY you did that in case it isn't obvious). After a bit, we'll have a bit more formal consensus from a few select revisions of it to decide upon and eventually implement. Have fun :) -- 09:08, 10 February 2008 (CST)
 * Some of the policies I feel would be better served within the guide itself instead of under a policies subsection. To give an example, "Account Naming."  Wouldn't it be a good idea to stick that under "Sign up" so that people see it before creating an account (I'm assuming most people who want help signing up aren't going to look at the "Policies" section first)?  If we place policies within the guide itself, we can then have a "Policies" page under "StrategyWiki" or "Contributors" and then have that page compile any policies we haven't mentioned.  Further, for policies that are within the guide, the policies page can have a link to those.  Not a big deal, by any means, but it might be a good idea for some policies.  Oh, and it'll clean up the ToC just a bit more.-- Duke  Ruckley Talk 10:11, 10 February 2008 (CST)

Next staff meeting
Anyone know when the next staff meeting is being held? Also, agenda would be nice too :) -- 19:53, 14 February 2008 (CST)