We disagree and I'm really not going to use more time arguing for the AOE caps removal, because it won't change a f*cking thing apparantly. You'll have to explain this, though, to me:How? Do you even know how AOE caps currently work?The main concern I would have from removing the cap is the effect on lag. If it does little to nothing to break of the Blobs (which I don't think it would), then it would mean significantly greater server load from calculating (and communicating) the addition damage/effects/targets.
Rune_Relic wrote: »We disagree and I'm really not going to use more time arguing for the AOE caps removal, because it won't change a f*cking thing apparantly. You'll have to explain this, though, to me:How? Do you even know how AOE caps currently work?The main concern I would have from removing the cap is the effect on lag. If it does little to nothing to break of the Blobs (which I don't think it would), then it would mean significantly greater server load from calculating (and communicating) the addition damage/effects/targets.
If you hit 10 people that's 10x calculations.
If you hit 100 people that's 100x calculations.
Is it really that difficult to grasp the effect AoE caps has on client updates at the server and client updates that then have to go from server to clients via the network ?
[...]
Rune_Relic wrote: »We disagree and I'm really not going to use more time arguing for the AOE caps removal, because it won't change a f*cking thing apparantly. You'll have to explain this, though, to me:How? Do you even know how AOE caps currently work?The main concern I would have from removing the cap is the effect on lag. If it does little to nothing to break of the Blobs (which I don't think it would), then it would mean significantly greater server load from calculating (and communicating) the addition damage/effects/targets.
If you hit 10 people that's 10x calculations.
If you hit 100 people that's 100x calculations.
Is it really that difficult to grasp the effect AoE caps has on client updates at the server and client updates that then have to go from server to clients via the network ?
I would suggest @Talcyndl understands the ramifications of AoE caps far better than a few on here.
You think destroying large groups is the priority in reducing lag.
Yet seem oblivious removing caps empowers them at the same time as you.
And have absolutely no regard for server performance and lag other than a wing and a prayer.
Yes small bomb groups can now damage more players.
BUT large groups can also hit many many more players for much much more damage over much much bigger area.
BUT pug groups who don't coordinate can also hit many many more people and not wipe them too.
So all your arguments about wiping large groups is irrelevant as it only works for bomb groups.
PVP is pointless with LAG. Cap removal is not a cure. Its a stab in the dark and hope for the best that works well of coordinated bombs groups and lags out everyone else.
vis-a-vis.... be a large bomb group or go home.
That's is not compatible with solo and small group play that @Wrobel is trying to encourage.
We had Lag before 1.6...no one has argued this.
Lag went to a whole other level when AoE caps were rasied to 60 from 6 because all of you cried "remove AoE caps".
You had your way once....and now scream...we need to hit even more targets with even more damage.
It failed. It was proven to fail with 1.6 and the cap rise from 6 to 60 targets.
WHY DO YOU THINK THEY LOWERED CAMPAIGN POPULATION AND BEGGED PEOPLE TO SPREAD OUT SINCE 1.6 ?
It had no effect on the ball groups and if anything the ball groups have got bigger and more numerous since...because they have been empowered rather than culled.
No.Rune_Relic wrote: »If you hit 10 people that's 10x calculations.
If you hit 100 people that's 100x calculations.
No.Rune_Relic wrote: »You think destroying large groups is the priority in reducing lag.
Yet seem oblivious removing caps empowers them at the same time as you.
N... evermind, you can't be serious.Rune_Relic wrote: »We had Lag before 1.6...no one has argued this.
Lag went to a whole other level when AoE caps were rasied to 60 from 6 because all of you cried "remove AoE caps".
You had your way once....and now scream...we need to hit even more targets with even more damage.
It failed. It was proven to fail with 1.6 and the cap rise from 6 to 60 targets.
No1 is going to say something against gap closer per se but IF you manage to get out of max range, then you SHOULD be able to disengange from your target (mostly targets).
Its called CLOSING the GAP and not, PREVENTING to BUILD a GAP.
Once you manage to get out of distance, the gap closer won't fire off. Not sure how that's an issue with or without the mini-stun.
You're not worth my time anymore sryRune_Relic wrote: »Bla bla bla
No1 is going to say something against gap closer per se but IF you manage to get out of max range, then you SHOULD be able to disengange from your target (mostly targets).
Its called CLOSING the GAP and not, PREVENTING to BUILD a GAP.
Once you manage to get out of distance, the gap closer won't fire off. Not sure how that's an issue with or without the mini-stun.
Wow, really? How about because you cant even get close to the situation of disengaging (leaving the range of a gap closer) because of the ongoing silencing?
Are you even for real man? You cant be serious...
Rune_Relic wrote: »We disagree and I'm really not going to use more time arguing for the AOE caps removal, because it won't change a f*cking thing apparantly. You'll have to explain this, though, to me:How? Do you even know how AOE caps currently work?The main concern I would have from removing the cap is the effect on lag. If it does little to nothing to break of the Blobs (which I don't think it would), then it would mean significantly greater server load from calculating (and communicating) the addition damage/effects/targets.
If you hit 10 people that's 10x calculations.
If you hit 100 people that's 100x calculations.
Is it really that difficult to grasp the effect AoE caps has on client updates at the server and client updates that then have to go from server to clients via the network ?
I would suggest @Talcyndl understands the ramifications of AoE caps far better than a few on here.
You think destroying large groups is the priority in reducing lag.
Yet seem oblivious removing caps empowers them at the same time as you.
And have absolutely no regard for server performance and lag other than a wing and a prayer.
Yes small bomb groups can now damage more players.
BUT large groups can also hit many many more players for much much more damage over much much bigger area.
BUT pug groups who don't coordinate can also hit many many more people and not wipe them too.
So all your arguments about wiping large groups is irrelevant as it only works for bomb groups.
PVP is pointless with LAG. Cap removal is not a cure. Its a stab in the dark and hope for the best that works well of coordinated bombs groups and lags out everyone else.
vis-a-vis.... be a large bomb group or go home.
That's is not compatible with solo and small group play that @Wrobel is trying to encourage.
We had Lag before 1.6...no one has argued this.
Lag went to a whole other level when AoE caps were rasied to 60 from 6 because all of you cried "remove AoE caps".
You had your way once....and now scream...we need to hit even more targets with even more damage.
It failed. It was proven to fail with 1.6 and the cap rise from 6 to 60 targets.
WHY DO YOU THINK THEY LOWERED CAMPAIGN POPULATION AND BEGGED PEOPLE TO SPREAD OUT SINCE 1.6 ?
It had no effect on the ball groups and if anything the ball groups have got bigger and more numerous since...because they have been empowered rather than culled.
If you hit 100 people stacked ontop of them with multiple AOE's without a cap..they'll all be dead...Where as right now if you hit say 60 people (the cap) with multiple AOE's...they'll probably still be alive..It takes longer to kill them..they require more AOE's to be used..Each time you hit them with that AOE..you have to do multiple passes to determine which gets hit for 100%; which gets hit for like 30% ect ect...
Basically its not the initial bomb that brings the server to its knee's..its when they're still standing in the same spot after 10 seconds of the initial bomb spamming AOE's
As for talking about Lag in a whole other level before 1.6
No..we've talked about this before
https://www.youtube.com/watch?v=jJFi1SYcaFQ
July of last year
No1 is going to say something against gap closer per se but IF you manage to get out of max range, then you SHOULD be able to disengange from your target (mostly targets).
Its called CLOSING the GAP and not, PREVENTING to BUILD a GAP.
Once you manage to get out of distance, the gap closer won't fire off. Not sure how that's an issue with or without the mini-stun.
Wow, really? How about because you cant even get close to the situation of disengaging (leaving the range of a gap closer) because of the ongoing silencing?
Are you even for real man? You cant be serious...
How is it "ongoing"? Other than ambush, all the gap closets have a minimum distance. So they can't fire off again after catching you. Just try something (like cc on them) before you bolt again. Sorry that spamming bolt is no longer a get out of jail free card.
Im just trying to get behind your thougt process...
Stop using 100 people as an example. You'll never have 100 enemies in an AOE area in this game. You'll never have more than 60 people, which is the current cap. You understand this, yes? Removal of AOE caps won't make you hit 'more people', because there will simply not be more than 60 people to hit at once, that will never happen. You understand if you hit 60 people right now, yes, where 6/24/30 people has to take calculated damage? For every AOE? Yes? With no AOE cap you'll hit all 60 people without any need for extra calculations? Yes?Rune_Relic wrote: »[
So you have 100 people all within the same healing circle (your targeted area) and you think 4 players are going to kill anyone with smart heals going off ?
Especially if your 4 strikes land over 4 ticks instead of 1 tick with the lag affecting different players latency in different ways.
I really cant believe anything anyone says if they think more players hit does not equal more server calculations and client updates to make.
Clearly they have never coded anything in their life.
Its really such a no brainer its not even worthy of discussion.
Probably why wrobel hasn't even merited the discussion with a response TBH.
Rune_Relic wrote: »Rune_Relic wrote: »We disagree and I'm really not going to use more time arguing for the AOE caps removal, because it won't change a f*cking thing apparantly. You'll have to explain this, though, to me:How? Do you even know how AOE caps currently work?The main concern I would have from removing the cap is the effect on lag. If it does little to nothing to break of the Blobs (which I don't think it would), then it would mean significantly greater server load from calculating (and communicating) the addition damage/effects/targets.
If you hit 10 people that's 10x calculations.
If you hit 100 people that's 100x calculations.
Is it really that difficult to grasp the effect AoE caps has on client updates at the server and client updates that then have to go from server to clients via the network ?
I would suggest @Talcyndl understands the ramifications of AoE caps far better than a few on here.
You think destroying large groups is the priority in reducing lag.
Yet seem oblivious removing caps empowers them at the same time as you.
And have absolutely no regard for server performance and lag other than a wing and a prayer.
Yes small bomb groups can now damage more players.
BUT large groups can also hit many many more players for much much more damage over much much bigger area.
BUT pug groups who don't coordinate can also hit many many more people and not wipe them too.
So all your arguments about wiping large groups is irrelevant as it only works for bomb groups.
PVP is pointless with LAG. Cap removal is not a cure. Its a stab in the dark and hope for the best that works well of coordinated bombs groups and lags out everyone else.
vis-a-vis.... be a large bomb group or go home.
That's is not compatible with solo and small group play that @Wrobel is trying to encourage.
We had Lag before 1.6...no one has argued this.
Lag went to a whole other level when AoE caps were rasied to 60 from 6 because all of you cried "remove AoE caps".
You had your way once....and now scream...we need to hit even more targets with even more damage.
It failed. It was proven to fail with 1.6 and the cap rise from 6 to 60 targets.
WHY DO YOU THINK THEY LOWERED CAMPAIGN POPULATION AND BEGGED PEOPLE TO SPREAD OUT SINCE 1.6 ?
It had no effect on the ball groups and if anything the ball groups have got bigger and more numerous since...because they have been empowered rather than culled.
If you hit 100 people stacked ontop of them with multiple AOE's without a cap..they'll all be dead...Where as right now if you hit say 60 people (the cap) with multiple AOE's...they'll probably still be alive..It takes longer to kill them..they require more AOE's to be used..Each time you hit them with that AOE..you have to do multiple passes to determine which gets hit for 100%; which gets hit for like 30% ect ect...
Basically its not the initial bomb that brings the server to its knee's..its when they're still standing in the same spot after 10 seconds of the initial bomb spamming AOE's
As for talking about Lag in a whole other level before 1.6
No..we've talked about this before
https://www.youtube.com/watch?v=jJFi1SYcaFQ
July of last year
So you have 100 people all within the same healing circle (your targeted area) and you think 4 players are going to kill anyone with smart heals going off ?
Especially if your 4 strikes land over 4 ticks instead of 1 tick with the lag affecting different players latency in different ways.
I really cant believe anything anyone says if they think more players hit does not equal more server calculations and client updates to make.
Clearly they have never coded anything in their life.
Its really such a no brainer its not even worthy of discussion.
Probably why wrobel hasn't even merited the discussion with a response TBH.
He is a stam Dk. So - yeah. I get that your rhoughtprocess is:
He is a stam Dk. So - yeah. I get that your rhoughtprocess is:
Well, I'm currently experimenting with him as a tanky DK, but....
I understand that a sorc would love bolt that can be cast several times without risk of interruption. I prefer having a counter - especially when it can be counter-countered (other than spammable ambush).
He is a stam Dk. So - yeah. I get that your rhoughtprocess is:
Well, I'm currently experimenting with him as a tanky DK, but....
I understand that a sorc would love bolt that can be cast several times without risk of interruption. I prefer having a counter - especially when it can be counter-countered (other than spammable ambush).
But the guy you argue with is no sorc... He is a dk
Rune_Relic wrote: »If you hit 10 people that's 10x calculations.
If you hit 100 people that's 100x calculations.
Rune_Relic wrote: »I really cant believe anything anyone says if they think more players hit does not equal more server calculations and client updates to make.
Clearly they have never coded anything in their life.
Its really such a no brainer its not even worthy of discussion.
Rune_Relic wrote: »Rune_Relic wrote: »We disagree and I'm really not going to use more time arguing for the AOE caps removal, because it won't change a f*cking thing apparantly. You'll have to explain this, though, to me:How? Do you even know how AOE caps currently work?The main concern I would have from removing the cap is the effect on lag. If it does little to nothing to break of the Blobs (which I don't think it would), then it would mean significantly greater server load from calculating (and communicating) the addition damage/effects/targets.
If you hit 10 people that's 10x calculations.
If you hit 100 people that's 100x calculations.
Is it really that difficult to grasp the effect AoE caps has on client updates at the server and client updates that then have to go from server to clients via the network ?
I would suggest @Talcyndl understands the ramifications of AoE caps far better than a few on here.
You think destroying large groups is the priority in reducing lag.
Yet seem oblivious removing caps empowers them at the same time as you.
And have absolutely no regard for server performance and lag other than a wing and a prayer.
Yes small bomb groups can now damage more players.
BUT large groups can also hit many many more players for much much more damage over much much bigger area.
BUT pug groups who don't coordinate can also hit many many more people and not wipe them too.
So all your arguments about wiping large groups is irrelevant as it only works for bomb groups.
PVP is pointless with LAG. Cap removal is not a cure. Its a stab in the dark and hope for the best that works well of coordinated bombs groups and lags out everyone else.
vis-a-vis.... be a large bomb group or go home.
That's is not compatible with solo and small group play that @Wrobel is trying to encourage.
We had Lag before 1.6...no one has argued this.
Lag went to a whole other level when AoE caps were rasied to 60 from 6 because all of you cried "remove AoE caps".
You had your way once....and now scream...we need to hit even more targets with even more damage.
It failed. It was proven to fail with 1.6 and the cap rise from 6 to 60 targets.
WHY DO YOU THINK THEY LOWERED CAMPAIGN POPULATION AND BEGGED PEOPLE TO SPREAD OUT SINCE 1.6 ?
It had no effect on the ball groups and if anything the ball groups have got bigger and more numerous since...because they have been empowered rather than culled.
If you hit 100 people stacked ontop of them with multiple AOE's without a cap..they'll all be dead...Where as right now if you hit say 60 people (the cap) with multiple AOE's...they'll probably still be alive..It takes longer to kill them..they require more AOE's to be used..Each time you hit them with that AOE..you have to do multiple passes to determine which gets hit for 100%; which gets hit for like 30% ect ect...
Basically its not the initial bomb that brings the server to its knee's..its when they're still standing in the same spot after 10 seconds of the initial bomb spamming AOE's
As for talking about Lag in a whole other level before 1.6
No..we've talked about this before
https://www.youtube.com/watch?v=jJFi1SYcaFQ
July of last year
So you have 100 people all within the same healing circle (your targeted area) and you think 4 players are going to kill anyone with smart heals going off ?
Especially if your 4 strikes land over 4 ticks instead of 1 tick with the lag affecting different players latency in different ways.
I really cant believe anything anyone says if they think more players hit does not equal more server calculations and client updates to make.
Clearly they have never coded anything in their life.
Its really such a no brainer its not even worthy of discussion.
Probably why wrobel hasn't even merited the discussion with a response TBH.
Fine. Lets cap aoes at 40 - 33.3% less than now but without any dmg dropoff??? Less cap less calculations and no dropoff calculations - yaaaaaaaaay?
The two avenues of attack we are perusing are buffing siege weapons and investigating making ranged abilities more effective at damaging large groups of players.
He is a stam Dk. So - yeah. I get that your rhoughtprocess is:
Well, I'm currently experimenting with him as a tanky DK, but....
I understand that a sorc would love bolt that can be cast several times without risk of interruption. I prefer having a counter - especially when it can be counter-countered (other than spammable ambush).
But the guy you argue with is no sorc... He is a dk
He's talking about not being able to "disengage". Which we all know, DK have never been able to disengage, mini-stun or not.
Your statement just proved you are unable to argue on the topic because it is beyond your own limitations. As a result you act like the infamous pidgeon [sic] on a chessboard.
Please dont argue on things you dont understand just for the sake of an uninformed opinion.
It was very much possible for dks to disengage...
Stop using 100 people as an example. You'll never have 100 enemies in an AOE area in this game. You'll never have more than 60 people, which is the current cap. You understand this, yes? Removal of AOE caps won't make you hit 'more people', because there will simply not be more than 60 people to hit at once, that will never happen. You understand if you hit 60 people right now, yes, where 6/24/30 people has to take calculated damage? For every AOE? Yes? With no AOE cap you'll hit all 60 people without any need for extra calculations? Yes?Rune_Relic wrote: »[
So you have 100 people all within the same healing circle (your targeted area) and you think 4 players are going to kill anyone with smart heals going off ?
Especially if your 4 strikes land over 4 ticks instead of 1 tick with the lag affecting different players latency in different ways.
I really cant believe anything anyone says if they think more players hit does not equal more server calculations and client updates to make.
Clearly they have never coded anything in their life.
Its really such a no brainer its not even worthy of discussion.
Probably why wrobel hasn't even merited the discussion with a response TBH.
Stop being such a fool
Your statement just proved you are unable to argue on the topic because it is beyond your own limitations. As a result you act like the infamous pidgeon [sic] on a chessboard.
Please dont argue on things you dont understand just for the sake of an uninformed opinion.
It was very much possible for dks to disengage...
Putting aside all the snark....
Can you explain how the current mini-stun system prevents disengagement on an "ongoing" basis? Again, are you talking about a situation with multiple attackers all stunning you?