![]() |
Re: Team Update 6
Quote:
|
Re: Team Update 6
Quote:
|
Re: Team Update 6
I'm so glad to know that I can just come on here and trust anything I read about the game so long as no one has come along to correct it yet.
|
Re: Team Update 6
I'll admit: in my numerous re-readings of the 2017 manual, I missed the caption below a figure that explicitly states the rotors must be engaged in order, as did a few others in this thread.
And we're the 'good ones'. Aside from the occasional "do we have a weight requirement this year??" silliness, I'll refrain from ordering people to ::rtm::. |
Re: Team Update 6
Quote:
Quote:
By not citing the actual rule, or in this case a caption in the rule book, it forces someone to do research into it. I don't need to tell someone to read the manual, I can give them a reason to by giving them information that they need to verify. Don't just hand your students the answer make them work for it and they'll remember it more. At least that's what all my teachers, that I would consider good, did for me. |
Re: Team Update 6
So basically, you're saying that instead of just telling people where to find the relevant piece of information when you post it, you'd rather make them go back and read through a 130 page manual in the hopes that they'll spot that one line of text underneath a picture this time?
I make my students read the rule book. When they ask me questions I don't just give them the answer... but I do tell them roughly where to find the answer and help them interpret it. I don't just leave them to struggle through 130 pages without knowing if what they're looking for is even mentioned in there or a figment of someone's imagination. |
Re: Team Update 6
Quote:
Also, FIRST conveniently splits the 2017 Game and Season Manual into sections, as advertised on their website. You could safely bet that this rule in question would be in either Section 3: Arena, Section 4: Match Play, or Section 7: Game Rules. |
Re: Team Update 6
Quote:
|
Re: Team Update 6
Quote:
-George |
Re: Team Update 6
Rotor = 57 mentions
Order = 34 mentions That's if you search the entire manual. Of course, something like this you'd think would be mentioned in the game rules, or maybe in match play, so you just open those one's up and search, don't find anything (Since it's talked about in the Arena), and assume what? That Eric is wrong? The point is, simply making a statement on here and forcing everyone else to go verify its reliability is making everyone look for a needle in a haystack, and it could be very easy for people to arrive at different conclusions based on the assumptions they make. If we really want to ensure reliable, easily verifiable discussion about the rules, references should actually be made to where we get our information. Trust me, in industry you don't just make statements about what's required for a product. You actually reference the requirement you're discussing, and when applicable even quote parts of it to ensure everyone is on the same page and agrees with whats been said. To do otherwise invites product errors. |
Re: Team Update 6
Quote:
|
Re: Team Update 6
Quote:
|
Re: Team Update 6
Quote:
|
Re: Team Update 6
Quote:
Spin gear 2.75 turns, then wait 9 seconds, then turn 0.25 turns and the rotor will start. Spin gear 2.75 turns, then wait 10 seconds, then turn 0.25 turns and the rotor will not start. The rotor still needs an additional 2.75 turns now. You must get all 3 gear turns within about 10 seconds. |
Re: Team Update 6
Quote:
The question is if I can place the gears for Rotor 2, THEN place the gear for Rotor 1, then start turning Rotor 2. Or better, crank on Rotor 2 while Rotor 1 gear is being placed. The only time I see this mattering is in a 3 gear auton attempt, but it could matter a lot for making that happen. I'm assuming slamming a gear in a slot is faster than placing it on a peg, so you ideally want to overlap building Rotor 2 gear set and placing gear in Rotor 1. |
| All times are GMT -5. The time now is 12:02. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi