Perrin, you're right, my system first proposed would still not solve the problem of people ruining games.

Blue, you also provide a good point, but it doesn't solve the issue of games being wasted.

I came up with a fool-proof solution

When a player in a game gets booted, the game is paused, and placed back in the lobby for another player to take the booted players spot. Once this happens, the game begins again.

This is perfect right? I can't think of a flaw to this.

I disagree 10 minutes is perfect for a 5 minute boot game : / I often have connection problems, but I generally get solved quick enough. If not, apologize and move on

Although the examples givn in your second post have never happened to me yet : /

>When a player in a game gets booted, the game is paused, and placed back in the >lobby for another player to take the booted players spot. Once this happens, the >game begins again.
>
>This is perfect right? I can't think of a flaw to this.


Hmmmm. OEJ, that's a really interesting proposal. I guess one problem that I see is additional delay, but that's preferable to having the game end with acrimony and name-calling. Also, if a game has gone beyond a certain point, it might not be reasonable to assume that someone seeing it in the lobby is going to join it. I mean, say someone on a clearly losing team gets d/ced and then booted. Is anyone going to pick that spot up? I doubt it. So maybe one refinement to your proposal would be that the game goes into pause mode for a short time, perhaps a fixed interval like three minutes, or a percentage of the boot time that's appropriate, and if no one takes the spot by them, the boot becomes permanent and the game moves forward. That would at least give you, and others frustrated by booting, a chance at seeing some games - - particularly early ones where somebody doesn't join in time, and the other team boots and refuses to VTE - - resolved in a more satisfying fashion.

I like the idea of a 2 minute grace-period and a popup. Pretty much all of my boots happen because I don't hear the end of turn buzzer, and forget about it.

The thing I absolutely hate is booting in team games. Don't get me wrong, I think there are times it is appropriate. But, if it's 2v2, booting somebody quickly after they run out of time for the first time is a dick move. By far my biggest pet-peeve of WL.

how about this guys, vote for it

http://warlight.uservoice.com/forums/77051-warlight-features/suggestions/1399961-a-solution-to-boot-problems

and also: Booting is not really a problem, if you can't make the boot time in a game, you shouldn't join it. booting isn't the problem, people who hold up games are the problem.

one last comment.... if you are on Blue's side: vote for the User-Voice option of Online/Offline status, that way there would be less people that would vote to boot if the player was online, because they might be be just checking another game or going to the bathroom or something, and not signed off.

OneEyedJack this idea -->When a player in a game gets booted, the game is paused, and placed back in the lobby for another player to take the booted players spot. Once this happens, the game begins again<-- is brilliant. I had a game going on where it was a 3v3 at first, then turned to a 2v2 after one from each team got booted. It was a 25 hour boot so it was a relaxed game, then I came back the other day to find my teammate booted to make it a 2v1, which both members of the other team knew it would get them the win. I got verbal, sure, but with justification. People come on this site to have fun, not for the stats...and if you boot someone in a 2v2 game like that, it's like...why? You get the win because you were impatient? Congrats?

I would also like to propose that if someone is booted in a game the end result doesn't show up on your stats, even if you get booted. That way, people quit booting so easily. For some reason I can't get the link to the game previously mentioned, which is annoying. But Marcinek and Vespasian were the players left, and Vespasian was the one that booted my teammate, making it a 2v1. Both are blacklisted, and I suggest that unless you want to stop playing and start taking a game seriously like they have you do the same. Links to their profiles:

http://warlight.net/Profile.aspx?p=771552052


http://warlight.net/Profile.aspx?p=742381460

here's the link to the game I mentioned in my last post:

http://warlight.net/MultiPlayer.aspx?GameID=1174075

>When a player in a game gets booted, the game is paused, and placed back in the >lobby for another player to take the booted players spot. Once this happens, the >game begins again.
>
>This is perfect right? I can't think of a flaw to this.

great idea, look at my stats!! i have been booted in 40% of games

You can also solve this by only playing long boot games. Most of the booting problems happen with the 5 min boot games. When I set up a game, I disable vote-to-boot and enable direct boot at a week, and then I just fuggedaboutit... If that doesn't give you enough of a warlight fix, join BUNCHES of long boot games and you'll end up with more turns than you can handle...

Or just use the banking boot time feature and you'll build up sufficient reserves to handle a disconnect if it occurs.

Having said that, I think a one minute boot warning is a good idea for real time games. It would enable players to hit confirm or skip changing an order, etc. Those boots must be very frustrating.

I disagree with the assertion that most boot problems are with the real time games. In fact, I'd argue the reverse. There's a sense of understanding with most real time games and a fairly standard unwritten rule of booting at 8 or 10 (in 5 min games) but only after a shout out for the missing person and, then, when someone calls to vote to end it's rarely an issue. My multi-day games are a different story. Someone goes on a boot frenzy within a couple hours of the boot time (I've actually seen someone boot 4 of the 6 players in the game right at the boot time) with absolutely no shout-out and arguments over voting to end... even if the boot(s) kill the game, which they often do.

Go back and look over the various posts of people complaining about being booted. The vast majority of them are involving 5min boot games. That's a pretty clear signal...

Well, open games with just about anybody might have the same problem, regardless of being 5 minutes of 24 hours long. It's just that there are more 5 minute games played (I think?) than 24h, so consequently there have to be more boots.

Imho, multi-day games are easier to not get booted from, presuming you don't overload yourself...

devilnis - I can only speak from my own experience and maybe Matma Rex is on to something. I play more real time games than multi-day (usually have only 10 or so multi-day games going on at a time) and so maybe the boots from multi-day games stand out in my mind. But during and just after the holidays, half of my multi-day games ended because of the large number of boots happening in them.

Hmm well I've only been booted 5 times in over 250 multiday games, but maybe it's just the people I play with, sometimes I feel like there's a bunch of closed circles of people that play each other, with no interchange between those groups...

most of my boots were from real time games.. my own fault really, trying to play 3 5 minute games at a time...

when you say after 5 minute boot a two minute delay, then itd just be 7 minute boot.

No because it's two minutes from the actual boot. If you like the 5 minute format make it 3 minutes. That would make 5 minutes the floor, but the max would be whenever the boot occurs + 2 minutes. The idea is to prevent tricky double boots (like when one player changes orders after seeing no boot of another player that's gone over.