Deleted 1 year ago
The body images for characters update with a preference for the first available image. The order that images are searched for is: pregnant, naked, default. If a character does not meet the requirements for the first two images or they are not found then it will skip that image. When an image is automatically updated it will store a value in the person to indicate which type of image it is using. However, this value for the image type is not used nor updated when the image is manually changed (including the random portraits mod's button). Any change of image while the image type is set to pregnant or naked would confuse the system until the person matched the default image type again.
Checking the size of the image nodes is difficult without the Godot editor.
https://itch.io/t/838806/core-tag-size-rules
I don't make image packs so I don't have many tips for making them. There is a channel on the Strive Discord that is dedicated to portrait packs(https://itch.io/t/284398/discord). The game only supports PNG, JPEG, or WEBP image formats. Most use PNG because they like to replace the background with transparency, though some feel that it is just extra work especially with the fading added by the Bugfix mod.
Something to keep in mind about image sizes is that anime images often have very fine details for things like hair or facial features, when those are shrunk to the portrait size they may not appear correct. Also, while there may be small benefits to using larger images and letting the game scale them down, this results in rather large file sizes. There is no benefit to increasing the size of images unless you have some kind of image processing to add detail.
Looking through the code I can confirm my suspicion the else starting at line 801 of exploration.gd in the AricsExpansion mod files is the part of code that recruits the rescued captive but doesn't seem to do anything to remove them from the world.
else:
rewardslave.obed = 85
rewardslave.stress = 10
globals.slaves = rewardslave
text = "$name observes you for some time, measuring your words, but to your surprise, $he complies either out of symphathy, or out of the desperate life $he had to carry. "
The issue is exactly as you have guessed. This was an issue that I believed I had fixed at the start of February, but it seems that I made a mistake. There is code to filter out duplicates from the world, which will run whenever the save file's "modversion" does not match the value in the installed mod. Edit: the duplicates in the mansion will not be removed, but they will be given unique IDs.
The following code can be added below the last line of exploration.gd that you quoted. It should start with the same number of tabs as the as the quoted code. Note that you will need to use a decent text editor and replace the leading spaces with tabs as the forums automatically replaces them. If you change the mod file, then you will need to re-apply the mod; if you change the program file, then you are all set.
text = "$name observes you... #add after this line
for i in globals.state.allnpcs.duplicate():
if str(rewardslave.id) == str(i.id):
globals.state.allnpcs.erase(i)
break
Thanks, I wasn't sure the exact code to remove them from the world.
I did change the code myself but instead of removing the duplicate, I set it up to prevent the slave granting a reward from being added to the world list until you don't (or fail to) recruit them after the fight.
There was already an if statement that primes the reward at line 539 of the mod file, I added an else and moved the code that adds the slave to the pools there.
Then I duplicated the code to add them to the world in the reward section at the end of every scenario other than successful recruitment.
It seems to have worked fine so far and has the added benefit of not posting a message about maybe seeing them again until after they leave.
There is no easy option to limit or disable non-combat encounters. You can edit the file "...files/scripts/explorationregions.gd" with a text editor and change the weights(13 entries) found after 'noenemyencountered' to anything greater than or equal to zero. At zero it should be the vanilla system.
1) It was recently discovered that the trainer job was not included in the list of jobs to be updated at the end of the day, thus it has no effect. This can easily be fixed by opening ".../files/scripts/Mansion.gd" with a decent text editor, finding the line starting with "var corejobs" at the top of the file, and adding to the list:
,'trainer'
2) The tamer specialization has not been changed to handle trainers working with trainees. Slaves working the same jobs will effect each other, but pairing different jobs has to be done explicitly. In "Mansion.gd", the line that starts with "if i.spec == 'tamer' &&"can be changed to:
if i.spec == 'tamer' && i.away.duration == 0 && i.obed > 60 && (i.work == person.work || i.work in ['rest','nurse','headgirl'] || (i.work == 'jailer' && person.sleep == 'jail') || (i.work == 'farmmanager' && person.work in ['cow','hen']) || (i.work == 'trainer' && person.work == 'trainee')):
3) The farm has job skill experience for each of the jobs: farm manager, farmhand, milking, bottling, milk merchant, and stud. How much impact the experience has varies considerably, and unfortunately farmhands never use that experience for anything.
4) The bottles use a copy-pasted function that was altered slightly for each; however the first line of text says piss for all of them. Generally(RNG dependent), if a person has a good fetish opinion for drinking that type of liquid then they lose a lot of stress, else they gain a bit of stress.
5) Fetishes have a small impact on the gameplay and I see no exceptions for the player, so I assume yes. I believe the save file is the only place to change the MC's fetishes at the moment; it's not too hard to do with a online JSON editor, but the daily updates can reduce the values you set unless you disable that option.
6) The code for creating people does not include a way to specify a hybrid race so it is currently not possible to intentionally generate them outside of breeding. There are no specific conditions against them being randomly generated but the chances are fairly low due to the various factors involved.
"There are no specific conditions against them being randomly generated" is all I needed to know. Let the hunt begin :D
Thanks for all the answers, oddly enough I was editing my post while you were finishing yours, I managed to find and correct the spelling problem for point 4.
You were super useful, I will add those lines to the files at once!
EDIT: Uh, should I add 'trainee' beside 'trainer'?
EDIT2: The Trainer job now works as it should, thanks.
About point 3: what I meant is that if I have a slave do, let's say, entertainment, or hunting, that slave will eventually not only get better at his\her job, but also gain enough normal XP to actually level up. Farm jobs don't really give experience, whereas it would be useful\realistic if I could add strength\agility to farmhands\milkmaids without having to resort to take them out to tag along while I fight bandits.
Thanks mate. I think we may have actually resolved the issue that was going to be save-breaking, but I'm not 100% on that yet. I appreciate your support!
The fetishes don't add new actions during sex, they add new Desire requests and improve the response of the person to actions corresponding to the fetish. The requests are randomly selected from the pool of possible requests. The better the opinion of the fetish the more times it is added to the pool. Many of the fetish requests can only be selected if they are not already plausibly fulfilled, meaning that they will not request cum on their body if the still have cum on them from a previous interaction.
Obedience can drop for many reasons: high stress(this is a common problem), low reputation in the town they work, high courage and confidence but low loyalty, failing to have enough food to feed them, having a low obedience and high courage slave instigate problems, not interacting with slaves with the Clingy trait, high lust for many days without sex, low luxury(can happen if you run out of supplies midway through the end of day), or having a dirty mansion. These are vanilla mechanics.
The housepet job and sleeping in the kennel each reduce charm a little per day. The pet rule reduces charm significantly per day. Regressive trait has no per day nor any stat effects.
Having more than one slave sleep in the master's bed is usually a recipe for a stress disaster unless you have prepared carefully. High stress can wreck slaves. The important things for sleeping together in the master's bed is a good relationship between each of the slaves (can be checked in the Statistics tab) or having the Fickle trait and not having the Monogamous trait. These are vanilla mechanics.
Having a farm manager with low confidence has a bug that will inflict stress upon everyone in your mansion.
Many jobs cause stress even if the person may be inclined to it. Fear is a partial substitute for obedience, it has no stress effect though they may gain stress while raising fear. Toxicity will occasional cause a bit of stress, but unlikely to be a problem by itself unless they are mutating.
The hybrid races are part of Ralph's Tweaks, you need to enable those before a person is created or conceived to be given a hybrid race. They can be enabled using the Constants mod and restarting after changing the setting. You may need to try a couple times anyways as with 50/50 splits the dominant race can go either way but the hybrid only happens for one race (Demon for Succubus).
No, it's basically self explanatory for in-game use, but here's a basic guide.
To install: Open the game, press Mods in main menu, select Constants in the list(it should probably be last), apply mods, and restart the game.
To use: press Constants in the main menu, change the values however you want, and close the menu to save the changes and return to main menu. The left column is variable names (hover mouse over for description), the right column has values that can be clicked to change. The mod will automatically reload any saved changes whenever you start the game.
Enabling Ralph's Tweaks with Constants is a special case and will require a restart to go into effect.
Use a text editor to open "customScripts/expansionsettings.gd", and find the line:
var swollenenabled = true
Change the "true" to "false" to disable most of the swelling and immobility, they may need to have an update triggered (ending the day if nothing else) before the change goes into effect.
Generally, the in-game solution is to give them a bath using the luxury rules, though that only works after ending the day.
Branding is not mandatory for slaves; according to the lore, it provides magical functionality to prevent escapes and (for the advanced version) enforce particular rules. You would not be alone if you are interested in distinguishing the social rank of your slaves, but nobody has invested time into implementing it and it is a rather broad mechanic to implement for a rather particular perspective. The Discord for this mod is a better place to offer your suggestions as most of the modders do not actively monitor this thread, but you can leave them here if you prefer.
The GitHub is not considered stable at this time so you may experience more bugs than usual.
The penis size for the person with the strap-on is being compared against null instead of 'none', thus resulting in an incorrect size of -1.
I did not see any indication of fellatio only being enjoyed by giver. If you have a specific example that would make it easier to locate.
>The GitHub is not considered stable at this time so you may experience more bugs than usual.
Would that explain why I'm not getting any after-combat activities (like raping captives, or the reward dialog when high reputation) or is that an install problem on my fault. I'm using the latest main build
I just tested with a new progress and the 1.7 version of the mod from this topic and had no difficulties impregnating 2 female slaves within a week. Thus there must be another factor preventing you from impregnating your slaves. While editing the save file can produce any number of problems, crashing the game is the most likely problem and severe infertility is probably the least likely, but I can't rule out that possibility. There are 4 possibilities (besides contraceptives) that I can think of which could explain it.
If you downloaded the mod from the GitHub within the last 2-3 months, then you are using an unstable version of the mod and your progress likely has severe data corruption. The solution is to download version 1.7 from the beginning of this topic and start a new progress.
Many people fail to install the mod properly, the game appears to run at first but some features like exploring will be significantly broken. Any progress created with an improperly installed mod will have severe data corruption. The solution is to re-install the mod (the Discord linked in the first post is the best place for help with this) and start a new progress.
If you started the save data using a prior version(1.6 was released in a somewhat unstable state) and continued using it with the current version, then you may have some data corruption left over from the previous version. These tend to be fairly minor but still a needle in a haystack. It may be possible to fix the save data by comparing it to a new progress. The Debug mod can sometimes help with identifying what data is corrupt.
I have not tried out every possible pairing of races, fertility traits, and testicle sizes so I cannot rule out the possibility that there is a bug for certain combinations. This mod(as well as Strive itself) is notorious for appearing to work fine until someone tries an unfortunate combination of things. Diagnosing something like this would likely require you share your save file either here or through Discord. If such an issue is found, then changes can be made to the mod files and you can continue playing your save data.
Your line numbers for slave_tab.gd don't match mine, version 1.7, so either you have another mod or a different version. I wouldn't doubt that the relatives panel is bugged for slimes. I think the slime changes are likely incomplete. In this case only children slimes have the slimesire data entry so captured slimes will throw that error.
I haven't played for a while so it's quite possible I changed something and forgot. Thanks :)
Sounds like you either made a mistake while installing or installed conflicting mods. If you saved or auto-saved the progress while this mod was actually installed, then it is unlikely to be compatible with the game without this mod installed. Therefore, if the progress was saved with this mod installed and works after you uninstalled this mod, then you may not have had this mod installed. If you had a progress from before installing the mod and completely uninstalled the mod(or extracted a new Strive folder) and not simply deleted the mod folder, then you should be safe to play.
There will probably be a 1.8 but when is hard to know. Most likely, development will resume in a couple months.
There will be a 1.8. I've had some various health fun times so priority dropped on this for a little while but progress is still being made slowly but surely.
I would not suggest Aric's for your first ever playthrough of Strive. While it does add to the game, most of it is geared towards making the game more challenging for veteran players. I would use Ank's bugfix which is link in the first post and maybe the improved random portraits mod for your first playthrough.
I agree with Rendrassa on playing the game vanilla for a first run. Aric's mod adds a lot of complexity to the game, which is hard to appreciate if you don't know what vanilla gameplay is like. Also, most mods are not compatible with Aric's unless specified so if you want to try all the mods you will need to try them in batches. Some compatibility information: https://itch.io/post/5897523
This mod isn’t for everyone. I appreciate you taking the time to try it and give your feedback. The systems aren’t perfectly optimized, it’s mostly guesswork to find out what works to give the intended result. The typos tend to happen when you’re trying to add in a lot of new dialogue (especially with any level of randomness or procedural generation). It’s unfortunate, but it happens. Almost every system added has fairly extensive toggles and customization under ExpansionSettings.gd where they can be modified and often disabled. However, instead of what currently seems to be an aggressive rant at the team who have spent a lot of their time creating this free mod for those who enjoy it to enjoy, I’ll just encourage you to try making your own mod with any and all changes you’d prefer to see in the game! This is an awesome modding community and we are always happy to see new content.
I'm just going to copy my post from the Discord, since it seems to cover most of this. As far as I remember, the condition of being torn only exists for at most the duration of the interaction, though stretching is semi-permanent.
In version 1.7, you can use the Constants mod to easily and safely adjust many settings for Aric's mod. There are many parts to the stretching system; the ones related to your request are tearing and stretching. Tearing is when the person's stretching becomes unpleasant; Stretching is the chance to permanently increase in size. Stretching can effectively be disabled by reducing the chance to well below zero(it's a base chance not a multiplier, so there are other factors). The option names start with "stretchchance".
Unfortunately, tearing cannot be easily disabled. There are options for auto-recovery like "tornvagautorecovery", but this just means that it heals during the next orgasm. In order to disable tearing, you would need to edit the script newsexsystem.gd. If you change the mod file, then you must re-apply. If you change the game file, then it will vanish whenever you apply mods. Any text editor will do, but decent ones will make it easier.
if difference >= 5 + rand_range(-5,0) + person.sexexpanded.pliability:
This line can be found twice in the file, when true the person can tear. Thus to disable tearing we simply need to ensure that it is always false. This can be achieved by a simple change like this:
if difference - 1000 >= 5 + rand_range(-5,0) + person.sexexpanded.pliability:
I'm away and don't have access to the code(I just remembered the GitHub, though the versions don't quite match). There is a nightly chance to restore tightness, though there are 2 RNG checks. The details are found in expansion.gd in func dailyTighten. There is an option accessible by Constants(vaginaltightenchance), though it simply changes the base chance with an age multiplier. It is affected by the new trait for elasticity.
