Decision Maker

[sinewav]

• Neither player will see the rename until the new round begins and they receive the server message. The sum of the numbers, even or odd, determines the winner.

Hmm, pretty sure this is deterministic. The player who joined the server first would get to keep his chosen nick name.

What? Am I not explaining it correctly or is there something I don't understand about the process if renaming?

[kyle]

they rename by appending a number to the end of their name (not letting the server rename them)

[Z-Man]

Epsy: they're not renaming to the same name and see who wins. They each rename to something else, and just use the server's delayed announcement of name changes to keep their choice secret.

Mind you, there are several spots in the between-round-time where renames are possible, so you need to make the first rename message count, not the final result. Someone with a quick eye and quicker fingers can alter the final result based on what the other one picked, I think.

Also, new game: Tron Rock Paper Scissors!

[Lucifer]

Epsy: they're not renaming to the same name and see who wins. They each rename to something else, and just use the server's delayed announcement of name changes to keep their choice secret.

Mind you, there are several spots in the between-round-time where renames are possible, so you need to make the first rename message count, not the final result. Someone with a quick eye and quicker fingers can alter the final result based on what the other one picked, I think.

Also, new game: Tron Rock Paper Scissors!

Just have the player choosing odd/even also rename. So, just like your rock paper scissors, well, you could actually just do rock paper scissors using the rename procedure sinewav gave. That also reduces the number of players who have to participate in the decision to the two team leaders.

Great, problem solved! Both team leaders rename to rock/paper/scissors!

[sinewav]

Great, problem solved! Both team leaders rename to rock/paper/scissors!

Damn, that's even better!

[Concord]

know it's knot. it's much worse.

1/3 of the time, you'll have a tie. That mean's you'll have to do a second round.
1/9 of the time, you'll have two ties, and will have to wait three rounds for a result.
1/27 of the time, you'll have three ties, and will have to wait four rounds for a result
etc. with the possibility of going 10 rounds, or 100, or 1000!

Your expected number of rounds approaches ~1.5

That sucks. A lot of times debating the issue will be quicker than that.


The following is a better method.

Each player renames to either Concord or Drocnoc (any two words will do as options, but I prefer these).
If both players have the same name, then the player who is listed as renaming first in the server output wins.
If the players have different names, then the player who is listed as renaming second in the server output wins.

This is simple and will always take only 1 round.

[sinewav]

But the server output could be different for each client.

[Concord]

then decide the round before who is same and who is different.

still much better

or whoever's original name comes earlier alphabetically is same

still much better

or whoever has the lower ping is same

still much better

[sinewav]

then decide the round before who is same and who is different.

They can use rock/scissor/paper to decide! \o/

[kyle]

heck combine the 2

rename to rock / paper / scissors but have someone call even or odd and append that to name

that is the tie breaker of it


(though I'm still not really sure why this should be done instead of boded server wins, Unless Server is Ub3r pathetic)

[sinewav]

(though I'm still not really sure why this should be done instead of boded server wins, Unless Server is Ub3r pathetic)

Right, there is already a rule for servers, but this "Decision Maker" has some practical uses, like, two people arguing for a center position in a Fort game, or a tactical decision, or even to determine who gets to substitute between a pair of players in pick-up.

Regarding Ub3r pathetic servers, hopefully there will be a mechanism one day to help determine if a server indeed sucks and switching would be better.

[Lucifer]

Regarding Ub3r pathetic servers, hopefully there will be a mechanism one day to help determine if a server indeed sucks and switching would be better.

That system's been in place for years. Player says "This server sucks." Others agree. "Let's try a different one." All players move.

We've been doing that since eggcozy thought Breakfast Burrito was a server name. We usually ended up on his server, except when we wanted a team game, in which case we ended up on my server.

[sinewav]

Player says "This server sucks." Others agree.

Do they agree by using rock/paper/scissor-tron!?

You know this reminds me of one instance several months ago when Team Unknown played Crazy Tronners in a Ladle semi-final. A few USA members of uNk has serious problems connecting to the EU server. We asked if we could use the backup to make the match fair but CT refused. We even offered to play on a different EU server of their choice but they were adamant about their decision to stay. Needless to say the first match was a total blow-out. After they realized we weren't just trying to get some "server advantage" and we actually had problems they agreed to switch. Unk still lost the final, but at least the second match fair.

Would even/odds or r/p/s helped in that situation? Probably not. No team wants to gamble with a Ladle win. But I still think this clever way to make decisions is still useful for lesser conflicts.

[Clutch]

The team leaders just 1v1 in the middle of the grid

And they have to play the song from this scene

[Concord]

if rock, paper, scissors shoot is implemented over my suggestion, I'm never playing this game again.