04-20-2017, 08:56 PM
So I recently thought of an idea how to make the way you use nanobots a bit more tactical and have a bigger reward the more you take a risk. The idea is to up the amount of hull a single nanobot repairs but reduce the number of nanobots ships have so in total each ship can repair the same amount of hull as before. The reasoning behind that is the fact you use as many nanobots needed to fully repair your hull and any excess repair is lost.
To explain it better - if you have lost 900 hull you will use 2 nanobots to repair back to full hull. This means you will use up 2x600=1200 potential repair to repair your 900 hull. This means you are losing 300 potential repairs because they were an overhead repair over the hull you needed to repair. My idea capitalizes on that loss. This means that if you keep pressing regens each time you notice you've lost a bit of hull you will be burning out a lot of potential repair power. But if you take the risk and fly possibly risking being instakilled you will use your nanobots a lot more wisely.
For instance if we up their potential by say 3 times this means a ship would repair with a single nanobot up to 1800 hull. So at worse each repair will actually waste at maximum 1799 hull which for a fighter with 12000 hull would be somewhere under 1/6th of your health. So if you decide to use nanobots if you barely lose any hull from your ship you'll burn through your nanobot supply a lot faster than if you take the risk of being prone to instakill but use them when you've lost a lot more hull.
Also just so people understand it - this means nanobot count for each ship will be reduced so the same maximal repair could be done as before. This means for instance of the Eagle:
It currently has:
66 nanobots and can repair 39600 hull with them (600 hull each bot)
It will have:
22 nanobots and can repair 39600 hull with them (1800 hull each bot)
This whole idea comes with a bit of a downside though. Ships which were prone to be easier to instakill will suffer more as you'll be in within the instakill threshold a lot more often while heavy ships will profit from this as they have a lot more overhead over the instakill threshold. Of course judging by the comments in 's other thread how people want more easier instakills not the other way around I supposed it wouldn't be all that bad.
To explain it better - if you have lost 900 hull you will use 2 nanobots to repair back to full hull. This means you will use up 2x600=1200 potential repair to repair your 900 hull. This means you are losing 300 potential repairs because they were an overhead repair over the hull you needed to repair. My idea capitalizes on that loss. This means that if you keep pressing regens each time you notice you've lost a bit of hull you will be burning out a lot of potential repair power. But if you take the risk and fly possibly risking being instakilled you will use your nanobots a lot more wisely.
For instance if we up their potential by say 3 times this means a ship would repair with a single nanobot up to 1800 hull. So at worse each repair will actually waste at maximum 1799 hull which for a fighter with 12000 hull would be somewhere under 1/6th of your health. So if you decide to use nanobots if you barely lose any hull from your ship you'll burn through your nanobot supply a lot faster than if you take the risk of being prone to instakill but use them when you've lost a lot more hull.
Also just so people understand it - this means nanobot count for each ship will be reduced so the same maximal repair could be done as before. This means for instance of the Eagle:
It currently has:
66 nanobots and can repair 39600 hull with them (600 hull each bot)
It will have:
22 nanobots and can repair 39600 hull with them (1800 hull each bot)
This whole idea comes with a bit of a downside though. Ships which were prone to be easier to instakill will suffer more as you'll be in within the instakill threshold a lot more often while heavy ships will profit from this as they have a lot more overhead over the instakill threshold. Of course judging by the comments in