Chief Delphi - cheif delphi is for cheaters

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)

- General Forum (http://www.chiefdelphi.com/forums/forumdisplay.php?f=16)

- - cheif delphi is for cheaters (http://www.chiefdelphi.com/forums/showthread.php?t=17824)

Quote:

Originally posted by Firewolf
you know what? We ARE all trying to get around the rules
if we didn't there would be nothing new in the world, but the
same people in line afraid to bend.

and it is true, they keep making so many up dates and changes,
I hear about them over and over again and I'm left so confused
b/c I don't know what is true and what is not, and what has
changed, and when and why, and such.
I'd wish there was a clear cut outline set out
where you can use your imagination to create whatever
you wanted w/o having to worry if you're light is 'exposed' or 'visable'

(sorry for the rant)

Good point. Unfortunately we probabaly won't find anything out until AFTER the ship date when they put out the "official" manual.

Perhaps we should finally have an "official" build period?

ok the person tha posted that on FIRST's forums was wasting there time and complaining they will do what they say and if they don't then you can get mad but stop complaining!

unfortunately last year at Richmond regionals, there were lots of problems with bots tearing up the carpet because of studs, spikes, etc. Some got DQ'd from a match, but FIRST should have been stricter, especially when they were in blatant violation of the rules.

I think that to prevent this from happening again, FIRST has gotten super-strict, even on insignifigant things like light visibility. Also, their rule-book is definitely vague and lacking, especially if they have had to release 12 (i think) updates in less than six weeks.

The posting reply doesn't spell out this site - the original question does, but I believe it is reference to the pic's of some of the bots that has been uploaded. Let's not get into a big to do over nothing. Besides, update 12 is pretty clear about the beacon requirement - time is getting short, lets all just relax and not get torqued up over this issue. Although, being refered to as a "wildcat" site is a bit funny - check out the # of posts and threads here, compared to theirs! As stated before, this site is set up for the FIRST community to discuss and debate "just about anything" - sometimes there are discussions related to the Rules - in our opinion, that is a GOOD thing. Keep posting, Keep discussing, Keep uploading pics, Keep sharing ideas. We love it and appreciate your participation.

Quote:

Originally posted by f22flyboy
especially if they have had to release 12 (i think) updates in less than six weeks.

Actually in the beginning they said that they were planning on releasing two a week even if there wass nothing to say in them.

I think the reason there are so many updates is because people whined about there not being enough last year. However, now that they are giving us a lot, other people are whining about there being too many. So all the updates is a result of last year probably.

Quote:

Originally posted by Ken L
There should be an official process for teams to submit a formal complain or some sort for these kind of situation. I mean, even though we are replying heavily on Gracious Professionalism, there are times when people take the easy way out, and not follow rules are strictly as they should.

FIRST should setup something at the competition where teams can go there, and talk to a person about something odd they saw on another team's robot. And teams have to understand that it is not a personal attack, and that people are just trying to make sure the playing field is fair and no one is having advantages by not following the rules. Then an inspector should be sent to the team, and check out the robot and decide whether or not that team is really violating the rules or not.

I know this could get out of hand, and teams might take advantage of this to cause trouble to other teams, but on the other hand, I've seen so many case where someone else notice something wrong with another teams robot, and have no one to talk to.

*cough* entanglement clause *cough*