Lots of talk about wars and how to “balance” them or improve them.
I know a very common complaint is when wars start. Now, technically, this affects everyone the same, since wars, as long as both teams have and keep 50 members, are 24 hours long. But, in reality, being the “first mover” has many advantages. Especially if you manage to get to 250 before the other team gets above 50 or so. You know exactly how many times you have to defend before the war is yours.
As something to consider, what if teams were allowed to set the times they could be vulnerable to a war declaration? Teams can pick a “prime time” for themselves, each day (or have larger windows of vulnerability so that they are not “on alert” every single day.
So, let’s say a team has to be vulnerable, just as an example, 18 hours a week. Most of this team’s players are in the US, and they are fairly active most nights, and very active on Saturday. And they have a few members who, due to other obligations, cannot play on Sundays. To facilitate this, they choose not to be vulnerable to wars on Sunday at all. So, they have to be vulnerable for 18 hours over the remaining six days.
They could, if they wanted, be vulnerable for 18 hours all in one day, but they could easily end up with 24 wars if they did this, and all of them staggered by 40 minutes. So, that is probably not a good approach. Might work for Dread.
Back to realistic. ideas for the mortals . .
Prime time is the center – so, if a team sets a 3 -hour vulnerability window with a Prime Time of 9:00 PM Eastern, they would be vulnerable to a war declaration starting at 7:30 PM Eastern time and ending at 10:30 PM Eastern time. Wars could be declared at any time in this window. But outside the window, wars cannot be declared (well, they can be, but they will not start until a vulnerability window begins).
In the League menu, teams that are currently vulnerable could have an Icon indicating such, could even be something like a simple red or green dot. Just something so that each team does not have to be looked at individually to see if they are vulnerable at that time. Windows must be at least one hour.
Anyway, back to the three-hour window this team has set on Monday. Any time in that three hours, any team in that league could declare. Wars start every quarter hour, so an attacker can still have that element of surprise by declaring 10 seconds before the next quarter hour. Don’t be late though, or the defenders will know you are coming.
Now, this team doesn’t really like committing to wars or at least having to watch for one EVERY night. And, they do have some players in England and a couple in Germany as well. So, instead of a 3 hour window, they opt for a 6 hour window, and start it at 6:00 PM Eastern. So, they are now vulnerable from 3:00 PM Eastern until 9:00 PM Eastern. And they know they can have at least some players on for that entire time.
Now, they have 12 hours remaining in which they can be vulnerable that they need to asign.
They choose to have a 1 hour window on Tuesday with prime time at 8 PM. (so, vulnerable from 730-8:30).
They have another 6 hour vulnerability window on Wednesday at the same time as Monday. So, 5 hours left.
Thursday, they set no window. They can be declared on, but the war will not start until the next window.
Friday, 2-hour window with prime time at 9 PM.
Saturday, 3 hour window, starting at 3 PM. (They are active, but they also want to work on the event, whatever it is).
Sunday, no vulnerability.
Vulnerability windows can be changed weekly, but once set, they are “locked in” and cannot be changed–or, they can be changed (i’m thinking in a panel similar to the war availability panel in “more settings”), but no changes take effect until the next league shuffle.
Another team may opt for smaller windows, but have them every day every day.
This has no effect on when a team can declare, only upon when they can declare on a particular team. Or, specifically, if they want to give the other team a warning that they are going to be attacked, they can declare whenever, but the war will not start until the next available quarter hour of the next available window.
18 hours is just a suggestion. Maybe it’s too big, maybe it’s too small.
What are your thoughts?
I’ll make a couple surveys to more easily capture general feelings, but please feel free to leave comments or suggestions or criticisms (constructive)–if you don’t like it, that’s fine. But please say why you don’t like it and not just that you don’t. I’m asking because I know there are a lot of people out there, and together, maybe we find a better solution… Or maybe I’m asking the wrong question here.
It’s only an idea I’m floating as a way to help balance out the war start-time bias.
Fundamental Question: Is this idea workable in some form:
- Yes – Vulnerability windows would help balance one aspect of wars
- No – Vulnerability windows would not help or would create more problems than they solve
How much time should a team have to be vulnerable?
- Less than 10 hours per week
- 10 to 12 hours per week
- 12 to 18 hours per week
- More than 18 hours per week
Should League be a factor in the minimum number of vulnerable hours?
- Yes – Higher leagues should require more total vulnerable hours per week
- No – League should not matter
- No – But leagues below platinum should have a smaller minimum requirement per week
Did I leave out any important questions (at least for starting)?
- Yes – and I’m going to tell you in my comment
- No – You asked everything I would have!
Thank you very much to anyone who provides some input. Again, this is not a proposal–it’s just an idea that maybe could address the fairness of war start times.