The 100% represents the total number of production points the department can produce. Whether you decide to divide up those production points across different lines doesn't change that the department can still only produce 100% of the production points. If you want 50% on line 1 and 50% on line 2, that is still 100% of the departments work points.
- Thread starter Twistty
- Start date
The 100% is not "1 employee". It is "100% of all employee output". So if you have 3 employees and one drug at 100%, all their effort goes to that one.
0.50.2 bugfix
PC:
MAC:
ANDROID:
PC:
You must be registered to see the links
MAC:
You must be registered to see the links
ANDROID:
You must be registered to see the links
i cannot make serum ,this game is broken , I went with the lower inhibition trait ,then i made that design research ,finished that and put it into production.
i was not able to make serum so after a bit i figured maybe it had something to do with production points so i bought more supplies and the end of day screen said i had made 5 serum so i was great ,i checked in the inventory screen and still nothing ,so i then hired someone to keep buying supplies ,then end of day screen says i made 5 more but yet again there is no serum in stock.
so yeah this thing is broken ,so let's see if the new fix works if not gonna try the mod version.
i was not able to make serum so after a bit i figured maybe it had something to do with production points so i bought more supplies and the end of day screen said i had made 5 serum so i was great ,i checked in the inventory screen and still nothing ,so i then hired someone to keep buying supplies ,then end of day screen says i made 5 more but yet again there is no serum in stock.
so yeah this thing is broken ,so let's see if the new fix works if not gonna try the mod version.
I know it won't help a lot but hopefully I can get ahead of a few bug reports here
Vren stated that the 0.50.2 bugfix is not save compatible, so begin a new game. This usually happens because something was changed that is instantiated upon beginning the game and so any changes to that something either will not be reflected in a save game even if it's patched, or will cause crashes because corrected code isn't calling the same thing
Unfortunately, even though I just defended Vren in my latest post, I do have to admit that he suffers badly from a couple of flaws: he gets excited and overconfident about changes and pushes them out before they've been tested, or changes direction halfway and so has contradictory code. I haven't tested 0.50.2 yet so I can't confirm them but early reports are saying that lunch dates are broken, potentially because some code was moved but the lunch date wasn't changed to reflect it, so expect some error reports ending with the line "NameError: name 'get_random_opinion' is not defined" until a fix is posted. The bugs were posted very quickly, so it's not impossible that we'll get another official bugfix since lunch dates are pretty essential (IMO) gameplay, but who knows. I (and I'm sure others) will be testing this soon and one of us will probably post a fix. I haven't checked the code to see if all the other observed bugs in 0.50.1 have been corrected, but will be doing that this morning if someone else doesn't beat me to it
Vren stated that the 0.50.2 bugfix is not save compatible, so begin a new game. This usually happens because something was changed that is instantiated upon beginning the game and so any changes to that something either will not be reflected in a save game even if it's patched, or will cause crashes because corrected code isn't calling the same thing
Unfortunately, even though I just defended Vren in my latest post, I do have to admit that he suffers badly from a couple of flaws: he gets excited and overconfident about changes and pushes them out before they've been tested, or changes direction halfway and so has contradictory code. I haven't tested 0.50.2 yet so I can't confirm them but early reports are saying that lunch dates are broken, potentially because some code was moved but the lunch date wasn't changed to reflect it, so expect some error reports ending with the line "NameError: name 'get_random_opinion' is not defined" until a fix is posted. The bugs were posted very quickly, so it's not impossible that we'll get another official bugfix since lunch dates are pretty essential (IMO) gameplay, but who knows. I (and I'm sure others) will be testing this soon and one of us will probably post a fix. I haven't checked the code to see if all the other observed bugs in 0.50.1 have been corrected, but will be doing that this morning if someone else doesn't beat me to it
guess i'll just get the mod version then ,can't get the newest fix anyway ,it's hosted on mega which a freed download limit.
I'm curious to see your end-of-day screen. Will you get a screenshot of it and post that? A screenshot of your production management screen may help too
That was quick... well lets see when the next batch of error reports comes rolling in
I checked 0.50.3 for all the zigs I've seen posted in this thread since 0.50.1 was released and they all appear to be in except the pregnancy day zig I saw posted by Thaunatas. I haven't tested it, but it looks right so I'll repost it here for convenience
in game\game_screens\character_screens\girl_overview_ui.rpy change line 56 to
edited for great justice
in game\game_screens\character_screens\girl_overview_ui.rpy change line 56 to
Code:
text "Pregnant, " + str(day - the_person.event_triggers_dict["preg_start_date"]) + " Days" style "menu_text_style"
Last edited:
- May 3, 2017
- 1,473
- 1,802
- 264
I seriously hope you guys change your wording - all those code changes are 'hotfixes' at most. Fixing stuff is more than just changing some code on the fly - fixing code means you actually make sure that nothing else breaks too. Far too many posts and problems are a sentiment that things are mostly just hotfixed. The code owner is basically the only one that can actually fix stuff properly since he also releases.
Well, better tell the authors of the unofficial bugfix team that they need to rename their project since they are uncapable of bugfixing...
There is little difference between a "hotfix" and a "fix" except release timeframe - both are bug fixes. "Hotfixes" in the industry parlance are fixes for issues that basically make the game unplayable for a large number of people and cannot be delayed. Normal bug fixes would be something that can be delayed to the next version because it only hits a few people or there is an easy workaround or whatever. For example, lunch dates not working? Worthy of a hotfix. A tier 4 trait causes only part of its effects to happen? Not worthy of a hotfix, and goes in next release if at all.
The changes I point out are usually obviously side-effect free: Vren misspelling his own function names, misunderstanding .append return value, etc. Most of the fixes here are of that nature, so they should be quite safe - or, at worst, no less broken than before.
- May 3, 2017
- 1,473
- 1,802
- 264
I have been in the 'industry' for 3 decades now and that is not how serious development works. Might be done in quick and dirty game development companies but not in areas where there is serious code and you break stuff in complex systems. And the confused users in this thread are a sign that stuff gets hot-fixed without thought of further consequences than actually fixed.
Dude, get the stick out of you a**. This is a forum for games made by (mostly) unprofessional coders, no serious business companies.
Not going to compare credentials, but that is how I have done and seen patches done. Simple, obvious fixes get little testing beyond "Was it broke before? Yes. Is it working after? Yes. What was the bug? Typo in method name. Great, ship it." And if they are very important, they go out faster as "hotfixes" out of the normal release cycle.
- May 3, 2017
- 1,473
- 1,802
- 264
You dont get the point. THIS is the game thread - not the bugfix or a mod thread. Players come here to read and talk about the game and the minority has any relation to code. Yet they get thrown bits and pieces of code thrown at them with notions of 'things being fixed' - while they are not officially. action -> consequences. A shitload of posts of confused users is simply proof of that and those 'fixes' are just floating around afterwards with no-one taking responsibilities for them.