Exploits/Engine tricks are often controversial, but I havent seen this particular argument made that often so I thought I'd mention it.
If the game shipped without this exploit/bug/trick, and someone posted a suggestion, "Hey guys, what if we patched this engine trick in? You could do X and Y and it will be skillful and awesome!" Would you agree with the poster? Or not?
Or alternatively, "I'm designing the sequel - do I implement this bug in the sequel?"
Flipping the situation around sometimes helps because people are often biased towards the status quo.
- Sometimes exploits/engine tricks are good for gameplay. Sometimes not.
- Just because something is a bug/exploit doesnt mean you automatically have to get rid of it. But sometimes you do.
- If you think about it from the perspective of "What if the game shipped without this exploit, would we want to patch it in?", usually what you'll decide is a "nicer" properly designed version of the exploit.
egs.
* "Yes, I'd patch it in"
- Comboing in Street Fighter 2.
- Bunny jumping in Quake.
* "No, I wouldn't patch it in"
- Guile "magic throw" in SF2.
- Being able to prevent your opponent from selecting his unit in Starcraft by flying your terran structure over it.
For people that play fighting games, its interesting to read about SF2's glitches and see the various bugs that became formal mechanics in later FGs:
http://combovid.com/?p=1450
Jump cancel, chain combos, red hadouken
Anyways, something to think about next time bomber multi-dropping or whatever is discussed