Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Would you be open to contributions? I ended up working the fetish into the hatchery code.  I could flush out some of the birthing weights and maybe add a mechanic where energy is required to birth, and running out leaves them in until the next day.

If the oviposition fetish is set at night to 0, it comes back the next day at 1.  Do you know where or why this happens?

Thanks!  

Do you get a text log in the end of the day report? There is a dailyFetish inside of expansion.gd that has a chance of increasing a fetish daily but it should trigger a “$name feels like fetish is now {opinion}”

Yes, that's it, but it doesn't seem to output anything in 9.4.

  • if person.dailyevents.count([i]) + rand_range(0,2) >= globals.fetishopinion.find(person.fetish[i])*2: 
  • if person.fetish[i] != globals.fetishopinion.back(): 
  • person.fetish[i] = globals.fetishopinion[globals.fetishopinion.find(person.fetish[i])+1]

If a topic is taboo, any fetish check will make it dirty the next day which isn't wanted in this case.  This isn't handled yet as I didn't want to put in too many workarounds for things you may modify in the future anyway.

Code already includes some workarounds for the checkfetish function because we want to use fetish to modify the experience, without necessary modifying their fetish.  It's called a lot during the snail experience, and the built-in increase chance made things weird.  You'd fail the fetish check, have an awful time, then be more ok with the fetish.  Makes sense to have a check function that doesn't add to daily events.

For daily events, some of this is down to personal taste. I would put in chances to increase a fetish for each successful check, and maybe chances to decrease it for each failed check, both weighted by the check difficulty. (e.g. succeeding a very difficult fetish check would have a high chance for increase).  

(2 edits)

Nope, that's not it??

Anyway, the latest most cleaned version is available here:

https://mega.nz/file/23ZVzCKb#-xx8M94Ku2UDAfxH8CwUkkVF3YOuWnAo2TidZsyfxWU

I tried erasing any references to oviposition in the dailyevents log from any checkfetish call at the end of the snail event with:

while cattle.dailyevents.find('oviposition') > -1: cattle.dailyevents.erase('oviposition') 

but the reduction still happened.  I don't see anywhere else in the code that could drive this.  Even confirmed absence of oviposition in dailyevent right before the game calls dailyfetish().  It looks like the farm events in my game are from the prior day - dailyevent processes before the farm script.

I'm giving up for now.  No idea how that value is going back.  Maybe my save is somehow broken.