Screenshot-Refinement-Theory: Difference between revisions
From MapSpawn
Jump to navigationJump to search
(Created page with "Talk about how I've mapped for years nearing the end of a map. I run through the map, take 100 screenshots if needed. Screenshot every single thing that catches me eye. Open hammer, tackle every screenshot issues as fast as possible. Move on and skip if you can't. It creates very high productivity, and it encourages playing your map and having fun before you map. I've learned to put the crosshair into the areas of interest because sometimes you forget why you took...") |
No edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 12: | Line 12: | ||
Plays into https://mapspawn.com/index.php/Lagrange-Point | Plays into https://mapspawn.com/index.php/Lagrange-Point | ||
[[category:Mapping_Exercises]] | |||
Latest revision as of 15:35, 6 February 2024
Talk about how I've mapped for years nearing the end of a map.
I run through the map, take 100 screenshots if needed. Screenshot every single thing that catches me eye.
Open hammer, tackle every screenshot issues as fast as possible. Move on and skip if you can't.
It creates very high productivity, and it encourages playing your map and having fun before you map.
I've learned to put the crosshair into the areas of interest because sometimes you forget why you took the shot.
Naturally produces a back catalogue of changes for your records.
