EVE Information Portal

We've been reviewing the feedback since we released the crimewatch dev blog (all 53 pages and counting), and now have planned some revisions that I'll outline below:

Interdictor bubbles:
We've looked at the concerns about Weapons flags excessively penalising Interdictor pilots, and also about flags potentially propagating intel that is otherwise not available. With these in mind, the following alterations are planned:

The act of launching a Warp Disrupt Probe from an Interdictor will not give any flags.

If someone CURRENTLY INSIDE a dictor bubble attempts to warp then:
* Both the (failed) warper and the bubble owner will get a PVP flag
* The bubble owner will get a Weapons flag.

When someone's incoming warp is altered by a bubble at the destination, no flaggings will occur.

This should allow dictor pilots to more easily keep moving with their fleet. It also prevents free intel via flaggings when someone starts a warp to a distant bubble from the other side of the system.


NPC and PVP timers:
Firstly I want to emphasise the following will remain unchanged: If a player disconnects from the game, his ship will make an attempt to perform an emergency warp. This warp will be prevented by the regular forms of disruption as normal. The presence of any flag will not prevent this emergency warp from being attempted. There was some confusion about this, so I wanted to make sure everyone is clear this was never planned to change. If you disconnect whilst engaging NPCs, your ship will still make a single attempt to e-warp as normal at the moment of disconnect, provided you aren't tackled.

With that out of the way, here are the updated changes/clarifications:
* NPC flag timeout will be lowered to 5 minutes. NPC flags are not further extended after log-off.
* PVP flags CAN be created and further extended after log-off even if the owner did not have a PVP flag at the time of disconnect.. If Char A logs off in space (with or without a PVP flag), and then char B attacks A, then A will get a PVP flag. Char A's ship will then remain in space for as long as that PVP flag exists.
These changes should ensure that unavoidable disconnects (eg caused by network problems) aren't massively penalising, whilst ensuring that manually killing the client to avoid PVP is never a viable strategy.
* We are adding a 'Safe Log-off' ability, where you can go through the process of removing your ship from space BEFORE closing the client, rather than after. This will let you confirm that your ship is truly hidden, by getting it to a safe location and then going through a timer.
Before anyone panics about this become the new ALT-F4 to avoid combat or that we're making the game too safe, this does come with a number of restrictions. For example, the timer cannot be started whilst you have modules running, have incoming/outgoing target locks, have a Weapons/PVP flag, are in a fleet, etc. Should any of these required conditions change whilst the timer is running, it will be aborted.
We'll be putting a dev blog out with more details on this feature in the near future.

Please keep the constructive feedback coming!

For safe logoff, what effect does a gate cloak have, if any? (Cloaking isn't specifically listed as preventing the timer)

We've been reviewing the feedback since we released the crimewatch dev blog (all 53 pages and counting), and now have planned some revisions that I'll outline below:

Interdictor bubbles:
We've looked at the concerns about Weapons flags excessively penalising Interdictor pilots, and also about flags potentially propagating intel that is otherwise not available. With these in mind, the following alterations are planned:

The act of launching a Warp Disrupt Probe from an Interdictor will not give any flags.

If someone CURRENTLY INSIDE a dictor bubble attempts to warp then:
* Both the (failed) warper and the bubble owner will get a PVP flag
* The bubble owner will get a Weapons flag.

When someone's incoming warp is altered by a bubble at the destination, no flaggings will occur.

This should allow dictor pilots to more easily keep moving with their fleet. It also prevents free intel via flaggings when someone starts a warp to a distant bubble from the other side of the system.


NPC and PVP timers:
Firstly I want to emphasise the following will remain unchanged: If a player disconnects from the game, his ship will make an attempt to perform an emergency warp. This warp will be prevented by the regular forms of disruption as normal. The presence of any flag will not prevent this emergency warp from being attempted. There was some confusion about this, so I wanted to make sure everyone is clear this was never planned to change. If you disconnect whilst engaging NPCs, your ship will still make a single attempt to e-warp as normal at the moment of disconnect, provided you aren't tackled.

With that out of the way, here are the updated changes/clarifications:
* NPC flag timeout will be lowered to 5 minutes. NPC flags are not further extended after log-off.
* PVP flags CAN be created and further extended after log-off even if the owner did not have a PVP flag at the time of disconnect.. If Char A logs off in space (with or without a PVP flag), and then char B attacks A, then A will get a PVP flag. Char A's ship will then remain in space for as long as that PVP flag exists.
These changes should ensure that unavoidable disconnects (eg caused by network problems) aren't massively penalising, whilst ensuring that manually killing the client to avoid PVP is never a viable strategy.
* We are adding a 'Safe Log-off' ability, where you can go through the process of removing your ship from space BEFORE closing the client, rather than after. This will let you confirm that your ship is truly hidden, by getting it to a safe location and then going through a timer.
Before anyone panics about this become the new ALT-F4 to avoid combat or that we're making the game too safe, this does come with a number of restrictions. For example, the timer cannot be started whilst you have modules running, have incoming/outgoing target locks, have a Weapons/PVP flag, are in a fleet, are under gate cloak, etc. Should any of these required conditions change whilst the timer is running, it will be aborted.
We'll be putting a dev blog out with more details on this feature in the near future.

Please keep the constructive feedback coming!

* PVP flags CAN be created and further extended after log-off even if the owner did not have a PVP flag at the time of disconnect.. If Char A logs off in space (with or without a PVP flag), and then char B attacks A, then A will get a PVP flag. Char A's ship will then remain in space for as long as that PVP flag exists.
These changes should ensure that unavoidable disconnects (eg caused by network problems) aren't massively penalising, whilst ensuring that manually killing the client to avoid PVP is never a viable strategy.

Not being able to self destruct leads to people being stuck in wormholes and unable to leave.

* PVP flags CAN be created and further extended after log-off even if the owner did not have a PVP flag at the time of disconnect.. If Char A logs off in space (with or without a PVP flag), and then char B attacks A, then A will get a PVP flag. Char A's ship will then remain in space for as long as that PVP flag exists.
These changes should ensure that unavoidable disconnects (eg caused by network problems) aren't massively penalising, whilst ensuring that manually killing the client to avoid PVP is never a viable strategy.

Still need to solve the T3 issue.
...
However - if you are going to have this mechanic, you have to have a way to NOT be in it when it explodes. This is a play choice that adds potential. Don't bottle it up.

If you must lock the pod in the ship, get rid of the SP loss mechanic. Otherwise let people eject (again - fine if you get rid of self destruct on eject too - eject should almost always result in your enemy stealing your ship!).