@Slammy, there is. It is currently at 100 days. (so no auto-boot= 100 day auto-boot)

Additionally I find it silly that there are 1v1 games with lower VTB than Direct boot, effectively hiding the actual limit. That's a completely different issue though :p

Edited 2/16/2015 16:08:52

so what has been said, what has been understood, what will be done?

someone may have said this but I refuse to read this whole thing, my solution is simple

a 10 day auto boot is required for all tournaments (Or less if wanted)

i very rarely visit the tournaments page, i believe most players equally only end up participating in tournaments by invites.

i don't think creating tournaments should be limited to members only, but they could atleast raise the level required to create them a little higher.

or cancel tournaments that are open for too long or have way above average number of declined invites (might be good indicator that folks made a bad template or are troll spamming it to people who don't care about such settings).

i think the trolls and bad template makers will still keep creating crappy tournaments regardless of any of these changes though.

so i would suggest better visibility to the open tournaments instead of stricter rules to cancel them.

a widget on the multiplayer dashboard listing the number of open tournaments. something similar to the real time ladder widget. i think that would do the trick.

The multiplayer dashboard is so cluttered already :(

A significant issue with tournaments is that people join then months go by, the tourney finally starts, but in the interim, people have left WarLight and so their teammates get screwed.

I would suggest the following:
- Invitations expire one week after being sent
- Invitations cannot be sent to inactive players
(no active games in the past week && > 1w inactivity)
- After accepting an invite, if a player goes inactive,
he's removed from the tourney attendees
- Every month a player needs to confirm their desire to
attend the tourney - failure to do so (within a week)
is an auto-decline
- If a tourney has declined (or failed to improve) in
accepted members over a month, the tourney owner is
asked whether he wishes to cancel the tourney
- If a tourney owner is asked three consecutive months
and attendance has not gone up, the tourney is
cancelled.

Most of this was already stated and would fix a lot of problems. Not saying I agree with all of it (mainly the time limits) but this can be adjusted to be more reasonable

Right now the open tournament page only shows the name of the tournament, what type of tournament it is and what the status of it is. For someone to even see what map it is he must to go into the setting and try to find it.

My solution to the problem would be to make it easier to find the game you want to play

---

mlb cubs

Edited 3/7/2015 23:44:02

I personally rarely join tournaments that are so large for fear of them getting stuck forever. If I get invited to a tournament that was made over 3 months ago, even if it only has 3 people left to join, I will decline. I have no incentive to join large tournaments like this

[I wrote the following but then checked some of the previous posts and saw that Fizzer had already considered the essential idea I put forward - well actually some other people thought in similar lines, unbeknownst to me earlier. See Fizzer's comments posted @ 2/10/2015 18:37:03

But I'll keep the following anyway. I still think the essential idea is good!]

- (to Fizzer) Just clear all of the tournaments which either (1) are at least one year old and haven't started yet, or (2) have no preset auto-boot time and stuck at one point for the last 3 months, for example [the points already earned are kept as is]


In the new system:

- Invited players should respond in 10 days max. If they don't, the invitation should expire.


- As has been said in a previous post (2/24/2015 03:31:12) there must be a preset auto-boot time. It could be 5 days by default. A tournament host should be able to extend (max. 10 days) or shorten it.


- A newly created tournament should be forced to start in -say- max. 2 months:

(a) If it can't start in a month, the host should be allowed to start it with the maximum number of players that can be accommodated within the elimination framework chosen.

..... e.g. You have an individual tournament (no teams, 1v1) which isn't round-robin, requires -say- 128 players, but only 110 players have joined by the end of a month. Then the host should be given the choice to start it with 64 players. If she approves, then the tournament starts with the 64 players who joined first. If she doesn't approve, the tournament is given an extra time for forced start (= 1 month extra, according to my suggestion above - see (b) below).

..... e.g. You have a team tournament (say, 2v2), which isn't round-robin, requires -say- 128 players (= 64 teams), but only 80 players have joined by the end of a month. 60 of them have their teams (30 teams are ready), 20 of them are waiting for teammates. Then the host should be given the choice to start it with the 16 teams which were formed the fastest. Again, if she approves, then the tournament starts with the 32 players who formed these teams. If she doesn't approve, the tournament is given an extra time for forced start (= 1 month extra, according to my suggestion above - see (b) below).

(b) If it doesn't start in a month, it is given an extra month. If it still can't start by the end of the 2nd month, it is forced to start with the maximum number of players that can be accommodated within the elimination framework chosen. This time he host is given the options to either force-start the tournament or completely cancel it.

(c) If the tournament is forced to start somehow, an identical tournament is created automatically with the players who are not able to play in the original one. If there are teams already formed, they are maintained and carried to the identical tournament as is. For the second tournament the host is the same initially (she probably won't be an actual player in that one), but she can leave the post to someone else.

Edited 3/19/2015 21:14:43