Forums » Suggestions
Furie mission reaction to disconnecting from server
Currently, if you have the Valent Furie mission active and are disconnected (often due to bad connection) the mission fails and you lose your 3 furies. You have to manufacture them again. I see absolutely no reason for this to be the case.
Suggestion: When the furie mission is aborted (recall isn't pressed, just the mission is aborted, either deliberately or due to DC) the furies are automatically recalled. There will still be a risk of them being killed and thus not being available next time, to prevent abuse. However, DC'ing will not make you lose all your furies.
An alternative method might be to have the mission continue across sessions, similar to manu or trade Guild missions, with the timer paused and the furies despawning after a delay, similar to player owned capships.
Suggestion: When the furie mission is aborted (recall isn't pressed, just the mission is aborted, either deliberately or due to DC) the furies are automatically recalled. There will still be a risk of them being killed and thus not being available next time, to prevent abuse. However, DC'ing will not make you lose all your furies.
An alternative method might be to have the mission continue across sessions, similar to manu or trade Guild missions, with the timer paused and the furies despawning after a delay, similar to player owned capships.
I see absolutely no reason for this to be the case.
The reason is that there are technical challenges around the cleanup of that type of NPC.
What you're asking is that the mission be re-written from scratch, and that the Furies be completely re-implemented using a different (more modern) set of NPC mechanics.
I don't disagree, but that's also a bit of an undertaking.
The reason is that there are technical challenges around the cleanup of that type of NPC.
What you're asking is that the mission be re-written from scratch, and that the Furies be completely re-implemented using a different (more modern) set of NPC mechanics.
I don't disagree, but that's also a bit of an undertaking.
Thanks for the explanation.
I understand furies are a bit of a niche use bot which you wouldn't really pay much attention to. If you ever get around to changing something in this area, please do remember the furies too.
I understand furies are a bit of a niche use bot which you wouldn't really pay much attention to. If you ever get around to changing something in this area, please do remember the furies too.
tbh it is smthing that would benefit a lot from a rewrite, u cant tell them to attack they get picked off before they even start shooting, all they do is sit and look pretty.
Also the whole going to mission tab to give commands system is kinda clunky. If you're rewriting furies at any point might also make them respond to pm commands similar to capships.
Lol, inc says it would require a rewrite and everyone has a suggestion to put in. Wasnt there a previous thread with several suggestions a long time ago? Like different varieties for different uses?
It's fine to make suggestions regarding the furies, so long as they are in discrete threads, titled in such a way that they can be searched when the devs are ready to perform said rewrite, and that it's understood that updating the furies is not high on the priority list for now.
Yeah, I'm just trying to level expectations here. For instance:
"tbh it is smthing that would benefit a lot from a rewrite"
..is true of almost everything in the game. Or at least a lot of things? I mean, we're still trying to get the Latos economy expanded to a greater portion of the galaxy.
There are always a ton of priorities, some of which are often "large and currently burning". We will take a look at the Furies when we come back around to related code, but I don't have a specific timeline on that.
"tbh it is smthing that would benefit a lot from a rewrite"
..is true of almost everything in the game. Or at least a lot of things? I mean, we're still trying to get the Latos economy expanded to a greater portion of the galaxy.
There are always a ton of priorities, some of which are often "large and currently burning". We will take a look at the Furies when we come back around to related code, but I don't have a specific timeline on that.