Some feedback on Multi-Limpet Controllers

Brrokk

Brrokk
After testing, I give you: the "it can mine anything very fast" Python.
I've decided the best use of the MLC is just to give 2 more limpets than a 3A collector; I still have a separate prospector controller as it simplifies fire groups and limpet admin.
10 collector limpets are great to watch. :p

EDSY

EDSY is a ship outfitting tool for Elite Dangerous
edsy.org edsy.org
 

Kynami

K
While the mass is far more useful for small ships I still have to say that the mining MLC is something of a bad deal. The only thing people will use it for is collectors as it stands because the E is completely useless and the C is bad at prospecting without screwing up collector usage. To say nothing of how laser mining wants grade A prospectors for max fragment count.
 

Brrokk

Brrokk
Kynami said:
While the mass is far more useful for small ships I still have to say that the mining MLC is something of a bad deal. The only thing people will use it for is collectors as it stands because the E is completely useless and the C is bad at prospecting without screwing up collector usage. To say nothing of how laser mining wants grade A prospectors for max fragment count.
Click to expand...
I think this is actually a bad feature of the implementation. For limpet admin reasons, it's always going to be most straightforward to use the MLCs as single-type controllers.
 

Darth Ender

D
it's a shame you can't prioritize the retirement of limpet types when spawning a new limpet. same way you prioritize power subsystems.

that way if you have room to spawn it's fine. but the moment you max ...if you have say prospector at a lower priority than collector, then the new limpet kills the prospector to spawn.

this would solve the mining issue entirely (and any other situations where you are spawning a mix of limpets).

Allowing you to kill the previous prospectors to launch new ones.
 

sandkid

S
Darth Ender said:
it's a shame you can't prioritize the retirement of limpet types when spawning a new limpet. same way you prioritize power subsystems.

that way if you have room to spawn it's fine. but the moment you max ...if you have say prospector at a lower priority than collector, then the new limpet kills the prospector to spawn.

this would solve the mining issue entirely (and any other situations where you are spawning a mix of limpets).

Allowing you to kill the previous prospectors to launch new ones.
Click to expand...
I would think the solution to this, especially with multi-limpet controllers, is not a prioritization but just a redundancy.

If I ask to launch a collector, replace a collector.
If I ask to launch a prospector, replace a prospector.

Now, in the cases of where I have too many of one limpet and I need a different type...

I should be able to target a limpet via nav - like the unecessary prospector a few km away - and terminate it. Just like abandoning the detonation for core mining.
Ta-da. Limpet management kept separate from the controller itself and, theoretically, proving easier to code. I am, of course, not a developer.

Alternatively, when an asteroid is depleted it should prompt the prospector to automatically detonate. That would solve 70% or more of the problem right off the bat.
 

cmdr chequers

cmdr chequers
Brrokk said:
After testing, I give you: the "it can mine anything very fast" Python.
I've decided the best use of the MLC is just to give 2 more limpets than a 3A collector; I still have a separate prospector controller as it simplifies fire groups and limpet admin.
10 collector limpets are great to watch. :p

EDSY

EDSY is a ship outfitting tool for Elite Dangerous
edsy.org edsy.org
Click to expand...
That hurts my eyes, please use coriolis
 
You must log in or register to reply here.
Back
Top Bottom