Review Of A 230,000,000 Python

INteresting review of a much talked about ship. I'm flying one for trading (without shields) and the costs are getting a little high. Great ship

I got the game after release so I had no access to glitches at founders world, I had the pleasure of actually earning it, and enjoyed every minute of it.

Curious why you felt you had to mention this. I've got access to the founders world, didn't use any glitches AND had the pleasure of actually earning it.
 
I am using 3xC3 fixed beams and 2xG2 gimballed MCs = no overheating issues. ;)

Yeah a full discharge from an A7 distributor will give you 100% core temp with 3 beams

I can run 5 beams on my Conda with an A8 and hit about 115% with a full discharge. No damage..
 
What I have found so far after 20 to 30 hours of combat in the Python is that it certainly requires more skill after 1.1. Skilled pilots in smaller ships now easily stick to your blind spots regardless of how much you boost and auto off. Unskilled pilots (new to the game with less than 10 hours of combat, and no use of Assist-off) still think the ship is overpowered just as they always have. Most don't realize that any ship with a skilled pilot can kill them in seconds, which is how skill based 3D sims have always been and should always be. If we dumb the game down so that all ships are the same in all aspects except 3d model, then the game will become a revolving door of new players who quickly lose interest. The skilled 3d sim players will have gone long before then.

Skilled pilots can kill an Anaconda in any ship quickly. I have done this even in a Hauler with a single beam laser (albeit, it does take 10-15 minutes). Cobra and Viper (my other two favorite combat ships) still kill Anaconda quickly after 1.1, but it takes much more skill and tact. Unskilled pilots have a hard time even attempting Anaconda kills after 1.1, and most are dead or shields off and running away within 15 to 30 seconds, regardless of ship model (Hats off to Sarah on her AI rework).

P.S. I don't run with the Mil spec armor upgrade on Python. If I get to down to armor in a fight I am running. The repair costs are just too high (can cost as much as three or four Viper base price) to even allow the shields to ever drop. Also the new AI Anaconda's seem to like ramming as much as they ever have, which is now even more damage than it was before, and sometimes the Python can be killed outright with a single instance of this, 8-9 million credits down the drain in that case.

I've never been rammed in combat since... Standard Beta I guess. Except for occasional collisions when NPCs were following the same target as I did. But never rammed by my target - hard learned lessons of Alpha - Standard Beta.

As for running when low on shields and out of the SCBs - that's the right way to do it.
 
INteresting review of a much talked about ship. I'm flying one for trading (without shields) and the costs are getting a little high. Great ship



Curious why you felt you had to mention this. I've got access to the founders world, didn't use any glitches AND had the pleasure of actually earning it.

Well some founders took a walk on the dark side bro.. not judging them because I was never presented with that choice.. I might have done the same thing.. But I do know many players think some of us are only well off financially because we glitched the game in some way... I can't speak for any other pilot but me.. and I don't want that hanging over my head with all respect.. feel me?
 
Last edited:
This thread came at the right time for me. I'm almost within distance for a Python plus outfittings and plenty for insurance and running costs but as an armed trader for now, so mostly cargo carrying. I'm taking the long way before I do any combat in it to learn how to fly this particular ship whilst I'm on a quiet trading route, practice FA off moves and such. I've flown most of the smaller ships up to a T7 so this will be my biggest investment to date and definitely won't be treating it with anything but respect. Thanks for the post, given me food for thought.
 
Last edited:
My only surprise is that the OP's setup has a smaller max jump range than my Cobby. I was thinking of slowly working up to a Python for exploring but that may make me think again.
 
IMO there's no point to running with upgraded armor. If you lose your shields, you've effectively lost. I can't imagine too many scenarios where having better armor made the difference between "winning" and "losing". Although I suppose a massive repair bill is marginally better than a full insurance re-buy.
 
My only surprise is that the OP's setup has a smaller max jump range than my Cobby. I was thinking of slowly working up to a Python for exploring but that may make me think again.

If you use Python for exploration you are going to be unpleasantly surprised with its ship integrity repair costs. Python is definitely not a ship for exploration.

IMO there's no point to running with upgraded armor. If you lose your shields, you've effectively lost. I can't imagine too many scenarios where having better armor made the difference between "winning" and "losing". Although I suppose a massive repair bill is marginally better than a full insurance re-buy.

Wrong here. When I was trying to test a Capital ship scenario in Beta 1.1 having mirrored surface composite probably have saved my ship after I was attacked by the Capital ship and about 6-10 smaller ships. Although they my hull was down to 61% I was able to get away. I would not have been that lucky with any other hull upgrade.
 
Last edited:
This is a pretty accurate review. Given your posts against the changes, I was pleasantly surprised to see you appear to agree with my take on the Python, now I've tried it. It would have been easy for you to complain that it's ruined but it seems like you've adjusted and have a balanced view of it.

+rep for an accurate and amusing read. I like that the Python has changed into a ship that demands skilled pilots. And in skilled hands it's a dangerous ship.

That said (and I've always said this), you're spot on that it costs a lot when things go wrong. I am looking forward to when FD review this (and they said they would). In the Python, it's an all-or-nothing deal. If you lose shields, you can lose several hours worth of credits extremely quickly. And this is the only aspect I dislike about the ship (and any large ship). Combat shouldn't be based on the idea that losing shields is a severe punishment, even in expensive ships, because losing shields should be a part of all combat and it's much more fun when fights sometimes go into a shield-less battle; it should cost more than smaller ships, no doubt, but not to the degree it is now (it should be a fraction of what it is now). If I do so badly in a fight that I'm reduced to less than 10% hull, I should have to pay a few hundred thousand credits, 300k tops. That would eradicate a half-hour's work but I think that's reasonable. At least then if you do lose shields but take only 10-25% hull damage, you'd get a bill for less than 70k. As it stands, going down to less than 20% hull costs over 1.5m. Losing 22% cost me over 700k the other night. It just means losing shields is a cardinal sin and it makes the whole affair much less fun and half of the fun of combat is taken away.

If FD change this so that hull damage isn't so out of whack for bigger ships, then the Python will be absolutely perfect.
 
Last edited:
Thanks for the post, given me food for thought.

Bro trust me I fought long and hard to keep the Python in play in these forums through the nerfing, the Python still isn't right in my opinion but it's what we have to work with and challenges me on every flight.

When I started I made a lot of mistakes, wasn't able to get reliable answers to my questions because everything was changing so much so fast. But when you talking about 230m.. you need to know exactly what you getting your self into.. I hope this helps
 
I sold my A-Python about 2h ago for a T9, I don't regret it. Well, I miss the old Python, not the nerfed one.
I have a A-Viper which is now a beast in the battlefield (I'm eating every Python in conflict zone) and a 500T trader which make money twice as fast as the Python. I prefer 2 ships that perform well in their role rather than 1 ship that suits no role.

I will probably grind for a Annaconda trader, and a Corvette when 1.2 comes.
 
Bro trust me I fought long and hard to keep the Python in play in these forums through the nerfing, the Python still isn't right in my opinion but it's what we have to work with and challenges me on every flight.

When I started I made a lot of mistakes, wasn't able to get reliable answers to my questions because everything was changing so much so fast. But when you talking about 230m.. you need to know exactly what you getting your self into.. I hope this helps

The trouble is at the moment there aren't any other mid-range ships before the Python. Latest news is that there will be two new ships coming with 1.2, and the Vulture on description appears to be what the Python was pre 1.1 nerfing. Then there's the FDL but we don't know exactly what role that'll be playing. What I'd hate to see is these new ships coming in and again people crying foul for their strengths, hopefully it won't happen with FD giving more ship choice in the coming months.
 
This is a pretty accurate review. Given your posts against the changes, I was pleasantly surprised to see you appear to agree with my take on the Python, now I've tried it.

+rep for an accurate and amusing read. I like that the Python has changed into a ship that demands skilled pilots. And in skilled hands it's a dangerous ship.

That said (and I've always said this), you're spot on that it costs a lot when things go wrong. I am looking forward to when FD review this (and they said they would). In the Python, it's an all-or-nothing deal. If you lose shields, you can lose several hours worth of credits extremely quickly. And this is the only aspect I dislike about the ship (and any large ship). Combat shouldn't be based on the idea that losing shields is a severe punishment. If FD change this so that hull damage isn't so out of whack for bigger ships, then the Python will be absolutely perfect.

Ydiss I wouldn't agree with you if you told me water was wet.. I don't agree with how much the Python was nerfed at all.. What you see here is an adult adapting and recovering.. making the best out of a bad situation.. that's it..

We had some really mean people exploit the powers of the Python and gave it a bad wrap.. It's got nerfed so the trolls and especially unskilled trolls couldn't do it so effectively.. that's NOT balance.. that's damage control..

We now have the same trolls moving to Anaconda's.. where does it end.. do we nerf Anaconda's for the same reason and call it balance..
 
The trouble is at the moment there aren't any other mid-range ships before the Python. Latest news is that there will be two new ships coming with 1.2, and the Vulture on description appears to be what the Python was pre 1.1 nerfing. Then there's the FDL but we don't know exactly what role that'll be playing. What I'd hate to see is these new ships coming in and again people crying foul for their strengths, hopefully it won't happen with FD giving more ship choice in the coming months.

Be warned. I'm really looking forward to the Vulture but from the stats given to us by Michael, it's definitely not going to be what the Python used to be. It'll be fast (probably faster than the Python was) and agile and I'm hoping it'll be tough as nails. But it won't have nearly the same level of fire-power and you'll need to sacrifice something to get the highest fire-power or highest durability. The power supply is size 5. It's more limited than the Viper, in terms of being able to kit it out with the best upgrades; you just won't be able to do this. The old Python let you do this, had huge fire-power and was agile and fast and was the most durable ship in the game.

I'm hoping the Vulture will be the ship I've been waiting for but anyone thinking it'll be nearly as nasty as the old Python will be very disappointed. That said, if it's agile and fast enough, the lower fire-power and limited power supply might not matter a jot.

- - - - - Additional Content Posted / Auto Merge - - - - -

Ydiss I wouldn't agree with you if you told me water was wet.. I don't agree with how much the Python was nerfed at all.. What you see here is an adult adapting and recovering.. making the best out of a bad situation.. that's it..

We had some really mean people exploit the powers of the Python and gave it a bad wrap.. It's got nerfed so the trolls and especially unskilled trolls couldn't do it so effectively.. that's NOT balance.. that's damage control..

We now have the same trolls moving to Anaconda's.. where does it end.. do we nerf Anaconda's for the same reason and call it balance..

Water isn't wet!

;)

Seriously, though. The intent of the change has been achieved. It's understandable that you're disappointed but there's no way the Python should have stayed how it was. It now needs skill to use. It's now no longer a crutch for players who had low skill but lots of time to invest in building the credits to buy it. As much as you'll never agree with me, you're confirming exactly the reasons why it was changed in the first place. It's no longer the FOM ship. And there isn't one, either. Not even the Conda.
 
Last edited:
Be warned. I'm really looking forward to the Vulture but from the stats given to us by Michael, it's definitely not going to be what the Python used to be. It'll be fast (probably faster than the Python was) and agile and I'm hoping it'll be tough as nails. But it won't have nearly the same level of fire-power and you'll need to sacrifice something to get the highest fire-power or highest durability. The power supply is size 5. It's more limited than the Viper, in terms of being able to kit it out with the best upgrades; you just won't be able to do this. The old Python let you do this, had huge fire-power and was agile and fast and was the most durable ship in the game.

I'm hoping the Vulture will be the ship I've been waiting for but anyone thinking it'll be nearly as nasty as the old Python will be very disappointed. That said, if it's agile and fast enough, the lower fire-power and limited power supply might not matter a jot.

- - - - - Additional Content Posted / Auto Merge - - - - -



Water isn't wet!

;)

As far as I understand Vulture is not going to be faster than Eagle.
 
What I can say is FD was able to see the full picture and reacted properly.. The Python wasn't the only problem with balance and they did a damned good job of making some threat room between the Python and the Viper making some room for a few new fighters..
 
Back
Top Bottom