Boot Handling

From WarfishWiki

Jump to: navigation, search

Previously known as 'Bug & Feature for tournaments' --FadeToOne 23:27, 1 April 2008 (UTC)

First, if you turn off the "3 boot" filter and select "check all", none of the unfiltered players are selected.

Yeah this was an intentional slight of the booted players, not to make it too easy to invite them. Maybe this was overly aggressive. It actually took extra code to store who was "too booted" to be "check all"'d so I could not check them... maybe it was unnecessary --Steven 14:30, 18 December 2007 (UTC)

Second, can the filter be changed to a percentage vs a boot number. I have seen some very good players who are no longer in the primary list because they have been booted 3 or more times. However, they have played a lot of games. I suggest if you have been booted 3% of the time, then you should be filtered.--Eric 22:03, 13 December 2007 (UTC)

How about instead of percentage expiring the boots after some amount of time? This way it is annoying to when you get booted but the pain goes away after 30 days. The percentage scheme would work also, but seems like if you were a heavy user and then got a boot it wouldn't really affect you at all (and it seems like it should) --Steven 14:30, 18 December 2007 (UTC)
The sounds good to me (expire after 30 days) --Eric 17:10, 19 December 2007 (UTC)
Booting is such a severe penalty that a lot of people hesitate to do it, even when a tournament player is absent for an unacceptably long time. Have you considered introducing a penalty that is less severe, Steven? You could, for example, introduce a special bot that takes the turn of a player who is absent too long.
I imagine it working something like this: Say a player goes on vacation for two weeks and is away from the internet all that time. The tournament "vote out" time is two days. After the player has failed to move in two days, the bot steps in and takes his turn. The other players take their turns, and it comes around to the absent player again. This time the player is marked as a known absentee, and his allowed response time is cut in half to one day, after which the bot takes his turn. The next time around the allowed delay is cut to 12 hours, then 6 hours, then 3, and so on until it reaches a floor of perhaps 1 hour. The player finally comes back from vacation and resumes taking his own turns. His only penalty is that the moves made were probably not as good as those a human player would have made.
A system such as this would nicely handle those absentee players and reduce the bog-down that afflicts many tournaments because of these players. Booting would be less of an issue and it would probably not be used much.
--Red Baron 19:48, 19 December 2007 (UTC)
If there was a "user status" feature that allowed you to set it to "On Vacation until Jan 1, 2008" would that help? It seems like most people are ok with waiting if they have indication that the slow player is on vacation, etc. Some players just post into the game message boards "I'm out until X". I guess these we're talking about 2 different methods of handling the same issue.. that are both useful for different cases and probably should both be implemented. I sorta prefer not going to "default bot" but I guess it should be left up to the players... with "default bot" it seems that you're no longer really playing with that person anyhow.. so that may affect the rest of the game.. for example if you're counting on someone to "do the smart thing" as part of your strategy as well and he happens to go on vacation and his bot starts doing something silly, in cases like that I'd rather just wait for him to get back. I making these various methods of keeping the game going user configurable would be the most flexible. --Steven 17:53, 20 December 2007 (UTC)
Take a look at Games 33 and 41 in this tournament. There is a player who hasn't played in about two months who is essentially delaying the whole tournament. Nobody seems inclined to boot him (though I think the host finally booted him from Game 33). The suggestion I made came from thinking about how you might build a solution to this problem into the system. --Red Baron 19:28, 20 December 2007 (UTC)
I see what you mean. Two months though... I'm wondering if that falls under the "vacation case"? It would be nice to differentiate between that guy actually losing out of the tournament and his robot playing his vacation moves and then losing out. Still seems like with or without the robot he is affecting the quality of play of the tournament... seems like booting would be appropriate though here.... Some folks have requested an auto-boot option as well as another solution to this, what do you think? I'm going to start a list here of all the options.. not necessarily an either or since a lot of these can be implemented as options and left up to the hosts or the users to set themselves --Steven 19:52, 20 December 2007 (UTC)
An "Auto-boot after xxx days inactivity" tournament option would certainly be another solution to this problem, though you would then want some way to allow a player to request vacation time. --Red Baron 20:20, 20 December 2007 (UTC)
I could create a vacation bot. My first cut on this would be one that puts down its armies and doesn't attack anyone (kind of like a neutral). However, Steven would have to build some infrastructure to turn let people turn it on. I think a bot that did only that when someone was gone would be fair. Option! Have it run only if it has be 2/4/7 days. Sometimes you can get to a computer during vacation and sometimes not. This would give you 2 days to make your turn, then run the bot. An alternative is to have this be the default action for all tournaments - you don't make your move, the vacation bot does it for you. --Eric 14:58, 26 December 2007 (UTC)
Hmm... would it make sense to always make the behavior of the bot straightforward and predictable... so that when the vacation bot takes a turn for a player it would just keep the game moving but not overly affect the outcome. Also then other players will know what to expect when the vacation bot takes a players turn. --Steven 18:46, 26 December 2007 (UTC)

[edit] Additional Boot Handling Options

  1. Boot expiring (to reduce the pain of a boot)
  2. Vacation-bot to cover for a user during vacation.
  3. Vacation status indicator
  4. Auto-boot timer

Back to Enhancement Suggestions

Personal tools