So, according to Wiki, even though the move order is random each turn, teammates will never go moves 1 and 2.

QUOTE: "In team games, WarLight ensures that teams are first randomized into their own move order, and then the players within each team. For example, in a 2v2 game, it's not possible for both of team A's players to get to move before any of team B's players."

Link to wiki: http://wiki.warlight.net/index.php/Move_Order

But does that mean that teammates also will never go 1 & 3? I'm talking about the 2v2 ladder. Anecdotally, I have not noticed a game where teammates ever move both first and third (assuming all four players make a move), always 1st and 4th or 2nd and 3rd. Is this just a coincidence in the games I checked? Or is it a hard and fast rule?

Also, why in this game did teammates move 1st and 2nd while the opponent moved third?

Game link: http://WarLight.net/MultiPlayer.aspx?GameID=2707536

In turn 12, the last turn of the game, there were only three players left. On the team of two, one teammate played the order priority card so he went first. Then his teammate moved second. Then their only remaining opponent moved third. Is this because the player moving first was selected to move third during the randomization process but happened to play an order priority card jumping him to first while the other players remained in their pre-determined move order? Is it a bug that's triggered when one player is booted? Either way, does this mean that until further notice, it is possible for teammates to move 1st and 2nd when one of them plays the order priority and neither opponent plays any card?

Thanks for the help.

On turn 12, orinocoflows played an order priority card, which is an exception to the regular move order rule. If you play an order priority, your move is moved to irst regardless of what the determines random order was.

In a 2v2 game with team A consisting of players 1 and 2, and team B consisting of players 3 and 4, the move order would be either 13422431 or 31244213.

(team a: x y. team b: w z) it is perfectly normal that in a 2vs2 the move order is like this xzyw. infact z move before than y and so the rules is not broken, regarding the order priority hurey already well explained. it was probably a casuality that u never see that, i can paste here games wich had xzyw move order, but maybe in the ladder games could be different but i dont think so.

Your Time, I wasn't didn't think the AZYW order was possible (without order cards being used). I also can't seem to find one in one of my games. Any chance you could post one for my conformation? Thanks :)

http://warlight.net/MultiPlayer.aspx?GameID=2662705 u can see by the picking turn this type of move order. in fact both me and bel had the second choice in our picks, and according to me this can only happen with that kind of move order or with a break of rules. instead except for the picking moment move order is usually abba or baab

ahah ups i think i made an error here cos i think that we were speaking about cyclic move orders, infact if u see the chat of that game also team c was asking us how it would be possible, so i'm not still so secure about my first answer (cos i've based on that very game) now i'll give a check to my other game for a better answer

aahah infact i was wrong. i've doublechecked the wiki rules and in cyclic games necessarily happens that sometime both the player of a team have the first and second move. instead in random move order can be just abba or baab.:P hope i didnt puzzle u:)

general arun has a new entity

uhuhuh but i still think that trying to be useful, is better than being acidic

if every semi-literate internet commenter is general arun, he's really putting in a lot of work.

@Your Time Is Gonna Come #Elite! (such a long name!!) i totally agree with you. i like to read the threads but unfortunately some people always ruin them posting stupid jokes, that, more over, are not funny at all. (they must have a pathetic life, so just ignore them)

raptor, you?

?

Sorry for bumping old thread, didn't find a newer one.

We just got jacked in a 2v2 where the same person got first move in consecutive turns without cards. Since it randoms teams, then within, it can happen.

My question is whether it should be that way in strategic games?

im sure i recall that we voted on cyclic move order for the 1v1 ladder and it was rejected. so, chris, i dont know if theres any cyclic support for the 2v2 ladder.

Back when I was new, I was against cyclic. Now that I know how to use it, and the other concepts aren't so foreign, I wish we could have a new vote on it.

Other things to vote for might include straight rounding, a 3v3 ladder, and perhaps even a change to the map, like the new East Russia variation.

Sure, "we" decided a long time ago what to do, but that was probably a year ago, and many of the regulars of that time are now gone.

fair enough, but i would have thought that The Fiz would be reluctant to change something that was already voted down.

If it was voted down by a huge margin, maybe he'd be reluctant to change something. I can't see the harm in having a new vote, though, and seeing how much support some of those ideas might have.

Well, I am casting my vote for teams alternating first move every time. It can stay random within teams, but IMO it sucks to have one team (sometimes 1 person) get first move 2, 3, etc turns in a row on you without cards. Very annoying.

The point of strategic IMO, is to take MOST of the luck out of it and let the best strategy win. So why have a feature that is complete luck in there like that?

I think it should change. It frustrates me enough that I might not even buy a membership/join the ladder because I know it will happen all the time then...it does to everyone (and I will care even more than I do now).

It frustrates me enough that I might not even buy a membership/join the ladder because I know it will happen all the time then...it does to everyone (and I will care even more than I do now).

that's just silly.

also, now that you have CLOT, you can make your own ladder with your own config.