Pod saving: Difference between revisions

Line 91:

== Effects of server ticks and lag ==

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 '''<font color="yellow">Warp to 0 m</font>''' button BEFORE this happens, your pod will usually warp out despite any lag that may occur, unless you "over spam" (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.

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 '''<font color="yellow">Warp to 0 m</font>''' button BEFORE this happens, your pod will usually warp out despite any lag that may occur, unless you "over spam" (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 10 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.

You can diminish lag by disabling your Mail and Notification notifications "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.

== Tactical considerations ==

@@ Line 91: / Line 91: @@
 == Effects of server ticks and lag ==
-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 '''<font color="yellow">Warp to 0 m</font>''' button BEFORE this happens, your pod will usually warp out despite any lag that may occur, unless you "over spam" (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.
+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 '''<font color="yellow">Warp to 0 m</font>''' button BEFORE this happens, your pod will usually warp out despite any lag that may occur, unless you "over spam" (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 10 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.
+You can diminish lag by disabling your Mail and Notification notifications "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.
 == Tactical considerations ==