Episode 3 is out, centered on AX variants of the Python Mk2.
And, as is forum tradition, here is the script for the video -
And, as is forum tradition, here is the script for the video -
Of the newly released ships, the only combat-oriented one is the Python Mk2.
Despite the name, it represents a significant departure from its homonymous older sibling.
The Python Mk2 is, in fact, a much closer relative to the Fer-de-Lance.
Much like the Fer-de-Lance, the Python Mk2 suffers from extremely limited optional internal compartments, and its powerful hardpoint layout is hamstrung by having “just” Class 6 power distributor and power plant. To make up for that, much like the FdL, it sports a category-leading six utility slots.
All those factors, taken together, scream a very clear design paradigm: shield tank. And that is a problem as Anti Xeno builds go, as shields are almost universally a liability in AX - they make your hitbox bigger, they don’t entirely protect you (as Thargoid weapons partially pierce shields), they force you to put pips in system, and, this latter point being generally poorly understood, they generate a lot of heat while recharging.
With the Python Mk2 you are thus presented with a tough choice. You can build it as a hull tank, much like you would for an AX Fer-de-Lance, which results in a more agile ship - but a very fragile one. Or you can build it as a shielded version, which is tankier, but has no hull repairs and forces you to contend with the issues inherent to shields.
The shielded version presents a further conundrum. It is exceptionally difficult to build a shielded variant of the Python Mk2 that can remain under 20% heat while its shields are recharging, and thus can be of practical use in TitanSpace as a Titan Bomber or Titan Fighter.
Taking all those factors into account, and with a LOT of trial and error, we came up with three AX builds for the Python Mk2, in addition to a “low engineering” build for newer CMDRs.
The TitanBomber V3.1A - which is arguably the best Titan Bomber in the game right now.
The OreoSnacker V3.1S - which is an extremely capable Orthrus hunter, intended for use at Spire sites, Alert systems, and Titan meltdowns.
The ZoneFighter V3.1Z - which is a workable build for Anti Xeno Combat Zones and solo combat, noting that the Python Mk2 still falls behind the Krait, Chieftain, and Challenger in this role.
Finally, we have a “low engineering” AX Python V3.1 U which has less restrictive requirements than the builds above.
Let’s look at each of these individual builds one by one.
With the advent of Anti-Guardian-Zone Resistance engineering, “original”, as-in, “non-modified” guardian weapons became viable for use in Titan Space. Gauss has long been known as the best such weapon against interceptors. Unlike interceptors however, a Titan’s Thermal Core doesn’t happen to have any armor resistance. Furthermore, also unlike interceptors, the Thermal Core is a stationary target. Last but not least, ammo capacity is of primary concern for Titan Bombing, as the time required to go rearm and restock in-between bombing runs is significant.
As a result, shards and, in particular, large-format shards pull ahead of gauss (and plasma for that matter) as the guardian weapon of choice for ore bombing. The Python Mk2, with its unique layout of 4 large and 2 medium hardpoints, is the best platform in the game for old guardian shard cannons.
Using premium ammunition, this ship is capable of “soloing” a Titan, that is, it is capable of doing 100% damage to the Thermal core each cycle, after having bombed each and every one of the 8 vents.
It is fair to say that it is presently the best Titan Bomber in the game.
In addition to being an exceptional core bomber, this shard-based variant excels at quickly dispatching Cyclops and Orthruses as targets of opportunity. Be warned however - original shards don’t do well against scouts, hunters, and harder interceptor variants, so make sure you steer clear of those.
Even with such evidence, this is a build surrounded by some degree of controversy. It is highly unconventional, as it sports D-rated shields and E-rated boosters, the former engineered for enhanced low power and low draw. It also makes the additional unconventional choice of using clean drives, instead of the otherwise ubiquitous dirty drives that most combat ships sport.
If your preference is to build a shieldless bomber with dirty drives, by all means, go ahead and build it that way - it will be faster but be warned, it will be very, very squishy.
For everyone else, join us in flying this shielded “stealth bomber”, that will run below 20% heat while under thrust and with shields charging!
A close relative of the Titanbomber, the Oreosnacker distinguishes itself by not having the requirement to run cold. Consequently, it is able to upgrade its powerplant to an armored variant and its shield to a biweave variant, while still rocking 5 shard cannons. The nanite torpedo, which is entirely useless outside of Titan Space, is replaced here with a beam to tag targets and to help cool down when needed.
The Oreosnacker excels at quickly dispatching Orthruses and the Cyclops they summon. But be warned, they can get overwhelmed by scouts. Having a friend tag along with multicannons or otherwise letting scouts periodically leave is advisable. Also, unlike missile boats, shard boats have no way to deal with Banshees at spire sites, so if you plan to use this build at Spires, you will need someone else to deal with the Banshees first - or, if you’re feeling bold, you can hop out in a dominator suit and handle them on foot!
Before we move on to the next build, let me take a moment to say that if you find these videos helpful, please consider liking, subscribing, and hitting the notification bell below. It really helps us notice your support!
If you wish to use the Python Mk2 at Anti Xeno Combat Zones or in solo combat, you’ll want to convert the ship to a more traditional shieldless build with military-grade armor.
At Anti Xeno Combat Zones, the Python Mk2 will be primarily limited by its Class 6 Power Distributor, which is the same as the Chieftain’s, and significantly less performing than the Krait’s Class 7.
Since a Python Mk2 would have to realistically fly with just 2 medium and 2 small gauss cannons, with worse convergence, less agility, and less tank than a chieftain, it is hard to recommend gauss for this ship.
ModShards do a bit better, with the ship’s ability to mount and use four mediums with decent convergence, while retaining two large hardpoints for utility weapons such as beams, or anything you fancy really.
In this reference build, we suggest a large beam and a cytoscrambler for the additional hardpoints, but really any weapon of your preference can work. The cytoscrambler is there because it is extremely energy-to-damage efficient, and a good complement to the very distro-hungry large beam. If you don’t have one unlocked, you can use a regular beam instead.
Finally, let’s discuss a low-engineering build option. This entry-level build uses Enhanced Anti Xeno Multicannons, available for credits at your local neighborhood’s rescue megaship, in addition to grade-3 engineering from “starter” engineers only. It won’t perform as well as the guardian-equipped variants and, honestly, if you’re going for a low-engineering build we would highly, HIGHLY recommend going with the Krait Mk2 instead. But if you must have it, and it MUST be a Python Mk2, well, here it is!
With builds out of the way, the obvious question is - how does the Python Mk2 perform in Anti Xeno Combat?
The answer is somewhat nuanced.
Given its characteristics, as we already mentioned, it is fair to say that it is presently THE best Titan Bomber in the game. No other ship is capable of “soloing” a Titan, and that in and of itself is a remarkable trait that will ensure that this ship becomes popular in the AX community.
The same characteristics make it a very decent Orthrus hunter, and I’d hazard the guess that shard-equipped Python Mk2s will increasingly be seen at spire sites, although organized groups like the Xeno Strike Force will still prefer ModPlasma Anacondas for Spires combat.
On the flipside, as a solo and combat zone fighter, the Python Mk2 does “OK”. Not great mind you, but not terrible either. It’s very, very similar to the Fer-de-Lance in this regard.
To test them out, I like to take ships for a spin in trying to do a hitless fight against a Hydra. I did manage to do it in the Python Mk2 ( you can watch the video of that fight in the link above if you’re interested), but this ship made me sweat and work for it in ways that other ships simply don’t.
The Chieftain is a LOT more agile, and the Krait Mk2 hits quite a bit harder (with its larger distro), runs naturally a lot colder, AND has over double the tanking capability. Net-net, it’s really hard to recommend this ship over either of those two for solo and AXCZ combat.
Even as TitanSpace fighters, where the large shards of the Python Mk2 are handy, the Xeno Strike Force will generally prefer to use Kraits Mk2s, as the Python Mk2s are simply too squishy.
In summary, and to use a Star Wars Universe analogy, the Python Mk2 is a little bit like the B-Wing of Elite: Dangerous. That is, the best medium bomber in the game which, in a pinch, can also handle itself as a fighter, but will fall behind A-Wings (Chieftains) and X-Wings (Kraits) in a dogfight.
And, by the way, feel free to tear into this analogy in the comments below, I’m sure you’ll have strong opinions, but, I think, you get what I mean.
With that, may the force be … I mean … Glory, To Mankind!
CMDR Mechan, over and out.
Despite the name, it represents a significant departure from its homonymous older sibling.
The Python Mk2 is, in fact, a much closer relative to the Fer-de-Lance.
Much like the Fer-de-Lance, the Python Mk2 suffers from extremely limited optional internal compartments, and its powerful hardpoint layout is hamstrung by having “just” Class 6 power distributor and power plant. To make up for that, much like the FdL, it sports a category-leading six utility slots.
All those factors, taken together, scream a very clear design paradigm: shield tank. And that is a problem as Anti Xeno builds go, as shields are almost universally a liability in AX - they make your hitbox bigger, they don’t entirely protect you (as Thargoid weapons partially pierce shields), they force you to put pips in system, and, this latter point being generally poorly understood, they generate a lot of heat while recharging.
With the Python Mk2 you are thus presented with a tough choice. You can build it as a hull tank, much like you would for an AX Fer-de-Lance, which results in a more agile ship - but a very fragile one. Or you can build it as a shielded version, which is tankier, but has no hull repairs and forces you to contend with the issues inherent to shields.
The shielded version presents a further conundrum. It is exceptionally difficult to build a shielded variant of the Python Mk2 that can remain under 20% heat while its shields are recharging, and thus can be of practical use in TitanSpace as a Titan Bomber or Titan Fighter.
Taking all those factors into account, and with a LOT of trial and error, we came up with three AX builds for the Python Mk2, in addition to a “low engineering” build for newer CMDRs.
The TitanBomber V3.1A - which is arguably the best Titan Bomber in the game right now.
The OreoSnacker V3.1S - which is an extremely capable Orthrus hunter, intended for use at Spire sites, Alert systems, and Titan meltdowns.
The ZoneFighter V3.1Z - which is a workable build for Anti Xeno Combat Zones and solo combat, noting that the Python Mk2 still falls behind the Krait, Chieftain, and Challenger in this role.
Finally, we have a “low engineering” AX Python V3.1 U which has less restrictive requirements than the builds above.
Let’s look at each of these individual builds one by one.
With the advent of Anti-Guardian-Zone Resistance engineering, “original”, as-in, “non-modified” guardian weapons became viable for use in Titan Space. Gauss has long been known as the best such weapon against interceptors. Unlike interceptors however, a Titan’s Thermal Core doesn’t happen to have any armor resistance. Furthermore, also unlike interceptors, the Thermal Core is a stationary target. Last but not least, ammo capacity is of primary concern for Titan Bombing, as the time required to go rearm and restock in-between bombing runs is significant.
As a result, shards and, in particular, large-format shards pull ahead of gauss (and plasma for that matter) as the guardian weapon of choice for ore bombing. The Python Mk2, with its unique layout of 4 large and 2 medium hardpoints, is the best platform in the game for old guardian shard cannons.
Using premium ammunition, this ship is capable of “soloing” a Titan, that is, it is capable of doing 100% damage to the Thermal core each cycle, after having bombed each and every one of the 8 vents.
It is fair to say that it is presently the best Titan Bomber in the game.
In addition to being an exceptional core bomber, this shard-based variant excels at quickly dispatching Cyclops and Orthruses as targets of opportunity. Be warned however - original shards don’t do well against scouts, hunters, and harder interceptor variants, so make sure you steer clear of those.
Even with such evidence, this is a build surrounded by some degree of controversy. It is highly unconventional, as it sports D-rated shields and E-rated boosters, the former engineered for enhanced low power and low draw. It also makes the additional unconventional choice of using clean drives, instead of the otherwise ubiquitous dirty drives that most combat ships sport.
If your preference is to build a shieldless bomber with dirty drives, by all means, go ahead and build it that way - it will be faster but be warned, it will be very, very squishy.
For everyone else, join us in flying this shielded “stealth bomber”, that will run below 20% heat while under thrust and with shields charging!
A close relative of the Titanbomber, the Oreosnacker distinguishes itself by not having the requirement to run cold. Consequently, it is able to upgrade its powerplant to an armored variant and its shield to a biweave variant, while still rocking 5 shard cannons. The nanite torpedo, which is entirely useless outside of Titan Space, is replaced here with a beam to tag targets and to help cool down when needed.
The Oreosnacker excels at quickly dispatching Orthruses and the Cyclops they summon. But be warned, they can get overwhelmed by scouts. Having a friend tag along with multicannons or otherwise letting scouts periodically leave is advisable. Also, unlike missile boats, shard boats have no way to deal with Banshees at spire sites, so if you plan to use this build at Spires, you will need someone else to deal with the Banshees first - or, if you’re feeling bold, you can hop out in a dominator suit and handle them on foot!
Before we move on to the next build, let me take a moment to say that if you find these videos helpful, please consider liking, subscribing, and hitting the notification bell below. It really helps us notice your support!
If you wish to use the Python Mk2 at Anti Xeno Combat Zones or in solo combat, you’ll want to convert the ship to a more traditional shieldless build with military-grade armor.
At Anti Xeno Combat Zones, the Python Mk2 will be primarily limited by its Class 6 Power Distributor, which is the same as the Chieftain’s, and significantly less performing than the Krait’s Class 7.
Since a Python Mk2 would have to realistically fly with just 2 medium and 2 small gauss cannons, with worse convergence, less agility, and less tank than a chieftain, it is hard to recommend gauss for this ship.
ModShards do a bit better, with the ship’s ability to mount and use four mediums with decent convergence, while retaining two large hardpoints for utility weapons such as beams, or anything you fancy really.
In this reference build, we suggest a large beam and a cytoscrambler for the additional hardpoints, but really any weapon of your preference can work. The cytoscrambler is there because it is extremely energy-to-damage efficient, and a good complement to the very distro-hungry large beam. If you don’t have one unlocked, you can use a regular beam instead.
Finally, let’s discuss a low-engineering build option. This entry-level build uses Enhanced Anti Xeno Multicannons, available for credits at your local neighborhood’s rescue megaship, in addition to grade-3 engineering from “starter” engineers only. It won’t perform as well as the guardian-equipped variants and, honestly, if you’re going for a low-engineering build we would highly, HIGHLY recommend going with the Krait Mk2 instead. But if you must have it, and it MUST be a Python Mk2, well, here it is!
With builds out of the way, the obvious question is - how does the Python Mk2 perform in Anti Xeno Combat?
The answer is somewhat nuanced.
Given its characteristics, as we already mentioned, it is fair to say that it is presently THE best Titan Bomber in the game. No other ship is capable of “soloing” a Titan, and that in and of itself is a remarkable trait that will ensure that this ship becomes popular in the AX community.
The same characteristics make it a very decent Orthrus hunter, and I’d hazard the guess that shard-equipped Python Mk2s will increasingly be seen at spire sites, although organized groups like the Xeno Strike Force will still prefer ModPlasma Anacondas for Spires combat.
On the flipside, as a solo and combat zone fighter, the Python Mk2 does “OK”. Not great mind you, but not terrible either. It’s very, very similar to the Fer-de-Lance in this regard.
To test them out, I like to take ships for a spin in trying to do a hitless fight against a Hydra. I did manage to do it in the Python Mk2 ( you can watch the video of that fight in the link above if you’re interested), but this ship made me sweat and work for it in ways that other ships simply don’t.
The Chieftain is a LOT more agile, and the Krait Mk2 hits quite a bit harder (with its larger distro), runs naturally a lot colder, AND has over double the tanking capability. Net-net, it’s really hard to recommend this ship over either of those two for solo and AXCZ combat.
Even as TitanSpace fighters, where the large shards of the Python Mk2 are handy, the Xeno Strike Force will generally prefer to use Kraits Mk2s, as the Python Mk2s are simply too squishy.
In summary, and to use a Star Wars Universe analogy, the Python Mk2 is a little bit like the B-Wing of Elite: Dangerous. That is, the best medium bomber in the game which, in a pinch, can also handle itself as a fighter, but will fall behind A-Wings (Chieftains) and X-Wings (Kraits) in a dogfight.
And, by the way, feel free to tear into this analogy in the comments below, I’m sure you’ll have strong opinions, but, I think, you get what I mean.
With that, may the force be … I mean … Glory, To Mankind!
CMDR Mechan, over and out.