Thread:Kodokor12/@comment-5778183-20131201043237/@comment-5778183-20131201052359

I'm the kind of guy who likes to use polite, simple and straight-to-the-point talk. This is why you never see me making big edits on pages. Nothing technical, but of course a section should be set aside if you want to look at the technical side. That's the table.

What I'm saying is that tables should be used in conjunction with the Usage section. Don't shove all the stats in one place and then put a table next to it which displays part of what the Usage section says. Hell, I barely read the Usage section now that all the general descriptions of how the weapon works and tips are mixed with a large amount of raw data. I look at the table, mix it with my in-game experience and get a really good picture of the weapon.

And if you don't understand what the tables meant, then there the Weapon Statistics page (which should serve its purpose) which I bet no one actually looks at.

So first of all, some paragraphing would be nice to break up the huge wall of text. I understand the more experienced editors get what the page is conveying, but we're kind of teaching people, so we shouldn't make it such a big monologue like at school. Paragraphing helps immensely to prepare the brain to digest the whole thing.

Secondly, we should probably cut the said walls of text by linking it to the table, which is an extremely important part of the page, IMO. If the Usage section is too long, I just look at the tables. Just switch to short run-through of its features, strengths, weaknesses, limitations, advised play-style, dangers and the occasional tip. Only the really necessary stats should be included like reload, lock time, damage or ammo. The things you can really see in the game. Then you make sure everything the table can back up what the Usage section mentions.