What is the issue of having a place for players who don't want to deal with proc sets? It doesn't matter what you consider a proc set. Proc is an effect beyond a set like Hundings, Spinners or Shacklebreaker type sets. If it has an ignition effect or conditional with (or without) a cooldown then it is a proc. Clever Alchemist is a proc. Mech Acuity is a proc. Hist Sap is a proc. They are all procs. There is server space to support having these environments. I don't care about specific sets. There needs to be an environment where Rush of Agony isn't in the game. There needs to be a place where the Rallying Cry ice-berg tip of set power creep is not there.Major_Mangle wrote: »If you want to kill battlegrounds completely, sure go ahead and disable 80%+ of all sets. Sure we need some sets to be adjusted (acuity ain't one of them however). But restricting what sets you can use has proven not to be that likable by the community as a whole (Ravenwatch being the prime example of this)
Edit: Most of the problem "proc sets" people tend to complain about aren't even "proc sets" (aka sets doing damage for you) but rather stat enhancing sets (I don't consider acuity a "proc sets" due to the fact that it enhances your stats).
And all proc sets aren't equally problematic. Anti stacking sets like azureblight was considered a healthy proc sets due to the fact that it was a tool against ballgroups anf larger stacks of players, while simultaneously being a bad set used by the groups it counters. If you wanna fix whatever problem/issue you should adress those specifically (even tho ZOS for some reason refuse to adjust problematic things for some reason), instead of asking for global/broad changes that usually ends in disaster.
What is the issue of having a place for players who don't want to deal with proc sets? It doesn't matter what you consider a proc set. Proc is an effect beyond a set like Hundings, Spinners or Shacklebreaker type sets. If it has an ignition effect or conditional with (or without) a cooldown then it is a proc. Clever Alchemist is a proc. Mech Acuity is a proc. Hist Sap is a proc. They are all procs. There is server space to support having these environments. I don't care about specific sets. There needs to be an environment where Rush of Agony isn't in the game. There needs to be a place where the Rallying Cry ice-berg tip of set power creep is not there.Major_Mangle wrote: »If you want to kill battlegrounds completely, sure go ahead and disable 80%+ of all sets. Sure we need some sets to be adjusted (acuity ain't one of them however). But restricting what sets you can use has proven not to be that likable by the community as a whole (Ravenwatch being the prime example of this)
Edit: Most of the problem "proc sets" people tend to complain about aren't even "proc sets" (aka sets doing damage for you) but rather stat enhancing sets (I don't consider acuity a "proc sets" due to the fact that it enhances your stats).
And all proc sets aren't equally problematic. Anti stacking sets like azureblight was considered a healthy proc sets due to the fact that it was a tool against ballgroups anf larger stacks of players, while simultaneously being a bad set used by the groups it counters. If you wanna fix whatever problem/issue you should adress those specifically (even tho ZOS for some reason refuse to adjust problematic things for some reason), instead of asking for global/broad changes that usually ends in disaster.
Battlegrounds currently are all lifeless already. 30 minute queues for imbalanced matches. Its just not enjoyable like 4v4v4 was. Since No-Proc is unpopular, you shouldn't find any hiccups in your usual programming queuing in for Proc Battlegrounds. You don't have to see my point, but its there. You don't lose anything because naturally most players will want to participate in proc content, right? No worries of "splitting the playerbase" will happen. I'm fine with waiting an hour in no-proc no-cp PVP queues just for one good match. This doesn't have any effect on you. This is my point. Ravenwatch and no-CP Imperial City are already dead. They have no purpose, currently. Giving them a purpose, even if that is unpopular, is a gain for somebody. Currently they are a gain for nobody. Adding the no-proc option to Battlegrounds functions exactly the same.
With all due respect my friend, Ravenwatch is still dead today. People STILL just Deathmatch on Flag Games and Relic Games in Battlegrounds. That's not the issue. Modern BGs have more issues now than before starting with finding 16 people in realistic queue times who actually want to play at all. Life never returned to Ravenwatch after the recent change and I was there enjoying no-proc Ravenwatch with a few veteran players until it was slashed. What history has told us is that Ravenwatch will be dead NO MATTER WHAT happens to it. There simply aren't enough Cyrodiil participants (for a myriad of reasons) to fill Grey Host and more. Most people don't want to play in a ghost town anyways.Major_Toughness wrote: »What is the issue of having a place for players who don't want to deal with proc sets? It doesn't matter what you consider a proc set. Proc is an effect beyond a set like Hundings, Spinners or Shacklebreaker type sets. If it has an ignition effect or conditional with (or without) a cooldown then it is a proc. Clever Alchemist is a proc. Mech Acuity is a proc. Hist Sap is a proc. They are all procs. There is server space to support having these environments. I don't care about specific sets. There needs to be an environment where Rush of Agony isn't in the game. There needs to be a place where the Rallying Cry ice-berg tip of set power creep is not there.Major_Mangle wrote: »If you want to kill battlegrounds completely, sure go ahead and disable 80%+ of all sets. Sure we need some sets to be adjusted (acuity ain't one of them however). But restricting what sets you can use has proven not to be that likable by the community as a whole (Ravenwatch being the prime example of this)
Edit: Most of the problem "proc sets" people tend to complain about aren't even "proc sets" (aka sets doing damage for you) but rather stat enhancing sets (I don't consider acuity a "proc sets" due to the fact that it enhances your stats).
And all proc sets aren't equally problematic. Anti stacking sets like azureblight was considered a healthy proc sets due to the fact that it was a tool against ballgroups anf larger stacks of players, while simultaneously being a bad set used by the groups it counters. If you wanna fix whatever problem/issue you should adress those specifically (even tho ZOS for some reason refuse to adjust problematic things for some reason), instead of asking for global/broad changes that usually ends in disaster.
Battlegrounds currently are all lifeless already. 30 minute queues for imbalanced matches. Its just not enjoyable like 4v4v4 was. Since No-Proc is unpopular, you shouldn't find any hiccups in your usual programming queuing in for Proc Battlegrounds. You don't have to see my point, but its there. You don't lose anything because naturally most players will want to participate in proc content, right? No worries of "splitting the playerbase" will happen. I'm fine with waiting an hour in no-proc no-cp PVP queues just for one good match. This doesn't have any effect on you. This is my point. Ravenwatch and no-CP Imperial City are already dead. They have no purpose, currently. Giving them a purpose, even if that is unpopular, is a gain for somebody. Currently they are a gain for nobody. Adding the no-proc option to Battlegrounds functions exactly the same.
Just learn from history.
We can't even have game mode specific queues because majority of people just wanted to PvP and queued DM. All the casuals complained objective queues were too long so they got consolidated.
When the game was more populated than now also.
We now have Group and Solo queues where Group is dead.
A vocal minority wanted no proc Ravenwatch which lead to it being a ghost town for 2 years and ZoS reverted it to try put some life back into it.
You want to combine two things that already did not work (more queues and no proc) which will negatively effect the whole BG population.
Developer resources that should be going to Vengeance?Again, nothing would be lost reverting Ravenwatch.
With all due respect my friend, Ravenwatch is still dead today. People STILL just Deathmatch on Flag Games and Relic Games in Battlegrounds. That's not the issue. Modern BGs have more issues now than before starting with finding 16 people in realistic queue times who actually want to play at all. Life never returned to Ravenwatch after the recent change and I was there enjoying no-proc Ravenwatch with a few veteran players until it was slashed. What history has told us is that Ravenwatch will be dead NO MATTER WHAT happens to it. There simply aren't enough Cyrodiil participants (for a myriad of reasons) to fill Grey Host and more. Most people don't want to play in a ghost town anyways.Major_Toughness wrote: »What is the issue of having a place for players who don't want to deal with proc sets? It doesn't matter what you consider a proc set. Proc is an effect beyond a set like Hundings, Spinners or Shacklebreaker type sets. If it has an ignition effect or conditional with (or without) a cooldown then it is a proc. Clever Alchemist is a proc. Mech Acuity is a proc. Hist Sap is a proc. They are all procs. There is server space to support having these environments. I don't care about specific sets. There needs to be an environment where Rush of Agony isn't in the game. There needs to be a place where the Rallying Cry ice-berg tip of set power creep is not there.Major_Mangle wrote: »If you want to kill battlegrounds completely, sure go ahead and disable 80%+ of all sets. Sure we need some sets to be adjusted (acuity ain't one of them however). But restricting what sets you can use has proven not to be that likable by the community as a whole (Ravenwatch being the prime example of this)
Edit: Most of the problem "proc sets" people tend to complain about aren't even "proc sets" (aka sets doing damage for you) but rather stat enhancing sets (I don't consider acuity a "proc sets" due to the fact that it enhances your stats).
And all proc sets aren't equally problematic. Anti stacking sets like azureblight was considered a healthy proc sets due to the fact that it was a tool against ballgroups anf larger stacks of players, while simultaneously being a bad set used by the groups it counters. If you wanna fix whatever problem/issue you should adress those specifically (even tho ZOS for some reason refuse to adjust problematic things for some reason), instead of asking for global/broad changes that usually ends in disaster.
Battlegrounds currently are all lifeless already. 30 minute queues for imbalanced matches. Its just not enjoyable like 4v4v4 was. Since No-Proc is unpopular, you shouldn't find any hiccups in your usual programming queuing in for Proc Battlegrounds. You don't have to see my point, but its there. You don't lose anything because naturally most players will want to participate in proc content, right? No worries of "splitting the playerbase" will happen. I'm fine with waiting an hour in no-proc no-cp PVP queues just for one good match. This doesn't have any effect on you. This is my point. Ravenwatch and no-CP Imperial City are already dead. They have no purpose, currently. Giving them a purpose, even if that is unpopular, is a gain for somebody. Currently they are a gain for nobody. Adding the no-proc option to Battlegrounds functions exactly the same.
Just learn from history.
We can't even have game mode specific queues because majority of people just wanted to PvP and queued DM. All the casuals complained objective queues were too long so they got consolidated.
When the game was more populated than now also.
We now have Group and Solo queues where Group is dead.
A vocal minority wanted no proc Ravenwatch which lead to it being a ghost town for 2 years and ZoS reverted it to try put some life back into it.
You want to combine two things that already did not work (more queues and no proc) which will negatively effect the whole BG population.
Again, nothing would be lost reverting Ravenwatch. It isn't going to affect Grey Host players in any way. BGs are already messed up, too. Anything is better than what current BGs are.
I guess this could be the solution. I think this would suffice for me, as Vengeance was more than a sufficient adjustment (at least in theory) to make Cyrodiil tolerable since I dipped out of them in 2022. As for Battlegrounds, a Vengeance variant would work for me but I know a bunch of people would get mad about it. Look. As far as my view goes, Grey Host could go offline forever and I wouldn't even care. It's useless to me and even serves as a detriment because I am an Imperial City player. Players queue out during fights to Cyrodiil from Imperial City and that kind of gameplay greatly bothers me. Ballgroups and lag have become so egregious for me that I don't even enjoy playing there anymore. The anti-Vengeance crowd is gonna hate my opinions no matter what.xylena_lazarow wrote: »Developer resources that should be going to Vengeance?Again, nothing would be lost reverting Ravenwatch.
Not sure why this needed to come up in two separate threads, but Ravenwatch was epically unpopular. The game was still broken without procs or cp, just with even fewer ways to try to deal with whatever was broken. Vengeance seems to have succeeded where Ravenwatch failed, so the faster Vengeance gets back online, the better.
I miss the Ravenwatch days. So much fun! The fact that its gone, unable to be revisited again is what drives my frustration on this topic.Major_Toughness wrote: »With all due respect my friend, Ravenwatch is still dead today. People STILL just Deathmatch on Flag Games and Relic Games in Battlegrounds. That's not the issue. Modern BGs have more issues now than before starting with finding 16 people in realistic queue times who actually want to play at all. Life never returned to Ravenwatch after the recent change and I was there enjoying no-proc Ravenwatch with a few veteran players until it was slashed. What history has told us is that Ravenwatch will be dead NO MATTER WHAT happens to it. There simply aren't enough Cyrodiil participants (for a myriad of reasons) to fill Grey Host and more. Most people don't want to play in a ghost town anyways.Major_Toughness wrote: »What is the issue of having a place for players who don't want to deal with proc sets? It doesn't matter what you consider a proc set. Proc is an effect beyond a set like Hundings, Spinners or Shacklebreaker type sets. If it has an ignition effect or conditional with (or without) a cooldown then it is a proc. Clever Alchemist is a proc. Mech Acuity is a proc. Hist Sap is a proc. They are all procs. There is server space to support having these environments. I don't care about specific sets. There needs to be an environment where Rush of Agony isn't in the game. There needs to be a place where the Rallying Cry ice-berg tip of set power creep is not there.Major_Mangle wrote: »If you want to kill battlegrounds completely, sure go ahead and disable 80%+ of all sets. Sure we need some sets to be adjusted (acuity ain't one of them however). But restricting what sets you can use has proven not to be that likable by the community as a whole (Ravenwatch being the prime example of this)
Edit: Most of the problem "proc sets" people tend to complain about aren't even "proc sets" (aka sets doing damage for you) but rather stat enhancing sets (I don't consider acuity a "proc sets" due to the fact that it enhances your stats).
And all proc sets aren't equally problematic. Anti stacking sets like azureblight was considered a healthy proc sets due to the fact that it was a tool against ballgroups anf larger stacks of players, while simultaneously being a bad set used by the groups it counters. If you wanna fix whatever problem/issue you should adress those specifically (even tho ZOS for some reason refuse to adjust problematic things for some reason), instead of asking for global/broad changes that usually ends in disaster.
Battlegrounds currently are all lifeless already. 30 minute queues for imbalanced matches. Its just not enjoyable like 4v4v4 was. Since No-Proc is unpopular, you shouldn't find any hiccups in your usual programming queuing in for Proc Battlegrounds. You don't have to see my point, but its there. You don't lose anything because naturally most players will want to participate in proc content, right? No worries of "splitting the playerbase" will happen. I'm fine with waiting an hour in no-proc no-cp PVP queues just for one good match. This doesn't have any effect on you. This is my point. Ravenwatch and no-CP Imperial City are already dead. They have no purpose, currently. Giving them a purpose, even if that is unpopular, is a gain for somebody. Currently they are a gain for nobody. Adding the no-proc option to Battlegrounds functions exactly the same.
Just learn from history.
We can't even have game mode specific queues because majority of people just wanted to PvP and queued DM. All the casuals complained objective queues were too long so they got consolidated.
When the game was more populated than now also.
We now have Group and Solo queues where Group is dead.
A vocal minority wanted no proc Ravenwatch which lead to it being a ghost town for 2 years and ZoS reverted it to try put some life back into it.
You want to combine two things that already did not work (more queues and no proc) which will negatively effect the whole BG population.
Again, nothing would be lost reverting Ravenwatch. It isn't going to affect Grey Host players in any way. BGs are already messed up, too. Anything is better than what current BGs are.
Beofre No-Proc Ravenwatch was pop locked on PC EU before Gray Host, every night. It was the more popular campaign.
It took too long to correct the mistake of no-proc, and all the previous no-cp players either quit or adapted to CP.
Other than the bug with games not starting if teams don't fill, what issues do BGs have?
Sure I don't find them as fun as 4v4v4 but not sure what problems exist, that completely destroying them with no-proc would fix.
opethmaniac wrote: »I speak from the perspective of Ravenwatch/EU. Before the introduction of proc sets, we had a relatively healthy population. The biggest problem was an overpowered group on DC whose guild leader held the Emperor title for months (many months, I didn't count). AD held up reasonably well, even with Poplock during peak times, but EP declined hopelessly, and many guilds (of all factions) switched to Blackreach when proc sets were introduced. That was the final nail in the coffin for the campaign.
Major_Toughness wrote: »I hate this false information, which was even posted while Ravenwatch was still alive in a desperate attempt to keep it how it was.
Those same DC players were on the forums claiming it pop locked every night. They even said at a certain time on Friday Evenings locked EVERY week. I went on at that time as it was Medium/Low/Low. When presented with that fact and screenshots there was no response.
It did not have a health population or ever hit a single faction pop lock for two years. I do not understand the need to lie.
the1andonlyskwex wrote: »No proc PvP was a failed experiment. The only way I can see it being made to work is if all proc sets gain alternate effects in no proc that are well communicated in game so you can go into a no proc campaign while wearing a proc set and not be severely disadvantaged.
The biggest problem with the previous implementation was that no proc required both outside research (into which sets would work) and special gearing, neither of which are really compatible with no CP, which mostly appeals to more casual players (both in the lower CP sense and in the sense where you don't need to worry about maintaining a special PvP CP loadout). Without resolving this inconsistency, no proc is a nonstarter.