Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

User talk:Antei thantonne: Difference between revisions

Discussion page of User:Antei thantonne
A few suggestions: new section
Line 25: Line 25:
Section 1, for final version should say purpose is to 'provide' vs. 'propose'.
Section 1, for final version should say purpose is to 'provide' vs. 'propose'.


Section 1.1, may want to drop the survey scanner from both fits and replace with more shield mods.  Since in motion across belt won't really have option to pick specific rocks much.  Just mine what's coming up since we're going to try and get all the rocks anyway.  The comment about both disadvantages of procurer being enhanced with Kronos should probably be remove, once Kronos is here it won't really mean much.
Section 1.1, may want to drop the survey scanner from both fits and replace with more shield mods.  Since in motion across belt won't really have option to pick specific rocks much.  Just mine what's coming up since we're going to try and get all the rocks anyway.  The comment about both disadvantages of procurer being enhanced with Kronos should probably be removed, once Kronos is here it won't really mean much.
 
Section 1.2, I'd take the part about using procurers as bait out completely, you never do gat back to it and I don't think it's something AMC should be doing during our own OP.  One thing to play bait with NSC/WH/LCS fleet standing by but don't think we should do this ourselves.  I'd also remove the personal references to yourself and Clutter, assuming the doctrine is to be used by others down the road may want to go generic (FC, Booster, etc.)  You have the same type of reference when talking about the bookmark containers.
 
Had an idea about the Procurer/Ore Hauler problem you mentioned.  Since the Procurers are moving they probably won't be able to reuse the same can and will need to create a new one each time.  So why not position an MTU within range of the entire belt and let it pull all the canisters to one spot for the hauler.  Don't normally want uncontrolled pulls in shared can but since cans can't be reused anyway why not.


Section 1.2, I'd take the part about using procurers as bait out completely, you never do gat back to it and I don't think it's something AMC should be doing during our own OP.  One thing to play bait with NSC/WH/LCS fleet standing by but don't think we should on ourselves.  I'd also remove the personal references to yourself and Clutter, assuming the doctrine is to be used by others down the road may want to go generic (FC, Booster, etc.)  Same type of reference when talking about bookmark containers.
Had an idea about the Procurer/Ore Hauler problem you mentioned.  Since the Procurers are moving they probably won't be able to use the same can and will need to create a new one each time.  So why not position MTP within range of entire belt and let it pull all the canisters to one spot for the hauler.  Don't normally want uncontrolled pull in shared can but since cans can't be reused anyway why not.
I think a detailed example would help here, using the graphic you have.  At what point to I warp in, what do I align to, when and to which point do I warp out.  Then do I go back thru in other direction or warp to my original point and repeat.  Not sure I completely understand the process.
I think a detailed example would help here, using the graphic you have.  At what point to I warp in, what do I align to, when and to which point do I warp out.  Then do I go back thru in other direction or warp to my original point and repeat.  Not sure I completely understand the process.