wicked wrote:It's not cheating, but it is grounds for neg. feedback... at least the part about them announcing it's a RT, then bailing. It would be the best way to warn others about what they're doing, which I think it pretty lame.
The only thing about it that makes it not cheating is the fact that there are no CC rules preventing teams from moving together. Obviously that, in itself, is perfectly fine.
It is, however, cheating within the context of that game because they laid the ground rules and then failed to observe them. It is not cheating to stop and rest if you are running. However, if I challenge you to a contest of who can run the longest without stopping to rest and then I, myself, stop to rest, that is cheating.
Honestly, the more I think about it, they're pretty much guilty even if the reason for one player's delay is legit. As the OP states, team 2 is a bunch of strangers who are unlikely to be able to coordinate play at a later time. Team 1 refuses to make moves in a timely manner because they want the advantage of moving together, an advantage that delaying the game is likely to be deprived from team 2. Fact is though, it's their fault that the thing is being delayed and, legit or not, they invited team 2 to play under those circumstances.
Much like the sentiment to "suck it up" that is often tossed around in defense of those who delay games on purpose. Once again, the advantage is being given to the person or team that caused the problem.
Instead of team 2 having to "suck it up" because of the tired "you should know better if you join a team freestyle game" how 'bout team 1 "suck it up" 'cause your teammate is the one who had to bail and it is you who failed to keep the rt game alive even if it was for a good reason.
