Sheepy Cloud
Active Member
- Apr 22, 2020
- 583
- 408
- 265
- Thread starter Twistty
- Start date
If it is something that you can reproduce, or you have a save file that hits it, feel free to post it.
Sheepy Cloud
Active Member
- Apr 22, 2020
- 583
- 408
- 265
You can probably reproduce it by setting your Sex_Skill > (Insert Anal/Vaginal/Foreplay/Oral here) to 10-100K.
Yes, but setting the skill to an invalid number like 10k is not a "bug". It is "unsupported behavior". Admittedly the code could be much better (like why he wrote it as recursive and no bounds checking, I do not know), but as long as you stay from 0-8 it would be fine.
Damn, sorry about that, pointed to the wrong file. That's in game/game_roles/_role_definitions.rpy, should be around line 28 in that file (but since I've modified the files in various ways the line-number might be slightly off).
Corrected my original post and also made a minor edit to the last change, since I noticed the indentation of the code (which is rather important in python) was ruined unless i specifically put it into a "code"-block.
Last edited:
Great game, only request idea, add some bdsm elements or sex toys would be awesome especially since there is a sex tou store.
Sheepy Cloud
Active Member
- Apr 22, 2020
- 583
- 408
- 265
I typically set skill/stat values to 1-100K, depending on what I'm looking to do during that update (Like Nora serum traits, but just brute-forcing the research).
Sex skills can be 100 without issue though, and probably up to 1K.
Now after all of this fixing, I get this error :
Any ideas? I've been looking around but, yeah, I prefer the expert looking over it himself lmao
You don't have permission to view the spoiler content.
Log in or register now.
Satalin
Newbie
- Jul 24, 2017
- 53
- 31
- 267
hmm the code want purchase a policy but i don`t know if you have it allready or not when you have it then it maybe cause that error and then there must be an option to check if you allready have it and then ignore that you bypass that. if you not have that policy then we have to make it so that you can buy it.
how to to this fixes i don`t know but maybe someone else can help or you find it helpfull
edit: Ignore this and check lewd_gamer_31415's reply on the next page instead, that should be the more correct option.
Last edited:
dragonflame
Well-Known Member
- Mar 9, 2020
- 1,666
- 788
- 331
- Aug 8, 2017
- 25,073
- 17,718
- 1,089
If you use the mod and have a long duration, extreme rapid pregnancy serum I think they'll show in around a week. It happens fast.
You actually want to use purchase_policy rather than buy_policy. Two different functions. The issue is that the Vren coded purchase_policy as a global method but is calling it as an instance method...As the error states, there's no purchase_policy method so I THINK that the method it is trying to call is the one named buy_policy, there's a few places that purchase_policy is references so I did a search and replace from purchase_policy to buy_policy in the role_city_rep.rpy file and it seems to work. At least it doesn't crash anymore
So change:
attention_floor_increase_2_policy.purchase_policy(ignore_cost=True)
to
purchase_policy(attention_floor_increase_2_policy, ignore_cost=True)
in role_city_rep.rpy lines 69, 77, and 321. (attention_bleed_increase_2_policy on 321)
Ah, so the buy_policy only buys the policy while the purchase_policy also activates it and triggers any related events. And for some reason the purchase_policy code is hidden away the the management_ui-file, that's what I get for not doing a proper search.
Guess I'll be manually activating a policy or two through the console next time I start the game to sort out this half-way-mess I've gotten myself into
Daily dose duty doesn't trigger. It's already mentioned but I checked a bit how it works.
It's broken in many ways:
1. It's supposed to be called from employee_on_move that is never triggered.
And that function should call daily_serum_dosage_duty_on_move but there's a condition that's never true anyway.
2. The function is defined as daily_serum_dosage_duty_on_move(self, the_person) and it doesn't need "self" argument.
It shows an error with this definition.
3. daily_serum_dosage_duty_on_move checks if a person already used serum but there's a wrong condition again:
if the_person.event_triggers_dict.get("daily_serum_distributed", False):
And even if you replace it with True, the flag is never cleared. So it would work only once like this.
I tried to make a workaround by switching daily_serum_dosage_duty_on_move function with on_day but it still has several issues:
1. It triggers only once/day now.
2. It triggers every day including weekends. I'm too lazy to check how conditions were supposed to work.
3. It spams log window with serum effects. But it would be like that anyway.
You can try to use these files but consider it just a bandaid fix.
It's broken in many ways:
1. It's supposed to be called from employee_on_move that is never triggered.
And that function should call daily_serum_dosage_duty_on_move but there's a condition that's never true anyway.
2. The function is defined as daily_serum_dosage_duty_on_move(self, the_person) and it doesn't need "self" argument.
It shows an error with this definition.
3. daily_serum_dosage_duty_on_move checks if a person already used serum but there's a wrong condition again:
if the_person.event_triggers_dict.get("daily_serum_distributed", False):
And even if you replace it with True, the flag is never cleared. So it would work only once like this.
I tried to make a workaround by switching daily_serum_dosage_duty_on_move function with on_day but it still has several issues:
1. It triggers only once/day now.
2. It triggers every day including weekends. I'm too lazy to check how conditions were supposed to work.
3. It spams log window with serum effects. But it would be like that anyway.
You can try to use these files but consider it just a bandaid fix.
tabernakle
Newbie
- Jun 4, 2017
- 30
- 188
- 128
So many of the new features don't work that I don't understand how this version could have been tested and released.
I wanted to start a milk empire, not a bug farm
I wanted to start a milk empire, not a bug farm
Strange... what version of the game are you playing? It used to be that you had to manually mark the serums that should be sold. But that was reworked a couple of updates ago. Now you should open a window by clicking "sell serums" where you see all serums you have in stock on the left side and value information on the right side. Sounds to me like you arent playing on the recent version
Likely gonna occur eventually, but Vren kinda a one man operation, so can only do so much per month. Though seems to be mostly done fixing business side stuff for now. Be lucky to get new models or faces someday... and your request prolly would at least require new models. Still, having serums affect player prolly more reasonable to expect soon. If ever!