Overview: Difference between revisions

Line 464:

#Switch back to your '''PvP''' or '''PvP travel''' tab before you drop out of warp, so you can see any enemies on the other side.

<br> When your ship is destroyed, a session change is initiated through you going from your ship to a pod. This can cause lag, and if you’re already spamming the Warp to 0 m button BEFORE this happens, your pod will usually warp out despite any lag that may occur (a chain of commands was built up before you got destroyed by the spamming). However, be warned that in rare cases of extreme lag you may not warp out. The session change timer is 30 seconds long and will prevent you from docking in a station or jumping through a stargate for that duration.

<br> When your ship is destroyed, a session change is initiated through you going from your ship to a pod. This can cause lag, and if you’re already spamming the Warp to 0 m button BEFORE this happens, your pod will usually warp out despite any lag that may occur (a chain of commands was built up before you got destroyed by the spamming). However, be warned that in rare cases of extreme lag you may not warp out. The session change timer is 20 seconds long and will prevent you from docking in a station or jumping through a stargate for that duration.

You can diminish lag by disabling your Mail and Notification notifications such as Blink NeoCom etc. This will reduce the delay between when you get killed and end up in your pod. Otherwise your client waits for the mail (insurance) to arrive and this might be the time they need to lock you.

@@ Line 464: / Line 464: @@
 #Switch back to your '''PvP''' or '''PvP travel''' tab before you drop out of warp, so you can see any enemies on the other side.
-<br> When your ship is destroyed, a session change is initiated through you going from your ship to a pod. This can cause lag, and if you’re already spamming the Warp to 0 m button BEFORE this happens, your pod will usually warp out despite any lag that may occur (a chain of commands was built up before you got destroyed by the spamming). However, be warned that in rare cases of extreme lag you may not warp out. The session change timer is 30 seconds long and will prevent you from docking in a station or jumping through a stargate for that duration.
+<br> When your ship is destroyed, a session change is initiated through you going from your ship to a pod. This can cause lag, and if you’re already spamming the Warp to 0 m button BEFORE this happens, your pod will usually warp out despite any lag that may occur (a chain of commands was built up before you got destroyed by the spamming). However, be warned that in rare cases of extreme lag you may not warp out. The session change timer is 20 seconds long and will prevent you from docking in a station or jumping through a stargate for that duration.
 You can diminish lag by disabling your Mail and Notification notifications such as Blink NeoCom etc. This will reduce the delay between when you get killed and end up in your pod. Otherwise your client waits for the mail (insurance) to arrive and this might be the time they need to lock you.