19:20 apparently. Personally I would prefer the bugfix was tested first, so happy to wait a bit more
You really think they tested this bug fix when they didn’t test the whole patch with weeks of time to do so? 
1 Like
Can I answer that in about 20 mins? 
1 Like
You guys Know how Change Management Works ?
Like DEV → TEST (ideally with people who know how the Game Looks inside) → PROD ?
I know that CCP does not know any of this. Vibe coding rotted their brains for good. Remember when they brought suitonia into the company as QA specialist to improve their release quality? Since then nothing has improved. Quite the contrary, CCP’s releases have become worse with every passing month.
1 Like
I expect my maruader will now max out at 1.2k km/s 
2 Likes
so because they didn’t let anyone test it aside from them, it wasn’t tested? you do know things can happen between an internal test server and main server right?
1 Like
No, not stuff like this. It’s ridiculous that THE MAIN FEATURE is messed up like that, after it was explained so boastfully. This is utter incompetence. Only naive people keep excusing this kind of poor delivery quality.
1 Like
I thought the 2 minute align time was a nice change of pace.
2 Likes
Its nailed now. Jump out one gate slow boat back and dock and my marauder no longer feels like a freighter with guns. Huzzah!
1 Like
Marauders happen to be the main feature for me as well, and it may be a way to help the newish owners wriggle out of any preexisting contract with QA. But people make mistakes sometimes. I just switched back to my battleship for a bit for some ‘retro’ playing. Dev’s and QA make mistakes sometimes, and I would prefer playing than testing new releases.
1 Like
CCP makes this kind of mistake ALL THE TIME. We players are their paying (not even free labor, we pay to test) alpha testers.
2 Likes
It looks as if some parts were definitely not tested.
For cap operation, cap transfer, ship attributes and their effects, and warp/align mechanics the internal test server works exactly the same as the main server. (The differences between the servers are in other areas)
I would put it down to probably being a combination of rushing to meet a deadline, not having enough time and not having enough people for testing … which results in some tests being skipped.
“I checked this marauder and it works fine after the changes… I have a huge list of other things to check, so I will just skip the other 4 types of marauders, because I’m sure testing 1 type means they will all be fine…” Sometimes this works… but sometimes it comes to bite a person in the behind…
Jim: “I have all long list of ships to test-jump through the ansi. Looks like I will have to work late. I will skip checking the cap transfer because I don’t have time and I think John will check it.”
John: “I still have so much to do with getting the position of these huge NIO asteroids just right near warp in. I don’t think I will have time to check the cap transfer, but I’m sure it will be fine because Jake will test it.”
Jake: “This is my 10th cup of coffee. Starting to see double, and I’m tired of jumping ships through the Ansi, so I will just leave the testing of the cap transfer to Jim. I’m sure he will fully test it.”
Unfortunately there is a lot of pressure on internal testers - companies often assign various other non-testing responsibilities to them, which take up a lot more time, and the actual testing suffers. I don’t know if FCCP is doing the same, and on top of that I would not be surprised if the testers also have to switch to testing the other FCCP projects often…
2 Likes
FCPlease (that does not roll off the tongue, btw), fix the 0-grade pyroxeres bug that prevents us from compressing it.