![]() |
YMTC: Redabot "Clangs" Tetras Together
You Make The Call (YMTC) is a series of situations where you are the official and make the call. Please reference specific rules when applicable. The results of YMTC are not official and are for educational purposes only.
Redabot receives a tetra from their human player. While maneuvering around robots to get to a goal, Redabot accidentally bumps a tetra on the autoloader with the tetra that it is carrying. When the two tetras "clang" together, Redabot is not in a loading zone and has not made contact with another robot. Based on the 2005 Game Rules, YOU MAKE THE CALL! |
Re: YMTC: Redabot "Clangs" Tetras Together
I do not think there is a penalty for that. If the team is on its way to a goal and is clearly not going for the auto loader then it should be a mistake, no penalty given, But it will all be up to the refs point of view on those kinds of calls.
|
Re: YMTC: Redabot "Clangs" Tetras Together
i think as long as it did not knock the tetra off, no pentalty.
|
Re: YMTC: Redabot "Clangs" Tetras Together
Quote:
I would not give out a penalty, as long as it look as if there intention was not to get another tetra from the auto-loader. however after the match i would be sure to go and explain to them to be more careful the next time. |
10 point penaty.
Quote:
Wetzel |
Re: 10 point penaty.
And this raises the philisophical question, "Did the bullet kill the person, or did the person kill the person?"
Technically the ROBOT did not touch the loading station Tetra (or as some may say, Tetram). Rather, a tetra that the robot just happened to be holding hit the loading station tetra. |
Re: 10 point penaty.
Quote:
|
Re: 10 point penaty.
Quote:
Is a tetra required for size check? Is the tetra you hold required to be "in profile" at the start of the match? Answer to all 3. No. Quote:
Therefore, as per those criteria, and the definition of a robot as defined in The Robot section of the manual, My vote is no. No penalty. UNLESS.. The team consistently tries to pick up a tetra on the automated loading station using another tetra that it is carrying as a pick up device, and thus is not in the loading area. Then, a sub rule would have to be written either not allowing that or "bending" the rules for teams who try to use that as a strategy. My guess though, is that the strategy would no be allowed. Incidental touching of another tetra on the automated loading station with one you are already holding should be OK, but maybe a warning about it given when it happens so it is made clear that it is not an allowable strategy unless you are in the loading zone. |
Re: YMTC: Redabot "Clangs" Tetras Together
Elgin I respect your efforts, but it is a penalty. Heres why:
When a human player loads a tetra onto a robot, if there is another tetra already on it, they cannot touch that tetra because it is an extension of the robot. ID:1789 Section:4.1 Status:Answered Date Answered:3/4/2005 Q:If the HP is placing a 2nd tetra onto the robot would they get penalized if part of their body touched the tetra that is already on the robot?A:Yes, the tetra is now considered an extension of the robot. If you had a defensive robot, and it hit an opposing robot in a loading zone with a tetra in its grasp, or on the floor, it is considered an extension of the robot. See example 5 in update 4. If a robot was to take a tetra on its arm, and push high on a robot with and it fell over...a dq would occur. All of this shows that a tetra in control or on a robot is considered part of it. THINK OF IT THIS WAY: (this is funny i think) Say I pick up a bat and start spinning in circles moving around while I do it. You are sitting quietly sipping water and I smack the drink out of your hand. Who do you blame the bat or me, the crazy guy with the bat? In this situation, the I am the robot and the bat is a tetra. The bat is an extension of me just like a tetra is an extension of the robot. It could be accidental it could not, but either way if I smack you with a bat (or knock a tetra off the loader) I get in trouble (or the robot gets a ten point flag).:) |
Re: YMTC: Redabot "Clangs" Tetras Together
I'm going to have to say penalty on this one. I don't have a specific rule to back it up, but here's a reason for my call: The rule that you have to leave the loading zone before getting another tetra only works if you entered the zone in the first place. I believe that actions should be called consistently, so if you allow a "tetra nock" to legally get a tetra from the loading station, you've allowed the teams to circumvent the rule.
--EDIT-- Sorry if this repeats something someone else has said. I started it this morning, but then I had to go to school... :) |
Re: YMTC: Redabot "Clangs" Tetras Together
Wait wait wait, IS the tetra comming off the autoloader or is it staying on?
If it stays on: no penalty if it comes off: penality |
Re: YMTC: Redabot "Clangs" Tetras Together
Quote:
Quote:
|
Re: YMTC: Redabot "Clangs" Tetras Together
I'm gonna have to go with penalty. Even if its unintentional, it still happened. Your control of the robot, and the robot itself, is responsible for the "bump" itself
|
Re: YMTC: Redabot "Clangs" Tetras Together
Even if the intent of the robot wasnt to dislodge the tetra from the loader, it is STILL a penalty.
Whether it stays on the loader, or falls off, its the same penalty because the rule specifically states TOUCHES a loading zone tetra. I'd say its just an unfortunate penalty that the team would have to endur. |
Re: YMTC: Redabot "Clangs" Tetras Together
If there is no reason to think the team is trying to hit that tetra, and it either falls out of play or stays normally on the autoloader, it should not be a penalty. If the tetra falls into play, it has to be called a penalty. It has consistantly been said that slight accidents will not be punished; a robot got bumped slightly (was not moved at all) while in the loading zone during elim rounds at peachtree, and there was no penalty. There's your precedent.
|
| All times are GMT -5. The time now is 03:11. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi