Greetings fellow Commanders !
Some of the available engineer blueprints are arguably useful. With the latest patch I think this problem is worsening more like ever before and it is due to start addressing some of the really useless ones and the way new blueprints are thrown out into elite.
For example, the reinforced or shielded prospector Limpet controllers :x[down]
I don´t think there is much to say of how useless blueprints like these are:S. If someone sees a use for these (except engineer levelling) please enlighten me. (please no [trolling?] cookie cutter Ideas). It is n1ce to have some engineer levelling blueprints, but even these should resemble a remotely useful idea.
FD I beg you to please rethink the strategy for coming up with new blueprints/content. Examples like these really shine bright as a horrific loveless and uninspired game design.
Putting out content mainly for the sake of putting out content is a bad “sign” for any game.
I acknowledge that there is more effort involved in actually programming/testing more “creative” blueprints, but in the long run, it makes for a much better game.
-----------------------------------------------------------------------------------------------------------------------------------------------------
(*rumbling* [wacky] : have to stay positive!, have to stay positive!, have to stay positive! ,....)
For not only ranting about an easy ranting-bait, here are some ideas I think are so much more engaging and fun (as more integrity):
Prospector limpet controller:
-higher limpet speed + higher range + more active limpets
-higher mining output (more fragments)
-higher material output (more materials)
-higher chance for more valuable asteroid content (if asteroid is not prospected/mined yet)
-prospector fabricates limpets and does not need stored limpets
-s.o.
Maybe new Feature:
-calling down prospector limpets from dismissed ship in orbit down on a planet to spawn mineral veins.
How about some mining-laser blueprints ? (just to stay with the mining idea)
Good Day Commanders !
/Discussion_start
Some of the available engineer blueprints are arguably useful. With the latest patch I think this problem is worsening more like ever before and it is due to start addressing some of the really useless ones and the way new blueprints are thrown out into elite.
For example, the reinforced or shielded prospector Limpet controllers :x[down]
I don´t think there is much to say of how useless blueprints like these are:S. If someone sees a use for these (except engineer levelling) please enlighten me. (please no [trolling?] cookie cutter Ideas). It is n1ce to have some engineer levelling blueprints, but even these should resemble a remotely useful idea.
FD I beg you to please rethink the strategy for coming up with new blueprints/content. Examples like these really shine bright as a horrific loveless and uninspired game design.
Putting out content mainly for the sake of putting out content is a bad “sign” for any game.
I acknowledge that there is more effort involved in actually programming/testing more “creative” blueprints, but in the long run, it makes for a much better game.
-----------------------------------------------------------------------------------------------------------------------------------------------------
(*rumbling* [wacky] : have to stay positive!, have to stay positive!, have to stay positive! ,....)
For not only ranting about an easy ranting-bait, here are some ideas I think are so much more engaging and fun (as more integrity):
Prospector limpet controller:
-higher limpet speed + higher range + more active limpets
-higher mining output (more fragments)
-higher material output (more materials)
-higher chance for more valuable asteroid content (if asteroid is not prospected/mined yet)
-prospector fabricates limpets and does not need stored limpets
-s.o.
Maybe new Feature:
-calling down prospector limpets from dismissed ship in orbit down on a planet to spawn mineral veins.
How about some mining-laser blueprints ? (just to stay with the mining idea)
Good Day Commanders !
/Discussion_start
) with 2.2