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

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

Player Features and Ideas Discussion

 
  • Topic is locked indefinitely.
 

Suggestion of a minor change to autowarp on CTD
Author
Previous Topic Next Topic
Green Cobra
Aliastra
Gallente Federation
#1 - 2017-02-20 12:27:48 UTC  |  Edited by: Green Cobra
Hi

I have a suggestion of a minor change to autowarp on CTD, as the feature work now there are a few instances where ship won't autowarp off on CTD that is not related to intended game mechanics and I hope you can change at least the one bellow.

If a pilot initiate warp by a warpgate inside a mission or complex and get CTD before ship exits warp the ship will not autowarp.
Not sure if same apply to warping outside of mission or complex but this should be easy enough to test on SISI

I recently lost a Golem to this and there was no weapons timer active when this happened.

Best regards
Green Cobra
Cade Windstalker
#2 - 2017-02-20 15:42:03 UTC
That's because a ship that's been disconnected will only try to warp once, and if anything prevents that attempt it will not warp off grid until the pilot reconnects. Last I heard anything on the subject this is working as intended, and I can't imagine CCP wanting to change this too much since under the vast majority of circumstances the only result would be the server spamming itself with warp requests as the pilot's ship sits tackled by something.

In future I'd personally recommend having your tank cycling when you enter a new room of a site to alleviate issues like this.

Also note that you may want to remove the ticket information as discussing petitions is prohibited on the forums.
Green Cobra
Aliastra
Gallente Federation
#3 - 2017-02-20 16:31:40 UTC  |  Edited by: Green Cobra
It should be a relative easy fix if they want to, CCP already have a command queue system in the client and can queue a command to warp if ship already is in warp at ctd.

Best regards
Green Cobra
Cade Windstalker
#4 - 2017-02-20 17:06:24 UTC
Green Cobra wrote:
It should be a relative easy fix if they want to, CCP already have a command queue system in the client and can queue a command to warp if ship already is in warp at ctd.

Best regards
Green Cobra


Yes, it's not about whether or not it's easy to fix, it's about concerns about load on the server and the actual utility of something like this. Depending on the site you warped into it's quite possible that your Golem would have died even if the server basically spammed warp upon your landing.
Ajem Hinken
WarFear Gaming
#5 - 2017-02-21 02:27:48 UTC
Cade Windstalker wrote:
Green Cobra wrote:
It should be a relative easy fix if they want to, CCP already have a command queue system in the client and can queue a command to warp if ship already is in warp at ctd.

Best regards
Green Cobra


Yes, it's not about whether or not it's easy to fix, it's about concerns about load on the server and the actual utility of something like this. Depending on the site you warped into it's quite possible that your Golem would have died even if the server basically spammed warp upon your landing.

Why not stop the spam by just checking if you can warp first?

https://forums.eveonline.com/default.aspx?g=posts&m=6875494#post6875494 - Ship mounted explosives. Because explosions and Jita chaos.
Cade Windstalker
#6 - 2017-02-21 03:17:31 UTC
Ajem Hinken wrote:
Cade Windstalker wrote:
Green Cobra wrote:
It should be a relative easy fix if they want to, CCP already have a command queue system in the client and can queue a command to warp if ship already is in warp at ctd.

Best regards
Green Cobra


Yes, it's not about whether or not it's easy to fix, it's about concerns about load on the server and the actual utility of something like this. Depending on the site you warped into it's quite possible that your Golem would have died even if the server basically spammed warp upon your landing.

Why not stop the spam by just checking if you can warp first?


That's effectively what spamming the command does. The server would still need to process all of that multiple times rather than simply doing so once in response to client DC.
Nevyn Auscent
Broke Sauce
#7 - 2017-02-21 04:59:04 UTC
Cade Windstalker wrote:

That's effectively what spamming the command does. The server would still need to process all of that multiple times rather than simply doing so once in response to client DC.

So just tick it once a minute rather than spamming it. Still gives some chance to warp in those cases where the first warp fails (like bastion, or when already warping, or or or....)
Cade Windstalker
#8 - 2017-02-21 14:02:22 UTC
Nevyn Auscent wrote:
Cade Windstalker wrote:

That's effectively what spamming the command does. The server would still need to process all of that multiple times rather than simply doing so once in response to client DC.

So just tick it once a minute rather than spamming it. Still gives some chance to warp in those cases where the first warp fails (like bastion, or when already warping, or or or....)


Up to CCP, but I don't think this would have saved OP from his situation.