|
|
| Author |
Thread Statistics | Show CCP posts - 37 post(s) |
Steijn
Quay Industries
CAStabouts
201
   |
Posted - 2012.12.05 13:13:00 -
[1] - Quote
Could you give a timescale of when missions will be returned to normal? By this I mean that the rooms will go back to the staged aggro instead of full room which started after yesterdays patch. As it is, with the drone nerf, certain missions are simply not worth doing as its almost guaranteed suicide.
Before the moaners start, this is nothing to do with creeping into the 'aggro bubble' either manually or via warping, or via drones doing the same thing, this is a bug that was introduced yesterday. |
Steijn
Quay Industries
CAStabouts
201
|
Posted - 2012.12.07 12:47:00 -
[2] - Quote
Quote:An issue has been fixed that caused locked targets to display the 'Locked' label blinking after the lock process had been completed.
this is still happening occasionally. |
Steijn
Quay Industries
CAStabouts
201
|
Posted - 2012.12.10 20:50:00 -
[3] - Quote
not sure if this is an issue, or working as intended.
2 players in fleet, both from different corps. Player A kills mission rats. Player B tries shooting a wreck, but cant because safety is on. He then tries blowing wreck up with drone, succeeds, and gets concorded. Why? Shouldnt safety stop this? or is this meant to happen?
The loss wasnt anything, i was just trying it out in noob ships after hearing someone lost an orca because of it, and not believing how it happened. Surely when the drone was activated, shouldnt there be some kind of warning given if safety is on and the above is meant to happen? |
Steijn
Quay Industries
CAStabouts
202
|
Posted - 2012.12.12 15:51:00 -
[4] - Quote
Aethlyn wrote:Lightening Bug wrote:Assisting drones no longer works. Cannot find any reference material stating there are conditions I need to be aware of that they will not work; have tested with various offensive modules.
Test was in 0.4 security status system.
Garde II's were launched by character A and set to assist Character B. Character B launched their own drones. Character C jumped into system at gate. Character B engaged Character C with 2 warp disruptors and took sentry fire while their personal drones attacked. Character C's Garde II drones never engaged; ship had to lock and fire itself manually to enage them. All drones were confirmed on Aggressive mode with Focus Fire.
Further direct testing involved shooting an alt in newbie ship with:
Hurricane aggressing with Web and Autocannons.
Procurer agressing with Warp Disruptors and it's own drones.
Assisted drones tested includes Warrior II's and Garde II's from Dominix, and Warrior II's from Hurricane and Procurer.
Tested with and without Focus Fire on on drones.
Tested in Passive and Agressive mode on drones.
Scooped drones, docked, undocked, launched, an set assist to proper player between each test case.
In all tests, the assisting drones never aggressed.
Something's rotten in Dronemark. So you went suspect (i.e. former GCC) and Character A's drones did not assist? Maybe Character A still had his security on green, which would prevent his drones from doing anything getting him flagged?
Safety doesnt affect drones, tried, tested, and concorded  |
|
|
| |
|