|
Re: FVC GDC wants your feedback
One person above suggested putting a choke point on a part of the field all contestants share - Good idea, but it should probably be a one-way path (mandate a different path return path) with a gate system or some other implicit mechanism that queues up the bots without having them collide with one another. Vex bots aren't very sturdy.
If all teams can bring two robots or if you can figure out a way to have equal numbers of team produce each of two types of robot; I would love to see a game that is played by alliances of two bots, and that demands two distinctly different types of behavior from those bots.
Perhaps one behavior would be pushing big objects out of the way and gathering objects that were hidden behind the big ones. The other behavior could be accepting the gathered objects and racing through obstacles to deposit them in a goal high off the floor.
The rules would be designed to make it very, very hard to build one bot to do all these things (much less do them well) and stay within other game constraints like size and weight. The importance of teamwork and strategic thinking would rise.
Blake
__________________
Blake Ross, For emailing me, in the verizon.net domain, I am blake
VRC Team Mentor, FTC volunteer, 5th Gear Developer, Husband, Father, Triangle Fraternity Alumnus (ky 76), U Ky BSEE, Tau Beta Pi, Eta Kappa Nu, Kentucky Colonel
Words/phrases  I avoid: basis, mitigate, leveraging, transitioning, impact (instead of affect/effect), facilitate, programmatic, problematic, issue (instead of problem), latency (instead of delay), dependency (instead of prerequisite), connectivity, usage & utilize (instead of use), downed, functionality, functional, power on, descore, alumni (instead of alumnus/alumna), the enterprise, methodology, nomenclature, form factor (instead of size or shape), competency, modality, provided(with), provision(ing), irregardless/irrespective, signage, colorized, pulsating, ideate
|