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

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

Test Server Feedback

 
  • Topic is locked indefinitely.
 

Bug with safety button? ON buckingham 20 NOV 2012

First post
Author
Soden Rah
Federal Navy Academy
Gallente Federation
#1 - 2012-11-20 20:46:11 UTC  |  Edited by: Soden Rah
I think I may have found a bug with the new criminal flagging system/safety button.

I went out to blow up some NPC's (high sec belt rats) which worked fine.
But that leaves loads of wrecks cluttering up the place, which just looks untidy.
And not having any salvage gear on board, I tried to blow the wrecks up.

Now these were my wrecks, all glowing white, and perfectly legal for me to shoot (on TQ)

However when I tried to blow them up the 'engage drones' button was red and had a skull and crossbones on it...
And totally failed to do anything.

So I set safeties to yellow rather than green and tried again... thinking that maybe CCP had made shooting wrecks,
even your own, a crime, but not a concordable offence.

I tried again...

And again the button totally failed to do anything.

So eyebrows raised, I set safetys to red/off, now expecting this action to trigger concord, and tried again...

The drones engaged, the ship exploded....

And nothing happened.

But it happened suddenly mark you...

Disappointed I lit my pipe....


So, shooting wrecks you own hasn't been made a concordable offence, Or at least if it has concord and the flagging system is broken.

However the safety button was preventing me from doing a perfectly legal action and making me think that it was a criminal act...


This seems to me like the safetys are broken somehow.

BR submitted on this.


Extra bonus points for everyone who spots the 'Goon show' quote....
CCP Frellicus
C C P
C C P Alliance
#2 - 2012-11-21 09:54:13 UTC
Yup, my bad. This has already been fixed and should find it's way soonish(tm) to the test server. The logic in the client safety level requirement bit was broken giving false results while the server was responding correctly.

Thank you for reporting the issue.