These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE General Discussion

 
  • Topic is locked indefinitely.
Previous page123
 

CCP Aggression Settings Wrong?

First post
Author
GAYNINJAS
The Filthy Few
Break-A-Wish Foundation
#41 - 2011-11-13 20:54:52 UTC  |  Edited by: GAYNINJAS
Here's another fun one.

1. Player A remote sebos/RRs player B, who's at war with player C. Since player A assisted player B, player A has inherited aggression towards all of player B's war targets and corps/players he has aggression towards.
2. Player B shoots player C, thereby receiving aggression towards player C, which is counted as new aggression.
3. Player A's remote sebo/RR/assistance modules automatically deactivate and player A receives a warning about player B's shenanigans, even though player A already has aggression towards player C, via war dec aggression inherited in step 1.

Feature working as intended...
Hwong Jian
Perkone
Caldari State
#42 - 2011-11-13 20:59:17 UTC
GAYNINJAS wrote:
Here's another fun one.

1. Player A remote sebos/RRs player B, who's at war with player C. Since player A assisted player B, player A has inherited aggression towards all of player B's war targets and corps/players he has aggression towards.
2. Player B shoots player C, thereby receiving aggression towards player C, which is counted as new aggression.
3. Player A's remote sebo/RR/assistance modules automatically deactivate and player A receives a warning about player B's shenanigans, even though player A already has aggression towards player C, via war dec aggression.

Feature working as intended...


Doesn't work that way. Player A already has aggression to Player C so no new flags are gained. Modules do not stop, pop-up happened during Step 1.

Next?
GAYNINJAS
The Filthy Few
Break-A-Wish Foundation
#43 - 2011-11-13 20:59:55 UTC  |  Edited by: GAYNINJAS
Hwong Jian wrote:
GAYNINJAS wrote:
Here's another fun one.

1. Player A remote sebos/RRs player B, who's at war with player C. Since player A assisted player B, player A has inherited aggression towards all of player B's war targets and corps/players he has aggression towards.
2. Player B shoots player C, thereby receiving aggression towards player C, which is counted as new aggression.
3. Player A's remote sebo/RR/assistance modules automatically deactivate and player A receives a warning about player B's shenanigans, even though player A already has aggression towards player C, via war dec aggression.

Feature working as intended...


Doesn't work that way. Player A already has aggression to Player C so no new flags are gained. Modules do not stop, pop-up happened during Step 1.

Next?


You're incorrect - this just happened to me. Go try it yourself before hastily replying.

What happens is that a new individual aggression flag is created when player B shoots player C. This new flag trips the new warning, and shuts the modules off.

This second flag is also seen in other instances, such as when player 1 steals a can belonging to player 2 in corp Z. When the can is stolen, player 1 gets the flag towards corp Z, but if player 1 and 2 exchange fire, player 1 will gain an individual flag towards player 2. Player 1 can then wait out the corp aggression and shoot at player 2, without the rest of corp Z interfering.


Also, the new 'shutting your modules off due to incoming aggression' pop-up only shows up once you're already assisting someone and they gain new aggression, not when you first activate your modules. In this instance (with default settings) you would get an initial warning that the person you're about to rep is at war, and that you'll gain all of their aggression. It then asks if you would still like to assist them. Once you're assisting them (and they shoot player C), you will get the new warning and your mods turn off.
MeestaPenni
Mercantile and Stuff
#44 - 2011-11-13 22:35:49 UTC
Jita Alt666 wrote:
MeestaPenni wrote:
Tippia wrote:
Rico Minali wrote:
Because you are assisting a person that all those people are at war with. Exactly how it should be, now stop crying.

It's not exactly how it should be. If he also inherited all the associated timers, it would be exactly how it should be… Twisted


I bet you're a marvelous co-worker.


Tippia would make a great District Attorney.


There's no need to be rude about it.

I am not Prencleeve Grothsmore.

Mr R4nd0m
Doomheim
#45 - 2011-11-13 22:58:05 UTC
firstly all the idiots shouting htfu, deal with it, etc etc - its boring - go get some anger management. seriously...

Now lets get my view on this straight - i know it might be hard for you to understand kiddies...

I fully support the neut assistance nerf, FULLY SUPPORT infact I think i wrote a post about stating it shouldnt be allowed a while ago. I personally think allowing neut repping/rsb is wrong, and personally i think CCP should just remove it full stop, and not even allow it. Being able to just reactivate it doesnt really matter in gangs as much as trying to dual box and do it solo (then it is a pain). I would rather see it removed altogether!! got it!??

However the mechanic exists and people will use it. What do you think people are going to do? let everyone else use it but you dont and have an unfair advantage? really?...is that what you honestly think Roll

Its like bubbles in 0.0, i think they are a lazy way to pvp, and dont get me started on drag bubbles, however even though you dont like it, you still have to emply those tactics in order to be in a level playing field...

So there you go, so lets get onto my real issue.

So lets say my mates alliance has 10 war decs. Fine. You alt rsb him, and he agresses, then someone just explain the logic to me, why would you then be aggressed TO ALL the other alliances you didnt agress..its a bit silly. they are completely separate entities.

However i can understand that perhaps if you are aiding him to some extent against another WT, you are likely to aid him against another WT he is also at war with, so basically seen as a adversary. if thats the case then thats the case. The post was basically to clear it up..However I do believe and this is my opinion, and we are entitled to it, that if i have helped against a target, i should only get agression for that war, which is fine. However thats not the case, so that is fine also. There is actually no problem either way.. just toget that straight for all the crazy posters out there.

Mr R4nd0m
Doomheim
#46 - 2011-11-13 23:06:18 UTC
GAYNINJAS wrote:
GAYNINJAS wrote:
From my initial testing, it seems that having the warning for stealing from a can turned off does this, but there has been so much inconsistency in how long it takes for this warning to kick in and stop modules (the entire time the target is still receiving RR, mind you) that I have not been able to confirm this. Can a Dev/GM confirm whether this is true?


I've done some further tests and confirmed that this is not the case - there is no way to disable this huge pain in the ass helpful warning. It would be greatly appreciated if the Devs could put in a check box allowing players to opt out of this warning, as well as the GCC RR warning, for our LS friends.


Yes just have an option like on all other boxes - dont show this again!
Personally as i said instead of making it a pain in the ass to work with, just dont allow neut assistance, it doesnt work for rsb as you still get the benefit of neut rsb before it shuts off anyway, its only for neut repping it will work. However you can still activate it afterwards anyway so whats the point in having it, its more of an inconvienience than actually stopping it.

I know its prob hard just to not allow it, has you can neut rep someone just normally, and yes you would only know your trying to neut rep when getting aggression. I dunno maybe if you try to neut rep a friend whos hitting say a WT then perhaps those mods should be disabled for 15 mins instead.
GAYNINJAS
The Filthy Few
Break-A-Wish Foundation
#47 - 2011-11-14 10:38:32 UTC
GAYNINJAS wrote:
It would be greatly appreciated if the Devs could put in a check box allowing players to opt out of this warning, as well as the GCC RR warning, for our LS friends.


Can we get a Dev to comment on whether this can/will be done? It would be greatly appreciated, and would align these warnings with all of the others received.
Trinkets friend
Sudden Buggery
Sending Thots And Players
#48 - 2011-11-14 11:18:28 UTC
here is my problem

My corp (A, for simplicity) is at war with Corp B.

One of my guys flips a can of Corp C. Corp C gets aggro versus our guy. We are running a spider-tanking gang.

Because WE are at war with corp B, we get the message for helping OUR GUY with remote reps. CONCORD deems that helping my guy while at war, means Corp A cannot spider tank Corp A while at war, and with aggression against some other random dude.

The pop-up messages resulted in the death of our guy (a punisher took 40K damage, luls) and complete operational SNAFU. This is crappy and needs an opt-out tickybox. This does nothing to actually stop neutral RR in a war dec because we are fully aware we are at war with a 5 man corp which has vowed to do skill changes from now until eternity - but when we go out to pick trouble with others, we get nerfbatted by CONCORD.

Sorry, this is crap. GAYNINJAS is right - this needs an opt-out. CONCORD be damned with this crap - this is preventing people who consciously swap aggression via RR (the whole point of can baiting) from repping their own corpies. Let alone neutral RR.

In this case, when you are at a war, you'll cop pop-ups and module cycling halts if you attack neutral RR and have your own RR running. Sorry. if the schnitzel has hit the fan, you need to be able to run your reps and cap chains if you are aware of the risk.

Further - whenever we got aggro versus ANYONE, even in lowsec, we gained a 15 minute aggro timer versus our war targets. none of them were even signed in. How does this compute? if we RRed after the fight - even after GCC's and aggro had worn off, we also got timer vs the WT's.

CCP, you have borked this up majorly. I understand WHY you did it, but your execution was just crappy.
GAYNINJAS
The Filthy Few
Break-A-Wish Foundation
#49 - 2011-11-14 11:30:51 UTC  |  Edited by: GAYNINJAS
Trinkets friend wrote:
here is my problem

My corp (A, for simplicity) is at war with Corp B.

One of my guys flips a can of Corp C. Corp C gets aggro versus our guy. We are running a spider-tanking gang.

Because WE are at war with corp B, we get the message for helping OUR GUY with remote reps. CONCORD deems that helping my guy while at war, means Corp A cannot spider tank Corp A while at war, and with aggression against some other random dude.

The pop-up messages resulted in the death of our guy (a punisher took 40K damage, luls) and complete operational SNAFU. This is crappy and needs an opt-out tickybox. This does nothing to actually stop neutral RR in a war dec because we are fully aware we are at war with a 5 man corp which has vowed to do skill changes from now until eternity - but when we go out to pick trouble with others, we get nerfbatted by CONCORD.

Sorry, this is crap. GAYNINJAS is right - this needs an opt-out. CONCORD be damned with this crap - this is preventing people who consciously swap aggression via RR (the whole point of can baiting) from repping their own corpies. Let alone neutral RR.

In this case, when you are at a war, you'll cop pop-ups and module cycling halts if you attack neutral RR and have your own RR running. Sorry. if the schnitzel has hit the fan, you need to be able to run your reps and cap chains if you are aware of the risk.

Further - whenever we got aggro versus ANYONE, even in lowsec, we gained a 15 minute aggro timer versus our war targets. none of them were even signed in. How does this compute? if we RRed after the fight - even after GCC's and aggro had worn off, we also got timer vs the WT's.

CCP, you have borked this up majorly. I understand WHY you did it, but your execution was just crappy.


Just as a quick side note - you will always gain full aggression towards all WTs when you repair someone, and this has been the case for quite a long time. For example:

1. Player A in corp 1 is at war with corp 2, and alliance Z.
2. Player B assists player A in any way (RSeBo, RR, etc).
3. Player B gains aggression towards ALL of players in corp 2 and alliance Z. In fact, player B gains aggression towards all players, corps, or alliances that can legally shoot player A (with the possible exception of kill rights - this I have not confirmed). This means anyone they have stolen from, or any and all corps/alliances they are at war with.

The rationale behind this is that you are helping someone's enemy, and therefore they should be able to stop you from continuing to do so. IMO, this makes perfect sense and should stay (as I said earlier, this has been the case for as long as I have been around, which has been about 2 years).

I'm perfectly happy with gaining aggression and having these people be able to shoot me when I assist someone - as they should be able to do so. Adding in the option to opt out of the warning still provides the safety net and the ability to be warned before committing an action that can get you killed, while allowing those people who choose to continue with those actions do so without impeding their ability to actually assist other players (concord warning is a perfect parallel to how this warning should be set up).
Jenshae Chiroptera
#50 - 2011-11-14 11:52:00 UTC
Mr R4nd0m wrote:
Not sure if this is right, if it is its silly. Or maybe its recently changed.

But i remote booster a player, the player shoots one war warget. My agression timer goes up (fair enough) but now I am aggressed to ALL the alliances/corps that player is at war with!!

Surely thats not right? how can all those alliances now be allowed to shoot me, if the player I was rsbing only shot 1 of them?


I am very happy now!

THANK YOU CCP!!!LolBig smileBig smile

CCP - Building ant hills and magnifying glasses for fat kids

Not even once

EVE is becoming shallow and puerile; it will satisfy neither the veteran nor the "WoW" type crowd in the transition.

GAYNINJAS
The Filthy Few
Break-A-Wish Foundation
#51 - 2011-11-14 11:58:45 UTC  |  Edited by: GAYNINJAS
Jenshae Chiroptera wrote:
Mr R4nd0m wrote:
Not sure if this is right, if it is its silly. Or maybe its recently changed.

But i remote booster a player, the player shoots one war warget. My agression timer goes up (fair enough) but now I am aggressed to ALL the alliances/corps that player is at war with!!

Surely thats not right? how can all those alliances now be allowed to shoot me, if the player I was rsbing only shot 1 of them?


I am very happy now!

THANK YOU CCP!!!LolBig smileBig smile


I'm not 100% sure, due to the OP being poorly written, but what I think he was complaining about was getting aggression towards all of player B's WTs when player B only has aggression timers towards one of their WTs. This has always been the case and has nothing to do with the new warning - nothing to write home about.
Tippia
Sunshine and Lollipops
#52 - 2011-11-14 12:59:08 UTC  |  Edited by: Tippia
MeestaPenni wrote:
Tippia wrote:
It's not exactly how it should be. If he also inherited all the associated timers, it would be exactly how it should be… Twisted
I bet you're a marvelous co-worker.
Indeed I am — always helping out and committing to the task at hand. So neutrals being committed to task they embark on only seems reasonable. Don't get involved in the fight if you can't commit to it.

Still, yes, an interruption opt out and/or a more intelligent flagging is needed (eg. no need to re-flag, and thus interrupt, people who are already flagged for some other reason).
GAYNINJAS
The Filthy Few
Break-A-Wish Foundation
#53 - 2011-11-14 21:53:29 UTC
Still no comments from devs regarding an opt out for the new warning?

It's my name, isn't it!? Cry
Terminal Insanity
KarmaFleet
Goonswarm Federation
#54 - 2011-11-14 21:56:04 UTC
CCP didnt clearly state the rule change.

The rule change actually effects all timers / aggression reasons, not just Criminal timers like it states.

"War declarations are never officially considered griefing and are not a bannable offense, and it has been repeatedly stated by the developers that the possibility for non-consensual PvP is an intended feature." - CCP

Jaroslav Unwanted
Brutor Tribe
Minmatar Republic
#55 - 2011-11-14 21:56:22 UTC  |  Edited by: Jaroslav Unwanted
Mr R4nd0m wrote:
Rico Minali wrote:
Working as intended and working well... War is a ***** isnt it?


How is that working as intended? How can you be agressed to EVERY other alliance and corp the OTHER player is at war with? when you have not commited or assisted in any kills towards those OTHER alliances?


Well you let yourself in. You assisted in an engagement against an corp/alliance member, you want to prevent it? Simple do not "help" or let yourself be engaged at such. Or deal with consequences.

ah sorry miss-read.

In that case its probably not such cool ..
Previous page123