Unity ProjectR [v0.6.0.4] [Team-Apple Pie]
- Thread starter Ω Nelo Angelo Ω
- Start date
the only way so far is to use the player trait script and put it on the MC.
Interesting. Thanks for the information.
I guess I'll have to plan better with that in mind.
I'd personally change it on the woman_player.mix to change it from a 70% Maternal Grandmother, reduce the number and add a split chance between woman/sister (maybe 5-10%?), that way you get a shot at Sister at a lower% and Woman at a higher %.
share my save，actually，you just need foucs in the increase damage，and than just let them keep breeding.
DKing369
Member
- Jan 8, 2023
- 110
- 81
- 104
pressing "~" in your keyboard may fix the top of the screen unclickable. It's the way to open the console command and to close it. I did and on my case with the newest version its working. there will be another little box on the right side so if u want to get rid of it u should close the game.
I can see that being quite useful as a quick-fix solution in the current version, but in the long run it probably would end up being a bit odd once we see the other races in the game.
This would probably be a bit less of an issue if we could see what the recent lineage of our units was though.
Alternatively, I wonder if it work work to just make 2nd generation monmusu sterile? It would avoid this whole issue and could easily be balanced around making the 2nd generation ones get some extra traits.
I mean, yeah it is a quick fix, though I think it is explainable because the player is currently human, so less 'expressing a small amount of sister/woman' and more a small amount of expressing the 'player' genes.
I could see them just grabbing the id's (unknown for null) and doing it like they did MBM. Simple solutions.
I don't think 2nd gen Monmusu being sterile makes a whole lot of sense though. Could introduce some no win scenarios. It also doesn't help if you get Monmusu from alternate sources, as they'd still have the issue of no prior parentage to pull from when selecting the race.
I've not checked if Devs have stated a desire for monmusu to be player only in the future, in which case it'll become a non-issue anyway if they could breed with Man to create Woman/Sister/etc.
Running into an issue where the enemy raiding party gets stuck on a spot beyond the stockade. I tried loading to before it happened and it repeated. Also when another wave came they got stuck at the same spot. Any way to fix or avoid it?
I've not heard of that one before, but you might want to give more information.
What day did it start, what infamy level are you, which side (or both). Did it start after a long play session? Have you modified the game files in some way? And are you on the most recent version?
It'd also be a good idea to take a screenshot so people can see exactly where as well.
uglywolf
Member
- Nov 3, 2018
- 365
- 268
- 155
If this literally needs an immediate attention, should really ping UnknownDevDot
Anything you could tell us on how to reproduce this? Like, any specific actions you did before it happened?
Now that I think, do slaves birthing slaves with the MC also make impossible for them to birth monster girls with monsters?
And how does fetal growth is calculated, since both monster and slave have the stat? The sum? Average?
And how does fetal growth is calculated, since both monster and slave have the stat? The sum? Average?
I think that is not the case. I have to breed slaves to have one for orcs and one for goblins, and it doesn't seem to impact my monstergirl supply.
Since the baby's race is known at conception, maybe just by applying the baby's stat?
The first one is easy: No. It is impossible currently for a slave to be unable to give birth to a monster.
Long answer behind the scenes, the .mix files dictate how (and the % chance for it) and what can be born from a union. Anytime a monster breeds a slave, you get an 80% chance for it to be a monster, 20% for a Monmusu. This can change in the future, of course.
Fetal Growth time code that matters:
You don't have permission to view the spoiler content.
Log in or register now.
Short answer: It's the mother, and it has a minimum of 15 seconds.
Also, Sex time is determined by the male, and has a minimum of 5 seconds.
Edit: For the code for the others, it is part of the UpdateTrait method, btw.
So I guess the best pairing would be is mating a slave with conception and growth with a monster with sex time and his best stat.
I was hoping to see if letting the game run it would reset whatever it is on its own, so I guess the auto save before it started was saved over. Based on the manual save I do have, it would have to have been day 43 or 44. I was doing a lot of shifting things around before it happened (deleting old women that didn't have bonuses and placing more with bonuses into the pens). Left side. 450 infamy so almost level 3. I didn't touch the files. Version 0.4.0.3. There was a point way earlier where I had too many monster character windows open and unity said a stack overflow error happened, but I'm not sure if that is related.
The big issue is that you only are guaranteed 1 trait being passed on, so if you wanted damage on all, you should go for it.
I'd also imagine the biggest 'killers' are Conception rate and then fetal growth time. Sex Time currently is nowhere near as 'bad' as FetalGrowthTime for army production. Conception Rate currently isn't terrible either, though you do deal with the 'downtime' between attempts as well.
Guaranteed production feels better than missing a 70% chance or so. Then the time for the newborns to grow, as then that slave cannot be producing new units. Still a nightmare to get 3 traits currently instead of only 2, let alone the guaranteed 1.
As an aside, playing with the number of guaranteed traits being passed on sounds like a wonderfully meaningful upgrade.
The main thing is diminishing returns. There's a few categories:
Actual cap. Trait gets bigger, but effected mechanic is limited.
Sex Time
Fetal growth time
Crit Chance
conception chance
Knockback resist
Soft cap (numbers get bigger, but nothing in the game can actually differentiate)
Damage
Crit multiplier
Leaving only health that can, uncapped, deliver some marginal effect, but even that effect ultimately gets very small.
Development wise, what might be better overall is passing down averages plus or minus a fixed value/percent rather than sums. Spit balling pseudocode, something like round((.9+.2*rand())*($mom.trait+$dad.trait)/2) + randint(-1,1). That's an average, scaled between .9 and 1.1, rounded, then possibly increased or decreased by 1. That should keep breeding meaningful for much longer.
Actual cap. Trait gets bigger, but effected mechanic is limited.
Sex Time
Fetal growth time
Crit Chance
conception chance
Knockback resist
Soft cap (numbers get bigger, but nothing in the game can actually differentiate)
Damage
Crit multiplier
Leaving only health that can, uncapped, deliver some marginal effect, but even that effect ultimately gets very small.
Development wise, what might be better overall is passing down averages plus or minus a fixed value/percent rather than sums. Spit balling pseudocode, something like round((.9+.2*rand())*($mom.trait+$dad.trait)/2) + randint(-1,1). That's an average, scaled between .9 and 1.1, rounded, then possibly increased or decreased by 1. That should keep breeding meaningful for much longer.
I mean, sure, but then you rarely grow. It'll be meaningless for a long time, as if you breed the basic goblin with a level 2/village b woman with 1 in a stat you have a possibility of backsliding to 0. And any .9/1.1 scaling is going to be meaningless until relatively late stages anyway. I'm not a fan of it.
And honestly, we shouldn't be coding for min-max breeders anyway. Three-fold issues:
1) Not everyone is going to min-max. Or want to. There are many who just want to have fun making super gob.
2) Other constraints can be put into place to cater difficulty.
3) Those that want harder challenges can self-implement, or get something to make that formula for themselves.
There's other spins that could be put on it though, like making the minimum value be 80% of the lowest value and the maximum value being 120% of the highest value. With that method, if a +10 damage goblin mated with a +5 damage woman, the minimum would be +4 (80% of +5), while the maximum would be +12 (120% of +10).
It also would be possible to replace some base stats with inbuilt traits, so goblins could naturally start with a +5 damage trait rather than simply having 5 damage. This wouldn't make any difference at the beginning, but would affect breeding as there would be a starting trait for the calculations to work with. Similarly, orcs could come out the gates with a natural +6 damage trait and +45hp trait, replacing their natural 6 damage and 45hp. Obviously, this would need a bit of a rework with regards to how multiple traits are inherited as you wouldn't want a creature to not inherit a hp stat and immediately die on reaching adulthood.
But overall I quite agree with turtletamer that having the current exponential growth is not a feasible way forward. It quite quickly reaches the point where stats are irrelevant as every desired stat is effectively infinite, so either every combat becomes trivial or the devs add some kind of hard-counter system that makes our breeding program irrelevant (for example, having enemies with abilities like reducing all incoming damage to 1 or dealing % max hp damage to our monsters). As interesting as having such specialised enemies might be, it would be overall a bit underwhelming if our breeding efforts are pointless past the first couple of enemy types; that kind of specialisation I feel would be better saved for bosses and the like.
Last edited: