Measurements. A years worth?

[Blacksheepboy]

If anyone were to spend several years putting together a map, what would they do during that course of the year to make a perfect version of their map? That was a question I thought up 30 seconds ago while looking at Zakath's dm_paradise and reading Vig's comment, and after watching a 12 minute video that took a year to design.

I believe it would start with something like doing a number of distance tests. Example: how far does a Soldat go by running, then jumping off of a flat surface? Where is he, in regards to the flat cliff, 2 seconds after jumping, or 6 seconds? or whatever practical measurement of time you would need to consider. Then you add more variables (jumping from standing still; not jumping etc), so on and so forth.

You would consider various ways to make bullets ricochet.

Obviously you would want to design the map for maximum playability, so no amazing backgrounds blending into the polygons to make your map look like a piece of art.

This would be an inherent waste of time to spend this much time on a Soldat map. But some people have striven for amazing qualities in maps. Do you, as a mapper, consider anything specific that's possibly out of the ordinary? aside from 'what texture/scenery/gamemode do i use'.

[zakath]

My main thought when designing a map is base design(if its a ctf/inf map) or otherwise the flow of the map as well as trying to balance it weapon wise trying to get some weapons more benificial in different parts of the map. Also trying to spend my out most to prevent lame tactics like spawnkilling spraying, camping and such.

[As de Espada]

firtst thought: when players spawns, where do they go?
second: if someone catch the flag, where do he/she goes?
third: how can spawning player intercept the flagger?

[Blacksheepboy]

But these are generally the typical thoughts you have when making a map, although I don't typical think about how certain weapons will work throughout the map, except for the sniper... Picture yourself spending a year on a map, and then the small, precise details become big.

[smiluu]

Must've been hard to spend that year in Semenperiod
I take too much basic stuff into consideration while mapping
that I'd be like repeating basic grammars.

[Blue-ninja]

A huge climb map project would make more sense. Or something pertaining to KamikazeDuck's puzzle maps (ctf_Explore)

[smiluu]

Climb maps aren't that special either. If it's 5jumps- style, each jump should be tested at very least.
Puzzles and race maps should be tested with intention of shotcutting (climbs too ofc). Also, careful
look at the possible mixed polygon types.

[Blacksheepboy]

Semenperiod

You know, it kinda looks like that...

[p0ppin]

when I read the first post, ctf_Ash came to mind simply because of all the trick law shots

[Blacksheepboy]

To clear any potential misconceptions..? I've never spent a straight year on a map. I think my longest is ~12 hours of designin. and that was on a map that turned out to be crap... inf_berserker er however I spelled it.

[Mr. America]

Ha, I've got some of those maps that take their time... well, I'm just bored to finally finish them, they're more like a "improve-if-nothing-to-do" ^^

However I usually consider mobility, so to say I want it to be possible to run trough a map with godspeed =P. Oh, and I consider sniping range/ possibilities, but that might be basic stuff...

[Blacksheepboy]

they're more like a "improve-if-nothing-to-do" ^^

Yup, same here. I've got a couple of these.