Publius_Scipio wrote: »
NightbladeMechanics wrote: »@Crispen_Longbow merging Azura's and BwB is a good idea actually.
I don't see why labeling Trueflame as the "main" campaign and Had as "overflow" or your other drastic changes to Had are warranted, though. The population reaches lock on weekends, and the map gets really active during prime time every night these days. It takes only a brief visit to see as much...
Also small scale will not be limited to battlegrounds in June. Open world will still be more unpredictable, demanding, and skillful.
I could get behind a group size reduction for all campaigns, though. 24 is monstrous in the current state of the game.
NightbladeMechanics wrote: »@Crispen_Longbow merging Azura's and BwB is a good idea actually.
I don't see why labeling Trueflame as the "main" campaign and Had as "overflow" or your other drastic changes to Had are warranted, though. The population reaches lock on weekends, and the map gets really active during prime time every night these days. It takes only a brief visit to see as much...
Also small scale will not be limited to battlegrounds in June. Open world will still be more unpredictable, demanding, and skillful.
I could get behind a group size reduction for all campaigns, though. 24 is monstrous in the current state of the game.
Crispen_Longbow wrote: »PC NA
BWB and Azuras (New to PvP and Low CP) should just be merged into one NO-CP campaign. Would make it a more active server for new and low Level CP players. Should be labeled as such.
TF (Large Scale Organzied PVP) - currently main server as that's the campaign that the most active guilds are homed. Should be labeled as such.
Had - (Medium Scale PVP) spill over campaign smaller scale. Map could be redesigned to remove the emp ring of keeps. All factions have only the 3 scroll home keeps. The inner ring of keeps is replaced my a 3 bridge system that replicates the bridge between Alesia and sejanus. At the center of the 3 bridges is a single capturable outpost. Cap max group size to 8
Small scale PVP will be battle grounds in June.
PenguinInACan wrote: »NightbladeMechanics wrote: »@Crispen_Longbow merging Azura's and BwB is a good idea actually.
I don't see why labeling Trueflame as the "main" campaign and Had as "overflow" or your other drastic changes to Had are warranted, though. The population reaches lock on weekends, and the map gets really active during prime time every night these days. It takes only a brief visit to see as much...
Also small scale will not be limited to battlegrounds in June. Open world will still be more unpredictable, demanding, and skillful.
I could get behind a group size reduction for all campaigns, though. 24 is monstrous in the current state of the game.
The populations on AZ can reach lock on weekends (with the map being generally equally active even with the zergs), so I don't think the servers could handle the additional populations from BWB. I also don't know what BWB is typically at population wise but i fear merging them would just cause a lot of overflow onto TF or Had.
I know most of us play on AZ because we prefer no-CP, so increasing the population (and potential queue-times) just to consolidate for the sake of consolidation I do not think would work.
Not to mention the imbalances that would happen for the non CP-160 players that get pushed over from BWB due to gear/skill availability.
Crispen_Longbow wrote: »PenguinInACan wrote: »NightbladeMechanics wrote: »@Crispen_Longbow merging Azura's and BwB is a good idea actually.
I don't see why labeling Trueflame as the "main" campaign and Had as "overflow" or your other drastic changes to Had are warranted, though. The population reaches lock on weekends, and the map gets really active during prime time every night these days. It takes only a brief visit to see as much...
Also small scale will not be limited to battlegrounds in June. Open world will still be more unpredictable, demanding, and skillful.
I could get behind a group size reduction for all campaigns, though. 24 is monstrous in the current state of the game.
The populations on AZ can reach lock on weekends (with the map being generally equally active even with the zergs), so I don't think the servers could handle the additional populations from BWB. I also don't know what BWB is typically at population wise but i fear merging them would just cause a lot of overflow onto TF or Had.
I know most of us play on AZ because we prefer no-CP, so increasing the population (and potential queue-times) just to consolidate for the sake of consolidation I do not think would work.
Not to mention the imbalances that would happen for the non CP-160 players that get pushed over from BWB due to gear/skill availability.
Isn't there close to a 100 page thread about population imbalances, night capping, and zerging when population is dead?
I will just build some animated gifs this week on the populations to see how they are. If a campaign only locks for a few hours on the weekend and is dead the rest of the time it's better to merge them.
PenguinInACan wrote: »
The problem isn't in recent trends though. ZOS analyzes data over several cycles and AZ has had similar population to TF on peak hours/weekends several times over the past 4-6 months. (and thats when we need the best server performance) The recent/current population imbalances shouldn't be considered by themselves but added to the larger pool of data. Only ZOS really knows the true population trends (including IC) so guesstimating based on seemingly inaccurate population bars wouldn't tell you much more than who decided to take a break for a weekend.