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

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

Science & Industry

 
  • Topic is locked indefinitely.
 

"Removed the ‘Attack if Aggression’ option from starbase control towers."

Author
Msgerbs
Federal Navy Academy
Gallente Federation
#1 - 2012-01-26 07:26:33 UTC
How does this affect POS settings exactly? Do they now just automatically attack on aggression or what? Or does this mean they now only attack if they themselves are directly attacked, not if somebody next to them is attacked?
Jarnis McPieksu
Aliastra
Gallente Federation
#2 - 2012-01-26 08:01:48 UTC  |  Edited by: Jarnis McPieksu
Msgerbs wrote:
How does this affect POS settings exactly? Do they now just automatically attack on aggression or what? Or does this mean they now only attack if they themselves are directly attacked, not if somebody next to them is attacked?


It doesn't.

That setting was literally "Set this POS to randomly shoot people for no apparent reason. Yeah, that also includes blues".

For example, it could cause the POS to shoot you just because you remote repped someone on that grid. No sane POS manager ever set it enabled. It was bit like a noob check for POS managers - newbies would set it because it sounded important and then learn with a wreck or two ("yeah those POS guns hurt") that it was a silly setting.

If you want to set your POS to attack someone else on grid, set it to "attack if standing lower than 0.1" (modify it from 0.0 to 0.1). That way the POS shoots ayone who isn't set blue to the POS owner.

AFAIK POS always attacks whoever is shooting it, no matter the setting. You can also specifically set it to attack war targets but usually "attack if standing lower than 0.1" takes care of that bit as well.
Msgerbs
Federal Navy Academy
Gallente Federation
#3 - 2012-01-26 08:17:19 UTC
Does attacking war targets include somebody who attacks a friendly?

I used to know all this but then the alliance POS got sploded and I never bothered to think about POSes again.
Jarnis McPieksu
Aliastra
Gallente Federation
#4 - 2012-01-26 08:46:23 UTC
Msgerbs wrote:
Does attacking war targets include somebody who attacks a friendly?

I used to know all this but then the alliance POS got sploded and I never bothered to think about POSes again.


Shoot if at War = shoots at any war targets = if the guy is in a corp that is at war with the corp that owns the POS, POS shoots as soon as the target is on grid.

It doesn't matter if the guy is attacking anyone or not.
Msgerbs
Federal Navy Academy
Gallente Federation
#5 - 2012-01-26 08:50:31 UTC
What about non-war targets that are aggressed to your corp/on GCC?
Jarnis McPieksu
Aliastra
Gallente Federation
#6 - 2012-01-26 09:00:24 UTC
Msgerbs wrote:
What about non-war targets that are aggressed to your corp/on GCC?


I don't do high sec POSes so I'm not sure. If you set it to "attack if standing less than 0.1" POS should immediately fire anyone that is not set blue by the owning corp, but in high sec that might not be true to all these silly rules involving CONCORD.

Any high sec POS owners around who know how POS and neutrals/reds work in high sec?
Msgerbs
Federal Navy Academy
Gallente Federation
#7 - 2012-01-26 09:13:43 UTC
I'm not concerned with hisec, I'm concerned with lowsec/nullsec.
Jarnis McPieksu
Aliastra
Gallente Federation
#8 - 2012-01-26 09:57:32 UTC  |  Edited by: Jarnis McPieksu
Msgerbs wrote:
I'm not concerned with hisec, I'm concerned with lowsec/nullsec.


In low/null, set the tower to "attack if standing less than 0.1" and the tower will shoot everyone who is not set blue (standing 0.1 or higher) by the owner corp. Problem solved. Doesn't matter what the guy would do on the grid, showing his nose in range with standing 0.0 (=neutral) or lower and he gets blapped.

(And I've personally verified this with my alt corp towers - got plenty of killmails of people who warped to the wrong moon and found a fully armed and operational POS...Twisted )
Scrapyard Bob
EVE University
Ivy League
#9 - 2012-01-26 17:05:11 UTC
Anyone tested whether "shoot at WTs" properly includes OOC reppers who assist WTs on grid with the POS tower?

I would hope this still works...
Carniflex
StarHunt
Mordus Angels
#10 - 2012-01-27 14:24:41 UTC
Msgerbs wrote:
How does this affect POS settings exactly? Do they now just automatically attack on aggression or what? Or does this mean they now only attack if they themselves are directly attacked, not if somebody next to them is attacked?


POSes have always returned agression if agressed upon - unless you very specifically mess up with settings. What this change does is that I can no longer feel elite when my POS does not shoot blues while some nub always manages to mess up the settings thinking "attack on agression" does something that it did not really do.

"Attack on agression" was meaning that if they guy warping to POS has agression, even if the guy was blue, the POS whacks him for being a naughty guy and shootin on other people.

Here, sanity... niiiice sanity, come to daddy... okay, that's a good sanity... THWONK! GOT the bastard.

Bugsy VanHalen
Society of lost Souls
#11 - 2012-01-27 15:02:04 UTC
this basically make the POS behave like Concord in that it will shoot anyone including the owning corp if they attack someone else on grid without provocation.

if other words any aggression on grid will be countered by the POS no matter who the aggressor is. And this includes remote repping and energy transfers.

The only possible use for this is running some sort of RP diplomatic meeting using the POS as a common safe spot so nobody on grid can aggress another without being popped by the POS.

Just leave it off or you will regret it.
Jarnis McPieksu
Aliastra
Gallente Federation
#12 - 2012-01-27 15:58:45 UTC
Bugsy VanHalen wrote:

Just leave it off or you will regret it.


As of Crucible 1.1, it is not an option any more, it is always off for all towers (option is gone) - that was the point of the OP, he was unsure what that meant and if something important was taken away.

(and then answer is: "nothing of value was lost")