We had ours on our own robot, 2458, and 2191’s bot
it was pretty cool to see it on other robots
2158 was the only team that legitimately shared a minibot (twice) during qualification matches at Alamo, but unfortunately the team they shared the minibot with did not successfully deploy the minibot either match.
-Danny
We were on the Olympic side of the 100 team Seattle Cascade/Olympic dual regional playing on the Olympic field and we loaned 1 of our minibots to MRT 3216 who successfully deployed it on Cascade at least twice. We specifically sought out a team from Cascade that had a good deployment system that was compatible, just to test this.
It threw the field people a loop since their system wouldn’t accept our team number. Which was the reason given why we were not eligible for the coopertition award at Cascade. Though I’m not sure why they couldn’t do a write-in tally since there were exactly 0 other shared minibots successfully deployed and there was no coopertition award given at Cascade.
We also loaned a minibot to 2147 on Olympic who successfully deployed it 3 times in qualifing and at least once in eliminations.
At Peachtree 122 shared their minibot with us (3573). We only got it on the pole once due to numerous issues with our deployer (wouldn’t have mattered what the mini was like).
Despite our best efforts to inform anyone who would listen that we were using 122’s mini before each match, they were not awarded the Coopertition award for the one qual match we did score it 
From what I heard, there were one or two shares at St. Louis, but none were successful and there was no mention of the Coopertition Award.
At Seattle Cascade the que’er did specifically ask 3216 if the minibot was theirs or loaned and if loaned the team that provided it, per the queuing form, as reported by the 3216 drive team.
At Seattle Olympic…
After selecting 1868 for our alliance, we immediately began working with them on getting their second minibot working with our deployment system. 45 minutes later we had it ready to go for our first quarterfinal match. Every time we attempted to deploy, it went up, I believe 4 out of the 6 elimination matches we played. Awesome minibot, awesome team, things worked out well.
At Seattle Cascade, you weren’t competing. You can only earn Coopertition points if you’re registered for an event as an FRC team per <T03>.
Any borrowed MINIBOT which scores points by legally triggering the TARGET during the MATCH receives one (1) Coopertition point for the FRC TEAM registered for the event that is affiliated with the MINIBOT.
For Seattle Olympic, though, I’m not sure what happened there.
It looks like very few Coopertition Awards are being given out; I’m not sure why. Even in cases where somebody’s eligible… I wonder if there are a lot of ties for the award, throwing off the count, or if people are just forgetting that it exists.
Mini bots were shared at the Chesapeake Regional.
The only minibots shared at Duluth that I know of were us installing a deployment mechanism on our alliance partner over lunch. In fact, using our minibot they consistently beat us up the pole by a few tenths, which is leading to a partial redesign of code. 
We were the team you loaned your bot to (thank you very much)… and thanks for picking 2530 as your first alliance pick. I did ask queuing after our last Qual match if any sharing had occurred yet and they said none had, so unless the last few qual matches had any sharing (I doubt it) I think you can win the coopertition award for sharing in the elims, since 2169 did win it.
By the way, after the 2169 minibot smoked on the pole due to a faulty deployment, we went back to our original minibot. I believe even with our slower minibot we still beat 2169 up the pole due to our fast deployment.
John Vriezen
Team 2530 “Inconceivable”
Mentor, Drive Coach, Inspector
FIRST team 118 brought with them 6 complete deployment systems and minibots to the Lone Stare regional. They had them mounted on 3 other robots by the end of the day on Saturday, including their alliance partner FIRST team 1801.
Yes, we were asked this at Peachtree as well and every match dutifully informed them that we had 122’s mini. After the match it went up we checked to make sure it was recorded and I was told 122 did as well.
Since this was such a success it is definitely something we are going to repeat at SVR and St Louis. You guys happened to have simple, effective parts that got the job done, and we plan on bringing a bunch of long 3/8 bolts and lock nuts to competition in the hope that we’ll be able to do something similar even during qualification rounds.
It was pretty funny after we spent all day trying desperately to get our deployment done, we gave you the minibot and it was done before lunch was over.
At the West Michigan District, 1918 NCGEARS loaned us their minibot after ours burned up. We played 4 matches with it on saturday, we only had a chance to send up once, 3 times it popped off our pins holding it in place (same deployment method) 2 times from getting hit hard by another robot the other was from hitting the playerstation to hard 
which lost us the match and put us too low to get in a picking position.
We were actually registered for Seattle Cascade, but after the fact First decided to treat it as one regional and place teams on fields based on team number. So they initially considered them as 2 different events, changed to considering them 1 event, and then back to 2 different events once they moved the teams around. On the one level I can understand the reasoning behind why they choose to shuffle the teams between the fields with almost 30 rookie teams and 20 something 2nd year teams they wanted them to have a similar mix of veteran and rookie teams.
I do know what happened at Seattle Olympic but at this point I can’t give anymore details.
In our discussions of the Coopertition award at our regional they told us that the qualification matches were the only way to earn the Coopertition award and elims did not count.
I will dispute this, as team 3221 won the coopertition award on the cascade field. our team deployed team 2471’s (FIRST Team Mean Machine) minibot twice in qualifications, and had a failed deployment in the finals.
Why we got the award and not 2471, I don’t know, but considering that they won the regional they were happy either way.
I will also dispute this, as this is never stated in the determination of Coopertition points. 5.3.5:
Any borrowed MINIBOT which scores points by legally triggering the TARGET during the MATCH receives one (1) Coopertition point for the FRC TEAM registered for the event that is affiliated with the MINIBOT.
The total number of Coopertition points earned by a TEAM throughout the qualification matches will be their Coopertition score.
“Any borrowed minibot which scores points…during the match”. Not “any borrowed minibot which scores points…during the qualification match”.
If that’s a rule, then it needs to be stated in the rulebook. Because it isn’t stated, then it isn’t a rule and isn’t enforceable as a rule.
In Florida, we lent 79 our back up minibot. They never got it up, but it was fun waiting to see if they could get it to work!
In Baltimore this weekend 340 shared their minibot and the other team got it to go up, so they got the co-opertition award. It was great.