Holy crap dude, learn to read. "Not with any decent compression."

Goddamnit, my bad.

304kb image to 124kb? That seems pretty decent.
Give me a GIMPster ratio.

I'm talking about the quality of the image, not the filesize. I have a 5GB server, I'm not worried about filesize. I'm worried about how nice they look.

Is it that hard to just make sure the pictures don't look like crap before you upload them? If you don't want to take the time to upload a good, high quality screen cap, don't bother and let someone else do it.

Dont go flagging other peoples images because they're better quality than yours. I'll take your write ability away so fast you won't even know what hit you.

What are you talking about?
If you're going to use a template, you have to use the specifications you provided so it doesn't look squashed, just like you told me. The picture looks all blurry and messed up! Either make the template more dynamic (don't make it static, one size only), or whoever uploaded that image has to crop the picture so it looks good on the template.

The problem is that the image requires the picture be that large. In that instance, its preferable that Nfs captured the round detonating as opposed to cropping it out so that it met guidelines.

Besides, I'd rather a picture had to be compressed than stretched. You tell me what looks worse, a picture artificially zoomed in or out?

Both.
"That's not a choice!"
TOO BAD.
lol.
</jerkmode>
I'm wondering if there is a way to make templates more dynamic. Like if a picture is X amount of pixels wide, then the template (not the picture) will stretch to X amount UNTIL it reaches Y amount (a maximum width). It would also get smaller if needed. This would probably solve most problems in picture discrepancies. But I do not have a good background in WikiCode, so I have no idea how one could do this. Too bad it isn't CSS, because that is dynamic and I know how to use CSS. Oh well.

Also, how are you posting if you're banned? OMFG HAXOR.

Its just a usertitle is all. Like "Corporation Moderator."

Anyway, you can make a dynamic function to change the width of an infobox using an input (ie: | box-width = xpx)

The problem is, that defeats the purpose of an infobox (which is to enforce and encourage uniformity in articles). If you start having them dynamically resize, then you start having issues with uniformity. Just crop the images to 232 pixels in width at 100% zoom. Not that hard.

Additionally, shrinking the width of the infobox spans would not solve the problem. What if you had an image that was 10px wide? Could you imagine trying to fit data in a box only 10, maybe 12 pixels wide? it wouldn't work. There had to be a set standard, and it just happened to be 232.

Yes. Uniformity is good.
232px is not. You should have taken into consideration the LARGEST possible picture you could have. This means the weapon with the longest range, which means the Flak Cannon should have been your first objective, first picture uploaded and templated with. I can take a bigger screenshot of a pistol firing, but I can't take a smaller screenshot of a Flak Cannon's shot because of it's long range. Guess what? Everything clicks and it looks a LOT more uniform because there is no stretching or squashing.
I could understand if you had a size issue, but 4gb is more than enough to store everything we need picture-wise for just the basic game.

Like I said, there is no filesize issue. And the Flak Cannon, for the time being, is one exception out of, what, 10 items that have pictures so far?

If you want to take the time to go and reupload every screen capture at say, 250 pixels in width and 125 pixels in height, by all means, do so. Its a Wiki for a reason. The only problem I have is uploading images that are too small and are therefore stretched. Squashed is better than stretched when it comes to image rendering in FFX and IE.

Additionally, if you go around and change all of the screen caps sizes, make sure you do the same for the in-shop images. And lastly, please do a reupload of an image on the image page, dont upload a new image. Its easier that way.

Go to the Image: Page for the image you want to change and then look for the link "Reupload new image," or something similar.

You need to either make the JumpTime parameter on the Actors template optional, or put a separate template on for Craft. Dropship article didn't have "Jump Time" defined (because there isn't one), so it decided to say "Jump Time: {Jump Time}" before I defined it as "N/A". It would be better without even that there... Just skip out the row.

It says it's been deleted and can never be brought back when I try and look at it

Or ... since its a Wiki, you could do it?

I whipped this up in like a minute. Just wondering if anyone wants this logo for the Wiki?

The logo looks... bland.

what? an entire CC mini-wiki? there would be like 2 pages! are you all on happy herbs?