[Dev Team] stellaris_test beta branch updated to 2.2.3 with many new fixes [checksum 1960]
- Thread starter Jamor
- Start date
-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
This just happened to me today as well. I didn't note the date though. When I wake up I'll check the year.
Built a ministry of culture and it boosted my unity output for a moment but I had no visual of the building just an empty slot where it should have been.
I noticed I had three unemployed for that moment which went to five once the unity boost vanished.
Supposedly two of them were doing culture work for a moment but I didn't see the jobs.
The five unemployed make sense as they were working as doctors until I replaced the cyto-revitalization facility.
I found a post about this under r/Stellaris as ministry_of_culture_is_bugged_vanishes_upon.
I'm pretty sure the game I'm playing started in 2.2.3 and is not from an earlier build but I could be wrong.
Is this being worked on? If it is fixed how do I benefit?
I'm rather afraid it does work like that. You don't get to ignore the most serious problems with your work and just focus on the easy stuff. I don't like to get all In the World of Work on people, but... yeah. I can't ever imagine a situation where a client was saying "half my people have this huge problem" and anyone's going to be ok with me saying "can't reproduce, I'll work on something else instead".
Anyway, no reason at all to think they can't replicate the problem. The certainly would have said something by now if they couldn't.
As far as I know, Ministry of Culture is bugged in 2.2.3 still. The problem is believed to be that something went horribly wrong with converting it from a planetary unique building to an empire unique building. Not only does it vanish on completion, but the Artisan Troupe will cheerfully sell you more unbuildable Ministries of Culture afterwards.
Unfortunate. I'll have to avoid buying a ministry of culture for a while.
Is there a post where they acknowledge it is busted and/or affirm a fix is in progress?
My stellaris beta_test version 2.2.3 just stopped working completely! Crashes as soon as the loading screen is supposed to pop up from the launcher. I've tried doing as it suggests (Clearing some files from the userdata), removed all mods and ran an integrity test. Nothing seems to work...
What people want:
"Hey boss, I have a 1-liner fix for disappearing ministries, it took me 5 minutes. And here is another 1-liner for the missing robot uprising flag. Can I merge them to the test branch?"
"Absolutely not! It is completely unacceptable to make any improvement before we rewrite the AI from scratch, redesign the sectors system, and reinvent the trade routes, because ..." and here is where my imagination hits the wall. What could it possibly be? Does anyone have any realistic guesses?
- New content is released when it's done, and not one day sooner.
- Patches are released ASAP. As long as they fix one small bug, they are worth releasing, at least to the test branch.
- The exact opposite.
"Hey boss, I have a 1-liner fix for disappearing ministries, it took me 5 minutes. And here is another 1-liner for the missing robot uprising flag. Can I merge them to the test branch?"
"Absolutely not! It is completely unacceptable to make any improvement before we rewrite the AI from scratch, redesign the sectors system, and reinvent the trade routes, because ..." and here is where my imagination hits the wall. What could it possibly be? Does anyone have any realistic guesses?
I am guessing Applebeam, that fixing the problems without causing other things to break is being challenging to them. I do not understanding anything about coding but from what I have read and heard a lot of the major issues are going to be pretty difficult and a bit time consuming to fix.
Trust me, i am anxious to get back to playing it and some of my many abandoned save games, but the last thing I want is to get all excited and worked up to get going when they release a patch only to find out other things were now broken that worked before.
Trust me, i am anxious to get back to playing it and some of my many abandoned save games, but the last thing I want is to get all excited and worked up to get going when they release a patch only to find out other things were now broken that worked before.
Not how software development works, especially when multiple people work on a project. A developer is assigned or works on a bug/feature, and they work on a branch of the current codebase (in this case, the test branch or most likely a development clone of the test branch). They fix the bug or complete the feature, and push their changes to a new branch that contains only the changes they made.
At that point other developers can review their changes to make sure they don't see any glaring issues and agree with their changes or suggest edits. THEN they agree it can be merged, and then that merge is usually done by someone else entirely. After several of these cycles of merges, then the cloned development branch is merged back into the base (test branch in this case).
You have an over-complicated vision of a project maintained by ~3 programmers.
Best-case realistic scenario for us (also, slowest): git checkout -b ministry_fix, tap-tap-tap, git add ..., git commit -m "Fixed the ministry bug introduced in 2.2.3", clickity-click, and you have a pull request for another dev to check and approve, then close the ticket. Takes 5 minutes, unless your colleague went to grab some Chinese food for lunch.
Realistic scenario, considering the size of the team and what we saw so far, most likely omits the code review phase and/or pull requests altogether (git pull --rebase, git push, and done).
Any more complicated and enterprise-ish ritual would not explain how we ended up where we are.
I know the bug's been reported in the Bug Reports forum, and someone with more patience than I found the probable culprit, an error in the script file that amounts to "If you don't have Ministry of Culture, you're allowed to build one; but if you build a Ministry of Culture, you're not allowed to have one." Some dev may have been under- or over-caffeinated when they coded that....
@Jamor or whomever it may concern:
While its of course a lower priority than the bug fixes (because its moreso a balance issue), but could you guys please consider taking a look at Strike Craft? As it stands, Strike Craft are so underperforming in practice that they are not worth using, which is really a pity. Things like launching them earlier (at greater engagement range), increasing their speed, tightening their turning radius, adjusting the weapon timing (and damage correpsondingly) so their cooldowns better align with periods where they're actually in position to attack again, etc, would be things to consider.
EDIT: As an addendum, if I remember correctly, there was an update back in the earlier versions of the game (1.9 if I recall right) in which Strike Craft were actually fairly good. I might recommend you take a look with how you handled Strike Craft back then; it might be a good source of inspiration to help fix them.
While its of course a lower priority than the bug fixes (because its moreso a balance issue), but could you guys please consider taking a look at Strike Craft? As it stands, Strike Craft are so underperforming in practice that they are not worth using, which is really a pity. Things like launching them earlier (at greater engagement range), increasing their speed, tightening their turning radius, adjusting the weapon timing (and damage correpsondingly) so their cooldowns better align with periods where they're actually in position to attack again, etc, would be things to consider.
EDIT: As an addendum, if I remember correctly, there was an update back in the earlier versions of the game (1.9 if I recall right) in which Strike Craft were actually fairly good. I might recommend you take a look with how you handled Strike Craft back then; it might be a good source of inspiration to help fix them.
Last edited:
The whole subterrenean civ chain is adapted horribly. There is no way to actually research both choices if you get the event early game. Both establish contact and preemptive strike special project costs 5000 society and engineering research, and both are timed for 360 days. With default 2 researchers it takes like 130 months to research both.
Thankfully if you do nothing, u get 1 event saying that they are emerging and attacking colonists, but than there is nothing happaning after, so event chain bad outcome seems broken too
It would be nice if a beta patch could be issued, even if there are still fixes left to go, so that which is now working in the dev build can go out and reduce the number of remaining issues present in the test_branch, even if not eliminating them fully. That would enable what improvements that are ready to provide relief now, and new improvements could be added in a 2nd wave.
Of course, this is a suggestion only, but one I think is worth considering.
Of course, this is a suggestion only, but one I think is worth considering.
- NEW PATCHES is released when it's done, and not one day sooner.
- NEW CONTENTS are released ASAP
-Ppl want a fine, complete patch.
-Ppl pray for that patch come out ASAP.
Better happy waiting for a complete patch.
