oramagugl.blogg.se

Python oolite
Python oolite






python oolite

33% to base shield strength is a minor change. It might mean a ship gets released that doesn't seem to fit the current trend, or relies on game play that hasn't made it in yet so it's a bit weaker but if I tried to counter those things I'd only have to take them away later and that doesn't go down well )Īnyway I don't recall ever saying exactly what I was going to do to address the fact that the python is way better than I intended it to be so chill out, step back and think rationally for a second. I'd have to constantly adjust each ship in the whole game to take into account a new ship each and every time if I hadn't tried to look at the big picture first. It makes no sense to set up a ship the moment before release based on what's only in the public build when I know in advance or already have access to all the other ships that will also be released soon. Of course I'm balancing ships based on what I have access too right now. It might be a sitting duck if you fit it with the smallest and crappiest thruster module you can get away with but it would have been that way before as well. I'd be surprised if it was noticeable even now. Anything less and the change wouldn't even be noticeable. The python still has one of the best hard point placements when it can get its guns to bare on a target and it won't become a sitting duck either.ġ7% is small. This puts the flight model in a better place for a large fighting based ship and also leaves room for the other fighting ships to come so they can be more manoeuvrable than it. The changes to the python is something like -17% to speeds, turn rates and accelerations, -33% to base shield strength roughly.








Python oolite