![]() |
SPChief and WV
Hey guys!
You two fellas are on the brink of elimination. I have picked a number between 1 and 1000. You guys pick a number. Closest number wins. Doesn't matter if you go over or under. Closest number wins. |
How do I vote?
|
WTF?
A player on our team is eliminated based on a number you pick? |
278.....and I agree with detoxing.
|
Yea. We did this last game. You guys really should of read up on what you were getting yourselves into.
|
Quote:
|
I changed my mind spchief.
|
Quote:
So...why is an elimination of one our teammates coming down to a random number? The rules are being made up on the fly... |
voting spchief off.
|
JMO.....but it should go by vote and if there is a tie....it should go by score on the last contest.
|
And this probably wouldn't even happen if we knew who the immunity was. How many votes were wasted on someone who was unknowingly immune, and would those votes have kept this thing from even being a tie?
I'm not trying to bitch, and I know i'm coming across like that, but these are simple things to iron out. |
Quote:
Hell, why do we even do the contests? This is ridiculous. All this could be avoided with a simple voting deadline. |
I'm gonna be pissed if this dumbass random number thing costs us a good member when the votes were to vote SPchief off.
|
They are ironed people just don't pay attention.
I said on the elimination thread, that is was a tie again. In fact, detoxing, it was you're vote that tied it up. So after two ties, the way we handled out in the last game is I decided who goes, and o based out pod who I thought would make the more interesting. I couldn't decide, so I decided this is how id pick my you're breaking vote. Don't like it? bye. |
Quote:
|
ROFL
|
Quote:
What does this even ****ing mean? Ummm, the contests are for immunity. That worked. The votes decided on SPChief and WV. However, two times they tied. They tied. They tied. Do I need to post that again? So my vote kicks one of them off. You guys are bitching for no ****ing reason. Things are running just how they're supposed to. Take a ****ing chill pill because this is really pissing me off. |
Quote:
|
Hey, we're not done changing our votes yet.
Give us more time! |
I don't see how this could be clearer.
Last time we had a tie, I picked who left and stayed. NOONE SAID A WORD. |
Quote:
Of those four people, when we revoted, three of them voted WV. However, somebody changed their vote in the revote, and we now came to a tie again. This is the final tie breaker. Get it guys? |
Quote:
|
Quote:
Actually, what kind of watch are you using? Does it have a timer? I'm using my cell phone and a Ninja Turtles watch i won in the quarter vending machine in front of KMART when i was 6. If you're wondering, i have the watch synced up to my phone, so no worries there. Let me know immediately, this is important. |
Quote:
You seem to be getting frustrated. You just need to have a plan in place for events of a tie, and let the people know what it's going to be before randomly deciding what to do about it. People like structure. People like to know that they're all playing by the same rules and being treated fairly. Pest's suggestion makes sense. If it's a tie, then go by they're last performance. The weak link goes. If the team is divided, then let the individual's performance decide (which, I guess, would ultimately be the judges deciding). Again, in case loochy complains that I'm trying to influence the votes and the game, I just want to say that this is only my suggestion. |
Quote:
|
Quote:
Quote:
|
Quote:
I agree with this. |
Quote:
|
Quote:
|
Quote:
|
the consensus of the n00bs is to vote off spchief.
|
Can we move on now?
|
I'm contacting the other judges to see if they are up for the work they're gonna have to put into the next possible challenge.
Be patient or I'll start kicking people off randomly. |
Quote:
|
If the next contest is for whichever team has the most sand in their 'giners, the Vets are hosed.
|
Quote:
|
Quote:
|
All times are GMT -6. The time now is 12:07 AM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.