General Python MkII Feedback

For bounty-hunting and space conflicts, the Python 2 is placed very nicely between the Krait 2 and the Mamba for pilot experience and efficacy:
  • The Krait 2 remains one of the best options for easing into that combat role, given the credits to do it of course! It has a borderline heavy loadout and a such large class 7 power and distributor that one can try any weapons and worry not much about managing them, and plenty of room for mistake-mitigating modules.
  • The Python 2 offers an incredible amount of firepower, honestly in competition with the Anaconda, in return for learning to work within its limits. It retains its ease of flight, but must be designed well to remain within class 6 power, and distributor must be managed. In part its fewer optional modules have transferred over into Utility modules for Shield boosters, and generally should be an option for Commanders who can fly a Krait 2 well enough not to need various safety options.
  • The Mamba remains above that in the context of kills per time, but now needs good ship design, very fast power management, targeting of modules, gear-boosting and relentless Flight assist toggling.
The Fer-de-Lance also remains beside those as an excellent duelist option—the difference with bounty-hunting and space conflicts being that evasive flight is not the goal, and generally detrimental for kills per time!

For various anti-xeno activities:
  • The Python 2 became instantly the best Titan attack vessel! Prior to that I regarded the Imperial Cutter best, for its amount of missiles was well worth being able to freeze only around half the vents, whereas the Python 2 can manage a full circuit and can bring more class 3 weapons. Keeping the ship design within class 6 Power with Low Emissions is a good challenge.
  • It is decent for Interceptor duels, although its agility works less well at higher speeds than with options such as the Alliance Chieftain. With the appropriate weapons being class 2, if one already accepts the lack of optional modules then it may be as well to use a Fer-de-Lance instead.
  • That said, it is good generally for a shielded solo AX conflict if one builds it to support the system forces. Azimuth Multi-cannons are good, and I like to bring at least one Azimuth Plasma charger to help conserve Multi-cannon ammunition.
Generally the Python 2 presents a good position between other options, both versus Humans and versus Thargoids—the big exception is being the best for Titans, although even that would be described poorly as combat and more appropriately as a unique activity which happens to involve weapons!


Maybe the SCO is a godsend for AX players.

This is emphatically true regardless of vessel!
 
Somehow I feel that we players are short-changed by FD again. How it is possible to go from 38 (MKII35+Python41):2 to 17 PMKII in index for Optional

The lost space is taken up by the beefier chassis.
Beefier chassis, and don't forget: PII is much slimmer than Python MKI or Krait. A lot of the internal space is taken up by the three dorsal hardpoints, there isn't much room left.

Honestly, lack of internals is not a problem for missions that doesn't involve bulk cargo. You can have 2400 MJ of prismatic and plenty of internals for whatever utilities you need for a mission at hand. Or you can trade 6A shield for 4A, still have good shields and 64 tons of cargo for eg mass black box salvage, cargo liberation or whatever. Basically, when it comes to mission payload it's comparable to a Cobra or Chieftain, but much more firepower and shielding than either of those.
I find this a balanced decision that keeps earlier ships relevant, but at the same time, it leaves the PMKII without much purpose. It seems to be a specialized ganking tool
Every ship can become a specialized ganking tool in the right hands😉 PII shines for PvE combat, you can literally do no-hits-taken pirate lord assassinations and kill the 'Vette in 10 seconds; it absolutely shreds CZ-s and High RES-s. Supercruise maneuverability is great, it's fast, it has way better jumprange compared to FDL and Mamba (mine does 26 ly in full combat fit and 33 ly sans SCB-s which are replaced for fuel scoop and FSD booster when travelling), it makes a great HGE harvester, though T8 may be somewhat better due to universal limpet controller, it's great for Odyssey missions (two Advanced Missile Racks for air-to-ground and still plenty of firepower left for ship-to-ship combat). I haven't found a mission outside of bulk cargo yet that made me switch the PII for something else, I just swap a few modules and can do it.
 
PII is much slimmer than Python MKI or Krait where did you find it?

PMKII dimension: 88.4x67.5x17.3, it seats right in between MKII 73.3x72X13.5 and Python 87.9x58.1x18. Its space is completely wasted and it does not have fuel tank to support SCO. I guess its designers and engineers live in the system which does not discover meta alloys yet so they filled all optional space with iron pellets. I hoped it would be a proper medium ship which could take down Hydra solo in AX zone in space but it does not. I am very disappointed it does not fit for heavy thargoid engagement except bombing titans.
 
Last edited:
PII is much slimmer than Python MKI or Krait where did you find it?
By looking at the ship in game. There's a narrow thicker central section, but most of the ship is quite thin "wings". The height number comes from two vertical fins at the back, which add something like 2 meters. Just compare the rear aspects of PII and Python MKI—one is a pancake, the other looks like a house. Krait is a relative pancake, too, but has quite significant volume due to the broad central "bulge" below the flat top.
PMKII dimension: 88.4x67.5x17.3, it seats right in between MKII 73.3x72X13.5 and Python 87.9x58.1x18.
What do you mean by "MKII"? Cobra MKII? Krait MKII? Assuming the latter, there seems to be an error in the dimensions given in game. Krait MKII: 13.5 m; Krait Phantom: 14.6 m. Doesn't sound right to me, Phantom is certainly not thicker than Krait II. Both are also wider than PII and don't have any fins protruding from the top.
Its space is completely wasted
Oh, boy, you should take a look at Orca🤪
 
Howdy Devs, It is possible to get 1 class 1 option internal added to the Python MKII? I know it is a combat ship but I like it for Exploration and having that slot means I can put the Pre-Eng DSS in the class one slot and have room left for a SRV.
 
I know it is a combat ship but I like it for Exploration and having that slot means I can put the Pre-Eng DSS in the class one slot and have room left for a SRV.

As with combat loadouts, you will always have to sacrifice something! It could be worth taking a look at how you have outfitted for exploration thus far, if you are willing to share it via ED Shipyard or Coriolis.

Setting aside the optional module classes, for exploration the Python 2 is a little short in total—a fully self-sufficient explorer must have:
  • Fuel scoop
  • Vehicle hangar
  • Surface scanner
  • AFMU
  • Repair controller, and cargo space for limpets
That alone occupies all six optional modules, so any conveniences such as a Shield generator, Guardian FSD boost or Supercruise assist must come at the expense of being self-sufficient or of being an explorer. There could be a case for changing the repair and limpets for a shield and FSD boost, given that hull damage only occurs accidentally—then again, Supercruise assist can help prevent accidents such as an emergency drop into a star.

Extra class 1 module space can not be added without making it absurdly good for combat, though! An explorer sees it as space to bring a Surface scanner, whereas to a combat pilot it means an extra layer of module or hull protection which increases the absorption or resistance respectively—aspects which the Python 2 trades away in return for Utility modules and their presumable use for Shield boosts.
 
Last edited:
Boy lots of helpful people. I do know about expo. You don't need an AMFU unless you are going to ride the Neutron Highway. You don't need Repair Controller with cargo space with limpets. FC's everywhere to repair or do our own FC base Expo. Scoop, Shields are landing cushions, PreEng DSS, Prefer SRV since I hit Elite V in Exo, Expo, and Trade. Did Exo in a Hauler with no SRV. Just looking to enhance the fun and work within my physical needs.
 
Boy lots of helpful people. I do know about expo. You don't need an AMFU unless you are going to ride the Neutron Highway. You don't need Repair Controller with cargo space with limpets. FC's everywhere to repair or do our own FC base Expo.
That's true. Hence that's what I'd fit my PII out with for exploration:
The extra fuel tank (or SRV hangar) could be replaced with an AFMU for neutron boosting.
 
You don't need an AMFU unless you are going to ride the Neutron Highway. You don't need Repair Controller with cargo space with limpets. FC's everywhere to repair or do our own FC base Expo.

Your intended level of self-sufficiency is an important part of the starship design! Without knowing now that you are happy to seek a DSSA carrier, the reason for adding hull and module repairs is only due to supposing you may be entirely alone and may prefer that a limited number of mistakes does not end the expedition.

With repairs not required, definitely that eases the module burden—you have a good-looking option above which could do what you need, otherwise definitely list which modules you want to bring and why they do not fit the available slots!
 
PMKII has to be redesigned or to have 2 options with SCO harness or without, or option to engineer harness to light modification with regaining of OU space.
 
Back
Top Bottom