StrategyWiki talk:Community Portal

This talk page is for discussion of general community issues. To start a new thread, insert a new subheading above the rest. ''Resolved threads removed one day thereafter. You can find them in the history.''

Discussion archives:
 * Issue 1

Console Naming Convention
Looking at the Categories page, it looks to me like we're lacking a clear naming policy for consoles. My concern is that the systems will not have consistent names; some systems will have the name of the company that developed it prefixed (for example, Sony PlayStation) and some will not (for example, simply PlayStation). Unfortunately this is a somewhat confusing issue because so many people are used to saying the full, developer-prefixed name of the system.

I personally think that we should avoid prefixing the company name wherever possible. There are some systems for which it is obviously appropriate, like on many Nintendo Systems ("Nintendo Entertainment System", "Super Nintendo Entertainment System", "Nintendo 64"), but if the name is recognizable enough without the company name, we should drop it, leaving for example names like "Genesis" or "PlayStation 3".

Please let me know what you think. --Doozer 17:06, 10 January 2006 (PST)


 * Systems should have a "long name" for category and a "short name" for disambiguation. Nintendo 64 and N64, Nintendo DS and NDS, Playstation 2 and PS2. So on and so forth... --Echelon 17:52, 10 January 2006 (PST)

Art/Screenshot of the Week
Feel free to suggest. Upload all of your candidates and post them on the talk page for Main_Page. --Echelon 02:47, 8 January 2006 (PST)

Series Guide?
Should there be guides for game series (Zelda, Final Fantasy, Warcraft...)?
 * I think so. It remains to be seen how we'll accomplish this, however. I'll be working on Ocarina of Time first, followed by Majora's Mask. At that time I'll find a way to link the Zelda games together. --Echelon 13:25, 7 January 2006 (PST)


 * Perhaps we should think of incorporating Wikipedia entries for the game series in some fashion? Either a link or the actual article might work. StrandOfLight 01:37, 8 January 2006 (PST)


 * While we're not an informational database on games (there's already a wiki just for that, and there's also wikipedia), we can incorporate any GFDL materials. I would suggest that we use what we can while still maintaining a mostly-strategy guides policy. Some background information can be nice, but let's not import purely informational articles about the history of, say, Mario Bros. At least that's my two cents. Echelon 02:10, 8 January 2006 (PST)
 * On that note, I recommend an "external links" section for single-page guides or "More information" page that includes "external links" for games in the book format.


 * Ooo I like colons. Anywho, check out Final Fantasy or Zelda.  Are those what you're talking about?  You could always include extra pages relating to what links them all together, etc. -- ArlanKels

Console Designation in Title?
Should there be a standard for including console names in game titles? There are often differences between the each console's edition, so perhaps we should create a Disambiguation page for each multiple-console title? Perhaps the title listing in every index page can link to the disambiguation, with "Title Name (Console)" for the actual item. If the differences are extremely minor, then perhaps a single guide page, and a separate "Differences" section or page. Thoughts? --StrandOfLight 01:55, 8 January 2006 (PST)
 * Yeah, this is most definitely what we shall be doing. If the differences are minor, there will only be an addition of a "versions" page. If the games are entirely different, however, they will be in the wikipedia-style disambiguation. Good to state it for the record. We should put this in our policy somewhere. --Echelon 02:05, 8 January 2006 (PST)
 * Aside from game controls, special moves (fighting games), and cheat codes; do any games actually exist where the plot is different from system to system?--RandomSkratch 14:28, 8 January 2006 (PST)
 * Sometimes a title can be deceiving. Note many movie- and TV-licensed games appear on many consoles including handhelds. King Kong is one example. The Game Boy Advance version of that is most certainly different from the Xbox 360 version. We should have one guide for each version of the game that is distinct enough from the other guides to need completely new information. However, there are times when a game is mostly the same but not quite. Silent Hill 2 is one example; when it came out for the Xbox it had some additional content, if I remember correctly. That should be included in the "Silent Hill 2" guide but the fact that a section only applies to one version should be noted. --Doozer 20:47, 8 January 2006 (PST)
 * Should we implement this right away then, in terms of renaming all of the existing guides? Also, should we start recording this sort of policy in StrategyWiki policy pages? --StrandOfLight 19:35, 9 January 2006 (PST)
 * I just started Standardization. I won't be able to edit it until tomorrow afternoon, but by all means feel free to jump in. We need some standards in place. --Echelon 02:30, 10 January 2006 (PST)

Standards & Conventions
I think it's better to start addressing the issue of standards and conventions sooner rather than later. So, some of my initial suggestions: We should try to model information on Controls after a game's instruction booklet. Buttons should be in bold, and each function (if there is more than one) should be separated by a semicolon, with any side-notes about the control below and bulleted. See the Ocarina of Time page for a good example. Pictures should be relevant, important, and kept to a minimum. On the SSB.M page for example, the pictures of Mario, and Bowser crushing Kirby seem unnecessary to me, and they both have poor, uninformative captions. We should concentrate on informative pictures like maps first, I think. Objectivity needs to be kept in the guides while opinions like "Ness is the best character known to date" need to be kept out. Spelling and grammar need to be checked by everyone before they edit something, at least by just copying the text into MS Word and looking for any misspellings (that's what I do). Please also check capitalization of things like "Gold Skulltula." Although the strategy for the beginning of Ocarina of Time is more interesting to read than a simple "go here, do that", I think we should consider whether our primary purpose is to entertain, or provide useful information. Text like "but Link knows deep inside that this was not to be the happy day his friends would expect it to be" is unneeded and, even worse, is completely made up. No one knows what Link thinks, so don't write about it. -- Ashandarei 16:37, 8 January 2006 (PST)


 * Everything you bring up is very, very timely and couldn't have been better stated. The last statement was especially important, as that was more or less my fault. I'll get to work and address these issues, especially the editing standards which will need to be delt with ASAP. --Echelon 01:53, 9 January 2006 (PST)


 * On that first note: maybe we should develop an blank image of a controller have people use that template to make a image for Controls...because informative visuals are good. ;) --Spiritsnare Flux 07:16, 9 January 2006 (PST)
 * I would really like it if we did that. But we've got to find some good diagrams. --Echelon 11:44, 9 January 2006 (PST)
 * Perhaps we should use high quality scans of the controller diagrams in the manuals. A high-res scan, then clean it up in Photoshop/GIMP, and use it as a standard on all "Controls" pages.  I think it would also fly under | fair use laws. --StrandOfLight 19:48, 9 January 2006 (PST)
 * That would be great!! I can't get them myself, but three cheers to someone who does! What a teriffic way to do it. --Echelon 01:59, 10 January 2006 (PST)
 * Sounds good. There's already a vast number of scans at sites like http://www.replacementdocs.com and http://www.hqscans.org. You'd just need to extract the images with a PDF disassembler. It might also be beneficial to develop button graphics like these for cheats etc. rather than constantly writing out the textual equivalent. Garrett 13:23, 11 January 2006 (PST)

Developer Pages?
Do we want pages for developers/publishers and the like? Right now I don't think there are any, but I think it would be a necessary addition. --Poody
 * I think that's a great idea. I've been thinking of getting started on those but hadn't gotten around to it yet. If you want to begin making pages for publishers/studios then by all means please do! --Doozer 23:28, 8 January 2006 (PST)

Regarding copying from Wikibooks/Wikipedia
Hey, there's a little bit of a hitch here guys. The GFDL requires credit to be given, which you aren't currently doing. Please see the crediting examples on Wikibooks or Wikipedia for more on this. About also needs to be changed to reflect this.

Also I personally think it's silly to mirror content that another site already has editable; all you'll end up with is different improvements to the same source work on each wiki it's been copied to. Gameinfo in comparison merely crosslinks to the other wikis' guides.

Anyway, if you could clear that up that would be great. Thanks! Garrett 20:05, 10 January 2006 (PST)
 * I believe that the guides will receive much more attention - which they need, on Stategy Wiki. There is a dedicated team, all of whom are game enthusiasts, at Strategy Wiki whereas Wikibooks would not normally be a gamers hangout. Jackhynes 09:08, 11 January 2006 (PST)


 * I will get on this issue immediately by creating a template to show that a source comes from Wikibooks. In the end, I agree with both Garrett and Jack on certain issues. Garret stresses that it would be redundant to have two branches of the same source--I agree. Jack believes the guides will get more attention here--I also agree. Right now, I think I have a possible solution. I would say that we keep the wikibooks guides for the time being until StrategyWiki has established itself. Once we have done so, we may work on creating our own originals for the guides from Wikibooks. This is only a thought, but I think it addresses both issues. For now, I will merely apply the templates to denote the source of these guides. Thank you Garrett for letting this be known to us. --Echelon 12:16, 11 January 2006 (PST)


 * If you see an article that has been taken from Wikibooks, please use Template:Wikibooks --Echelon 12:22, 11 January 2006 (PST)


 * You're welcome. The issue of how sites should link to each other still needs to be addressed though, even if Wikibooks' content were permanently moved here. Hm. Garrett 13:26, 11 January 2006 (PST)


 * I have modified the template as I believe that reference/link to the GNU FDL is needed when using material from Wikibooks. (From the article on Wikibooks)
 * Use on the Internet


 * For specifics read: GNU Free Documentation License


 * 1. Mention Wikibooks as the source (not mandatory; but appreciated)
 * 2. Provide a functional link back to the Wikibooks book or Wikibooks module (this satisfies the author credit requirement of our license)
 * 3. State that the text is available under the GNU Free Documentation License
 * 4. Link to a copy of the GNU FDL license (preferably stored on your own server).
 * 5. Your version of the text must be machine readable (meaning you cannot prevent others from copying the text)


 * I just want to say that I also agree with Garett about problems with having two copies (it was my original argument against having a different guide for the same game on different platforms). Despite this I believe the guides at Wikibooks are contributed too far too seldom and lots of the information comes from a small number of users (i.e. Garett). Therefore the guides will not become stale here as they have at Wikibooks. Jackhynes 13:34, 11 January 2006 (PST)

Google Ads to help fund the site?
Wikicities has a Google Ads sidebar. You've already got this side area blank, so why not put some ads in there? No matter how small the income if they help keep the site afloat it's a Very Good Thing. Garrett 13:26, 11 January 2006 (PST)