Your "content.xml" lacks an "id" parameter in "content" this why Vortex can't install it, also your text description also lacks a language id, if you don't want to bother with a language id just put your description in the "description" parameter of "content". Those are just best practices, tough you should really give your mod an id parameter so other mods can reference it. Best practice for "id" that are not on the steam workshop is to follow egosoft's folder naming "author_mod". If you publish your mod on the steam workshop it would also be smart to use the "id" it gives you on your mirror uploads.
Hello. Thank you very much for this very needed mod. I have a suggestion considering the issue with permanently turning the drones off and then back on.
If the issue is that the ship needs to take new damages to trigger the drones after they've been turned off, could it be possible that when turning them back on, it would slightly damage the ship? (like 1% hull or something, that's the kind of damage the crew will take care of anyway.)
I know that Kuertee wear and tear mod can damage the ship or the ship components over a set and customizable time.
I actually tried that and couldn't get it to work.
I actually had it reduce the ship to 1% hull trying to get it to work that way and nothing. So, I just did it this way. I do believe, not 100% sure, that the trigger is hidden in code not accessible to us. I think you have to actually take damage from a fight as I have noticed that sometimes when you take damage from the environment and explosions the drones do not trigger (even hitting things like an asteroid). The launch of the repair drones always seemed to me to be hit or miss.
Sitting in a ship and thinking 'Why are my repair drones not launching.' is a thing of the past with this mod, just retrigger them and they will launch if there is damage and you have drones.
The other reason I thought this is a better way is what if you're at 1% hull and want to reactivate the drones and kill yourself doing so due to taking damage.
Thanks for the comment I am happy that people might find use for the mod.
Thanks for the answer and clarification. I'll never understand why they made the repair drones behaviour so weird compared to the other drones. (not like the other drones work perfectly either, but the repair drones are definitely the biggest pain in the a$$)
17 comments
Thanks for the information.
Thank you very much for this very needed mod.
I have a suggestion considering the issue with permanently turning the drones off and then back on.
If the issue is that the ship needs to take new damages to trigger the drones after they've been turned off, could it be possible that when turning them back on, it would slightly damage the ship? (like 1% hull or something, that's the kind of damage the crew will take care of anyway.)
I know that Kuertee wear and tear mod can damage the ship or the ship components over a set and customizable time.
I actually had it reduce the ship to 1% hull trying to get it to work that way and nothing. So, I just did it this way.
I do believe, not 100% sure, that the trigger is hidden in code not accessible to us. I think you have to actually take damage from a fight as I have noticed that sometimes when you take damage from the environment and explosions the drones do not trigger (even hitting things like an asteroid). The launch of the repair drones always seemed to me to be hit or miss.
Sitting in a ship and thinking 'Why are my repair drones not launching.' is a thing of the past with this mod, just retrigger them and they will launch if there is damage and you have drones.
The other reason I thought this is a better way is what if you're at 1% hull and want to reactivate the drones and kill yourself doing so due to taking damage.
Thanks for the comment I am happy that people might find use for the mod.
I'll never understand why they made the repair drones behaviour so weird compared to the other drones.
(not like the other drones work perfectly either, but the repair drones are definitely the biggest pain in the a$$)
Let me know if you run into any issues. I have yet to have any problems related to this script.