Project talk:Wiki Conventions

So, I've been working on this in my spare time, just wittling away at it. I had intended to keep at it myself till it was more complete, but with all that's been going on I've neglected it a bit, plus Kolano is doing something very similar with the Infobox VG template documentation, so I figured it was time for me to open this up and get some help. This wiki is colaborative, so let's work together on it. The only request I have for the style of this is that it avoid "rule" language. Thou shalt and thou shalt not type stuff. Just read the "preamble", and you'll get it. I'd like to be open and inviting, focused on how we do things and why, and not be bossy. I'm not sure I got that standard myself, but that's the goal for me.

So, first up, the things that are wrong with it right now. You'll notice there's alot of blanks, but that's just stuff that isn't complete yet. The broken formatting is the biggest issue for me right now.
 * How to format the opening. Putting the "preamble" up top created a situation where there is this tiny bit of text up at the top against the header, and then the giant contents box, then the information people wanted. It made the preamble completely invisible!
 * Seriously, how on earth does one get multiple lines into  code? I tried everything without any luck. Anyone have any better ideas for that section?

- MaJoR (talk) 08:11, 17 November 2012 (CET)


 * If you want multiple lines in the  tag, you must insert a space infront of each line. I've fixed the lines in the page already as a test. As for the preamble. I think the preamble and methodology can be merged into one section since it seems like they have a similar intention. ─ Garteal (talk) 14:01, 19 November 2012 (CET)


 * ...of course it was somethings simple. DOH. Thanks. As for the merging of the preamble and methodology, I thought about it, but I wasn't sure how to make it flow well from one to another. I'll try again sometime soon. - MaJoR (talk) 14:16, 19 November 2012 (CET)

FOV patches
I think there should be a convention to that can support FOV changing here because certain amount of people want to adjust it for a nice view something like zoomed out.--Brandondorf9999 (talk) 22:09, 15 July 2015 (CEST)


 * I oppose adding FOV codes; they modify the way the game was intended to look and it's a lot more invasive than a simple widescreen fix, 60FPS codes or cheats to bypass emulation issues (like ZTP patch). Also, from the recent troubles regarding cheat codes, only you showed interest in adding these kinds of codes while the majority of other wiki admins and active users are against them too. Jhonn (talk)


 * Well you need to support them. It's not invasive, it's an enhancement. Also, it should be like other games where you change FOV on like Call of Duty.--Brandondorf9999 (talk) 00:19, 16 July 2015 (CEST)


 * We do not. There is no FOV codes indicated for any of the Call of Duty games on the wiki, so I'm not sure what you are talking about there, I suspect you may mean the PC Call of Duty, which has nothing to do with this wiki. In general such codes augment gameplay in ways that were not intended by their developers, which is specifically counter to the goal of enabling accurate emulation here. Kolano (talk) 02:15, 16 July 2015 (CEST)


 * There is a Call of Duty wii game with the FOV code submitted by Bully WiiPlaza and it's located somewhere in that gecko code page. That one's called Call of Duty: Modern Warfare 3.


 * Another note is that it's proper emulation, but some of them have bugs. The game in question can have more FOV than the one they adjusted it for.--Brandondorf9999 (talk) 03:21, 16 July 2015 (CEST)


 * You're still the only one showing interest in adding them, so, not gonna happen, as I said, the majority here is against. Jhonn (talk)