Every Tuesday, Mike Sylvester brings you REVOLUTIONARY, a look at the wide world of Wii possibilities.
I was going to jump right into writing another script with you this week, but as development progressed, I remembered how much time I wasted on my first scripts because I didn't have a handle on exactly what motions were triggering the responses I was after. I figured I'd be doing you a disservice if I didn't take time out to get you primed on the nomenclature of all the motions and get you started in thinking in 3 dimensions.
Last week we wrote a simple script that didn't use the Wiimote's motion detecting functionality. Some might say that defeats the purpose of using the Wiimote, but is that really what the Wiimote is about? The different input options are there to give the developer choices. Sometimes the developer will throw in lots of alternatives and pass the choice on to the gamer. Taking every feature of the controller and slapping it onto a game isn't going to assure a fun time. More than likely, you'll wind up making something repellent that people will call "gimmicky." It's best to have an understanding of the control options available, and be selective in applying or omitting ones from your project.
