|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Balls In Opposing Robots
I've seen numerous fouls called today on teams who had an opponent's ball enter their robot. If a team has put the ball in your robot, or it accidentally enters your robot, why should you be penalized for trying to remove it?
I understand why it has been called this way, but it's painful to see this create huge point differences... Last edited by Navid Shafa : 08-03-2014 at 17:31. |
|
#2
|
||||
|
||||
|
Re: Balls In Opposing Robots
I agree. It is extremely saddening to me that this caused 1114 to lose. They had the best robot there and in my opinion should've won. These penalties are deciding elimination matches when the penalties received are judgement calls. Meaning it is debatable as to whether or not the penalties should've been received. In the Finals at the Arkansas regional the Blue Alliance won the first match and the next two the Red Alliance won but solely because of foul points that were questionable.
|
|
#3
|
|||
|
|||
|
Re: Balls In Opposing Robots
Quote:
|
|
#4
|
|
Re: Balls In Opposing Robots
Sorry, but the problem was entirely avoidable by the drivers having the robot back up when they saw the ball bouncing toward them. I watched this match as it happened. The GDC made no mistake in the rules by saying you should design your robot to make sure you don't accidentally possess another team's ball. That's how it happened. There should be no changes made in the rules.
|
|
#5
|
||||
|
||||
|
Re: Balls In Opposing Robots
We got 50 foul points twice on our alliance for 100 tech foul points. Luckily we still won! It was for the same reason. They threw it in our intake. I can't see why it's a game changer?
|
|
#6
|
|||
|
|||
|
Re: Balls In Opposing Robots
I find that the rule covers all of the situations of possession but I don't like the rule.
Quote:
|
|
#7
|
|
Re: Balls In Opposing Robots
Since when should engineering not have a hard, defined, approach to a problem that could very easily occur.
|
|
#8
|
|||
|
|||
|
Re: Balls In Opposing Robots
Quote:
As for the GTRE match, was the second tech foul pinning? That was enough to seal the game for the blue alliance (who won due to strong defense in the first match). The illegal catch just meant that the game was hard to win from an earlier point in the match. While I was cheering on the red alliance (3683 is long due for a championship appearance!), the red alliance got upset by a strong 5th seed. |
|
#9
|
|
Re: Balls In Opposing Robots
The second tech foul was indeed pinning.
|
|
#10
|
|||
|
|||
|
Re: Balls In Opposing Robots
Quote:
I completely agree with the decision on this matter. I saw this happen plenty of times both at week 1 events and this week, even in cases where the ball was not directly in the robot. It was clear possession, regardless of intent. It is unfortunate that it has happened to teams, all of which I'm sure were accidental, but it was clearly stated very early that you must design around this to make it impossible for that to happen. It's no different than a robot designed to effectively shoot the ball. Both aspects are incredibly important parts of the game. |
|
#11
|
|||
|
|||
|
Re: Balls In Opposing Robots
Quote:
|
|
#12
|
|||||
|
|||||
|
Re: Balls In Opposing Robots
If they threw it into your robot, apparently intentionally, ask the head ref why G14 was NOT called. Just sayin', a G14 called for a human loading the wrong alliance's robot will swing the final score by 100 points (takes off your T-foul and gives the opponents a T-foul).
|
|
#13
|
|||
|
|||
|
Re: Balls In Opposing Robots
Quote:
|
|
#14
|
|||||
|
|||||
|
Re: Balls In Opposing Robots
I agree, it's a harsh rule. BUT think about it this way: anytime the other alliance's ball is in your robot, that alliance cannot be scoring said ball. So it's harsh, but it's necessary to ensure that both alliances have as fair and equal scoring opportunities.
|
|
#15
|
|||||
|
|||||
|
Re: Balls In Opposing Robots
Quote:
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|