Hey, when did Tim Buckley get into modding?

Look, if simplicity is your concern, then work on the mod with large maps, but when polishing the product for release, OS would be nice to use when compressing it so it's not destroying whatever hosting you use. I mean, if it's a release, there's no changes to be made other than bugfixes, so complexity won't be a concern, right?

From what I've gathered in the thread, it seems people are mixing up the source with the public product. Masterz is concerned that making the maps smaller now would be too complicated to work with, which is perfectly fine. What everyone else is worried about is having these massive-ass files that don't need to be as big as they are. They're not done yet though. When working on a project, simplicity always wins. However, when the product is finished, convenience for the user is ALWAYS the winner against simplicity of the code/tags/whateveritisI'mnotinthisfield, because when a product is released, it is assumed that the inner workings will not need to be deeply tampered with, and thus, the complexity does not matter.

TL;DR: Let them be big as shit now, but when it's done, use OS to make it smaller.