|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: Game Manual - Team UPDATE - 2014-03-18
Quote:
G25 ROBOTS on the same ALLIANCE may not blockade the FIELD in an attempt to stop the flow of the MATCH. This rule has no effect on individual ROBOT-ROBOT interaction. Violation: TECHNICAL FOUL I like this update. I think it keeps serious offenses as a Technical Foul (50 points) but moves minor infractions to a Foul (20 points). |
|
#2
|
||||
|
||||
|
Re: Game Manual - Team UPDATE - 2014-03-18
Quote:
However I view any possession that significantly slows a cycle as consequential, regardless of the score. I would argue that going forward, it may be in the best interest for the robot causing the infraction to actually step away from the play to ensure that the ref sees that the unintentional possession of the ball did not give them a competitive advantage. You are definitely still at the mercy of the ref. Here's a link to the video at the time of the infraction. http://www.youtube.com/watch?feature...vxVzpyfks#t=95 |
|
#3
|
||||
|
||||
|
Re: Game Manual - Team UPDATE - 2014-03-18
Quote:
Sometimes a team gets called for any little bump of the opponents' ball. That is not the way it's supposed to be called, in my opinion, because one tap is not possession. The change to a regular foul for unintentionally or inconsequential POSSESSION is a good change. However, I suspect that referees will have a hard time distinguishing between POSSESSION and CONTACT when making this call, and a lot 20 point fouls will be called when a robot touches the other team's ball for any reason and with any result. Last edited by Nemo : 19-03-2014 at 09:45. Reason: Less whining |
|
#4
|
||||
|
||||
|
Re: Game Manual - Team UPDATE - 2014-03-18
Quote:
There will be no appreciable change in game flow since the base rule is still the same (don't POSSESS the opponent's ball). If the refs start handing out FOULs like candy, I for one will be happy, because under the old rules, every single one of those would have been a TECHNICAL FOUL. |
|
#5
|
||||
|
||||
|
Re: Game Manual - Team UPDATE - 2014-03-18
Quote:
Q466: Does TU 3/18 lower the threshold for G12 (a no-call in Week 1 could be a call now, for the identical situation), or raise the threshold for receiving a G12 tech foul (a tech foul in Week 1 could be a foul now)? https://frc-qa.usfirst.org/Questions.php |
|
#6
|
|||
|
|||
|
Re: Game Manual - Team UPDATE - 2014-03-18
To paraphrase and try to put it in context:
They have merely reset the severity of the G12 penalties.. If your act is an inconsequential or unintended action, but, still manages to keep the opposing alliance away from their ball (not a bad thing in this game), but, if your action is deemed to appear or be intentional or worse absolutely deliberate and strategically planned by nature of appearance...They can raise the severity back to where it was, and even higher. I say don't look a gift horse in the mouth. Some of those fouls now won't necessarily flat cost you the match...But some still will. Try to be nice. Play your game, don't attempt to run or ruin theirs. This is a 1 game piece per Alliance, work well together, inbound get 3 assists / truss/ catch/ score fast cycle game. (And it is really exciting to see it played to full complete high scoring fast cycles by both Alliances at the same time (especially w/ occasional zone defense, when not on the ball right then, added). Not so much, when it instead reverts to just a battle bots type show). |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|