wetty11 wrote:
pokerguy wrote:
tomski wrote:
Hello
I know there's been a lot of discussion, but is there an agreed / gentlemanly way of resolving a tailing loop?
eg. game 605720 where plane A is tailing B is tailing C is tailing A so nobody moves coz we're all waiting for each other...
Or should we just come up with some random way?
Thanks
Tom
I think the fair way in a 3 player loop is for the player tailing his teammate to move first.
Agreed. Though that should go for any number of players in a loop. If you are tailing a teammate then it is up to you.
I think a large part of this problem is that once a tail request is put in most people do not look at a game again. Most of us only look at games that come up as being our turn in the list. This is especially true for non-league games where there is no status to see.
I am in a league that is difficult to finish because the player who should move and turned off the email communication part in his profile. He logs in and makes moves but clearly does not open his old games or look at the league status pages.
I'd propose this 'gentlemans conduct' rule for tailing loops.
If there are an even number of planes in a tailing loop - then every other plane in the loop should have to move, and to decide if it is plane 1 3 5 7 or planes 2 4 6 8 etc - either pick at random - or I'd suggest that the plane closest to their home line (in terms of hexes, and in terms of facing that's a tie) ought to be one of the planes that has to move.
in an odd number of planes in a tailing loop, there will always be someone tailing an ally, I think they ought to be the plane to move first.
If the coders wanted to detect tailing loops I think they probably could, then they could perhaps work out which planes were now 'obliged' to move and give them the 'play' button again - and the message 'you are tailing EdwardLaneUK - it was a tailing loop, you must move'
or something like that
Edward
Donate
Leagues
Gonzaga
Blue Max
Cartagena
Wooden Ships...
King Me!
VampiRing
