|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: You write <G34> and <G35>
My understanding of the "strategy solely aimed at damaging" rule is to prevent saws, spikes, blow torches, etc. Not to prevent aggressive pushing. Likewise, the intentional flipping rule is designed to prevent "scoop bots" who can go out and up-end a robot with some kind of pneumatic flipper.
So, <G34> is OK as written and as enforced. The intentional entanglement rule is also there to keep teams from throwing a lasso around another robot and immobilizing them due to entanglement. So, <G35> is OK as written and as enforced. What many people seem to want is a couple of new rules to influence style of play. <G50> If two or more robots become entangled with each other, the referees will disable all entangled robots until the end of the match. <G51> Charging. If an offensive robot drives through a defensive robot on the way to a scoring object (while in the scoring zone as defined by a different color of carpet), a "charge" will be called on the offensive robot. 5 point penalty. <G52> Blocking. If a defensive robot drives into an offensive robot on its way to a scoring object, a "block" will be called on the defensive robot. 5 point penalty. <G53> Late hit. If a robot intentionally runs into a disabled or immobilized robot, a late hit will be called. 5 point penalty per offense. Repeated offenses may result in the robot being disabled at the discretion of the referee. BTW, for those offensive minded teams, if FIRST limits or eliminates "vigorous interaction," it becomes much easier to play defense. There was more contact initiated by robots trying to get to the scoring objects then by robots attempting to prevent them. If contact is limited, the defensive bot just has to get to the scoring zone and drop a flimsy wall around it. The offensive bot would have to "stand off" in order to avoid penalty, resulting in a very boring match indeed. Ramming...how do you decide whether a robot was driving across the field and encountered another robot in its path (due to limited vision, driver reactions, etc.) or a robot built up speed in order to hit another robot? If a ramming rule were put into place, teams may put themselves into harm's way, just to get another robot disqualified. In order to defend a position, a robot just has to get into the vicinity first. Any other robot would have to slow down and inch around the defending bot, in order to avoid a ramming call. |
|
#2
|
|||||
|
|||||
|
Re: You write <G34> and <G35>
defensive play is a part of the game. it is and always will be part of the game. it is only when that defensive play starts to damage other robots that it crosses the line. if a team is habitually tipping or damaging other robots, then action needs to be taken. I really like the idea of the yellow card/red card notion
|
|
#3
|
|||||
|
|||||
|
Re: You write <G34> and <G35>
This is a very interesting subject. If FIRST does go down this path (I hope it doesn't...see later in my post), then I suggest looking at professional sports like otheres here have mentioned.
Rules in these sports cover all aspects of what seems to be bothering people here. But you have to pick and choose rules from which sports for what. For example, picks (where your teammate blocks your opponent from following you) are allowed in basketball, but not in football. You could have the charging rule from hockey. Maybe impliment the 3 second rule from basketball where an offensive robot is only allowed in certain areas for 3 seconds. No holding...that's a pretty standard rule in all sports. Tripping? That's kind've like flipping in the robot world. Maybe FIRST can supply shock sensors (like those used in airbags on cars) and we place these on our robot and if another robot hits us and it causes the shock sensor to go off, a big light goes on or something and the attacking robot is assessed an "aggressive play" penalty. But, I thought FIRST didn't want to be like professional sports. What I would really like is for the FIRST community to work on this ourselves and not need all these rules stating every little thing. This is a rough game. When you are trying to score through another robot, you better expect they are going to fight back. And if you want to stop another team from scoring, expect the same. If your robot can't handle it, then you better figure out another way to score. That was the beauty of this game. The stationary goal being blocked all the time? Work on a strategy to get the mobile goal into play. Or go hang... I know most of this is starting from the agressive play from 469 and 494...both great teams which I admire greatly. Both had awesome robots, but really the only way I could see 469 get defeated was by playing very strong defence. So, that is what 494 had to do...and they did a great job. There was nothing wrong. They played 469 EXTREMELY hard and aggressive and guess what...469's robot didn't break. It was robust. Very robust. Our robot this year worked fairly well, but it broke very easily upon contact with others. And I know if we went to hang and another robot wanted to stop us, they could easily move us... So, we are using the experience and observations from the Championship to try and design and build something that won't have those issues next year. Some strong, easily repairable, and robust. Will it look as pretty as ours did this year...probably not. Will it have all the fancy gadgets and stuff to do whatever we need to do...probably...but they will be basic, robust things. So, I think these gaming rules shouldn't be changed at all because it will always come down to the refs judgement, which differs from ref to ref, Regional to Regional, and at the Championship. And that's not really fair to any of us. It's not their fault and they do a great job, but it comes down to peoples perceptions of things and that is very hard to qualify. I do like the idea of a video or something on the FIRST site explaining where each rule comes from so we all understand what they are trying to accomplish with each particular rule. Besides, there are other material rules that should be reworked instead. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|