Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Green Cobra
Aliastra Gallente Federation
8
|
Posted - 2017.02.20 12:27:48 -
[1] - Quote
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. I have a ticket to this with ID 381058
Best regards Green Cobra |
Cade Windstalker
843
|
Posted - 2017.02.20 15:42:03 -
[2] - Quote
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
8
|
Posted - 2017.02.20 16:31:40 -
[3] - Quote
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
844
|
Posted - 2017.02.20 17:06:24 -
[4] - Quote
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
Quaice Industries
26
|
Posted - 2017.02.21 02:27:48 -
[5] - Quote
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? |
Cade Windstalker
848
|
Posted - 2017.02.21 03:17:31 -
[6] - Quote
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
3857
|
Posted - 2017.02.21 04:59:04 -
[7] - Quote
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
848
|
Posted - 2017.02.21 14:02:22 -
[8] - Quote
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. |
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |