TheLoneTrucker
Banned
Deleted. Think this one is best swept under the rug.
Last edited:
Patch Notes Update Powerplay Update 1.3.04 Incoming
- Thread starter Adam Woods
- Start date
- Status
I did just realize though that if a player did manage to buy a conda at the price of 3 million credits and then outfit it in all A grade everything for less than 5 million. He's got the cheapest insurance bill in the game now
Welp, if you come across a ridiculous equipped, suicidal conda, you'll know why.
The rebuy cost of one of the stock 3 million CR conda is only 183k.
oh well, lucky them.
I haven't seen this before so it must be. If it is, it's a very good addition.
Thanks Michael, it was prompt reaction from you. Good luck with all hard work, and please give us some info for things coming up beyond 1.3. Thanks!
TheLoneTrucker
Banned
lol someone ninja'd my post before i could change it.
Oh you must be kidding me... the Hull integrity repair cost went up again!!! half a mil to fix a python at 90%.. yesterday it was working fine..
for god sake...
for god sake...
Last edited:
I'd much rather they concentrated on fixing the monsoon of bugs that came with 1.3.x, seems like they've been stumbling from disaster to the next for the last couple of weeks.
TheLoneTrucker
Banned
Huh? Half a mill for at 90% so its 500k for 10%.. That's what it should be, right? The complaints before Michaels hotfix were that 1% was costing 1.4 million.
yesterday i repaired a python at 9% for 100,000 Cr
today my python at 90% and it cost 500,000 Cr
i didnt have the 4 Mil repair problem before .. now it increased ..
I'm fairly sure that the NPC ships were of different ranks but they are just not being shown as such.
I'm wondering if the fix that is applied will also have a retrospective combat ranking update applied?
i.e. When this is fixed will the corrected NPC ship ranks be applied to CMDR's combat ranking?
SOKN still is not fixed...
>.<
>.<
The majority of powerplay is still broken man, but they wont admit it as it was the only thing they had in the tank to try and placate the PC users.
Michael Brookes
Game Director
Hi Adam,
no I won't ask "Did you fix protesters in Skon?"
I always find it a bit funny, when people asking about stuff that is not listed in the change log. The logic is really simple: when it is not mentioned, it is not fixed. The bug migth get busted in a later patch, but for now it persists. This is okay, it is all understandable and I am patient.
(Edit: as additional fixes were added in the time this thread unfolds, I might be wrong and asking for missing fixes might not be as unreasonable as I thought...)
The "Skon issue", however, is time critical. The cycle will only last for two days and this bug will effectively prevent a successful take-over.
So, instead of asking "Is it fixed?", I want to ask:
"Did you already decide, how to handle the game effects of this bug?" Will Skon be counted as accomplished expansion (manually injected by FD) or will Antal lose this cycle's only expansion target?
--
By the way: I am especially grateful for this:
Thank you, FD!
We have a proper fix for this and a related issue with overlapping conflict zones being tested for another update hopefully later this week. However that will be too late to affect this week's cycle so in this instance we'll set the expansion to succeed.
Michael
An update / fix during E3? Now that's one *pleasant* surprise for a change. Credit where credit is due, thanks, good stuff!
Thanks for clarification on this particular issue.
I surely do hope these issues get fixed,
as they have a huge impact on small powers.
I've been opposing that expansion all week!
- Status