after reading the manual, the only restrictions on teams is drive team and it was something saying people can’t be on multi-drive teams. but I would like to check if this set-up would work.
7701x
drive
program
build
7701x2
drive
program
build
According to the rule… looks legit to me.
Basically you can even set up a factory and build multiple robots for others, as long as you are not driving all of them (except one).
Yep, looks good. Just you can’t be on 7701x drive team
@meng Bots r us. I am sure there a few parents currently under indictment who might have paid big money for the scholarship opportunities.
@gcfky Haha… maybe we can even have an online site that allow them to choose which subsystems do they prefer… lol…
You want a 4-motor Drive or 6-motor drive?
Now select your ball manipulator - flywheel or puncher? Lol…
Ok ok… think I better stop here… I am giving all the bad business ideas over here 
The forum does have enough bad ideas without fostering more.
As stated above, a given student can be on as many teams as they wish, so long as said student is not on more than one drive team.
[Just reinforcing what was said, no contradictions here.]
This happened at states to me and my sister team, where I was the builder for her team and driver on mine, (only her team was competing at that event). For some reason the refs said I couldn’t even be on her team, if I touched the robot she would’ve gotten DQ’ed … et cetra. It technically abides by the rules but if i were you I would play it safe.
The intent is more roboteers, not more robots, and have them work with their teams, not to part themselves out. In a discussion with @Paul_Copioli1 the “drive for one team rule” came about because of groups of robots sharing the best driver. What @cykaraptor is presently legal, but it’s the kind of thing that will get additional rules added down the road.
^Adding those additional rules would certainly be a pain for competitors and mentors. We all understand what the intent would be, but that would also disallow a lot of inter-team cooperation and normal interaction.
(I won’t bother elaborating, because we can all see where my train of thought is going. But I will if there is any confusion.)
I disagree with this assertion. Normal cooperation and interaction is encouraged. However, organizing a club to produce more identical robots by having builders/coders doing it for multiple teams is not in the spirit of creating more roboteers @Foster’s point.
We had to deal with such a situation in the region, and it was not pleasant. Yes I know clubs want more metal trophies and banners… I get that, but by having one guy do all the coding prevents other club members from learning it too. Ditto for building, designing etc… Let them learn, and that means not being good at the beginning, getting constructive feedback from others, and not by having the work done for them by others. Otherwise, next thing you know they will be in some college admissions scandal plastered in the news. We don’t want that, do we?
As for having club members support a team at Worlds, I get that - we’ve done that. Those kids know that they are there to support the team operationally.