- Nov 22, 2012
- 324
- 262
Mapping is a somewhat calculated skill that fuels on what may seem to be the opposite - that being creativity.
When people submit maps for examining and testing, I'm sure a lot of us can easily point out major problems with almost every map. This is all part of map design f course, but I would really like to see it ultimately become more efficient.
This is where the whole lame term of feedforward comes in. I have never really liked the term, but you have to use what you have got I guess.
Feedback is usually pointing out things that are problems or things to be desired, feeding those things back to the creator of the map.
Feedforward on the other hand gives feedback but elaborates on it by supplying ideas or suggestions to help fix the issues, hence the 'forward' part.
I have seen a few people give feedforward on the forums but still I would say over half give good old feedback. While that certainly helps it could be even more helpful with some suggestions on how to fix. Of course you have to be rational - you don't need to give a 3 page essay on how to avoid random clipping on the top of a door frame but things like sightlines, over powered sentry nests and the like can be fixed.
Say I had a map with a massive sightlines. I could get this;
or I could get this;
I find that if you are going to give feedforward, it really helps to use 2 ideas. Instead of saying "get rid of it by using big wall brush" you can start a discussion which can actually solve the problem in a better and more fun-to-play manner.
So there we go - if everyone gives feedforward we would have a forum overflowing with hundreds of fixes to various map issues that could even be implemented into other maps and a place full of create ways to handle that annoying 'thing' that every new (and completed) map has.
When people submit maps for examining and testing, I'm sure a lot of us can easily point out major problems with almost every map. This is all part of map design f course, but I would really like to see it ultimately become more efficient.
This is where the whole lame term of feedforward comes in. I have never really liked the term, but you have to use what you have got I guess.
Feedback is usually pointing out things that are problems or things to be desired, feeding those things back to the creator of the map.
Feedforward on the other hand gives feedback but elaborates on it by supplying ideas or suggestions to help fix the issues, hence the 'forward' part.
I have seen a few people give feedforward on the forums but still I would say over half give good old feedback. While that certainly helps it could be even more helpful with some suggestions on how to fix. Of course you have to be rational - you don't need to give a 3 page essay on how to avoid random clipping on the top of a door frame but things like sightlines, over powered sentry nests and the like can be fixed.
Say I had a map with a massive sightlines. I could get this;
mass sightlines pls fix
or I could get this;
The sightlines are a problem here. Maybe you could try to move this platform here up a bit or even just completely put a doorway here?
I find that if you are going to give feedforward, it really helps to use 2 ideas. Instead of saying "get rid of it by using big wall brush" you can start a discussion which can actually solve the problem in a better and more fun-to-play manner.
So there we go - if everyone gives feedforward we would have a forum overflowing with hundreds of fixes to various map issues that could even be implemented into other maps and a place full of create ways to handle that annoying 'thing' that every new (and completed) map has.