- May 6, 2017
- 9
- 6
Correct, it reduces the stress level but then this reduction gets ignored next time stress is calculated.It seems the stress is not reduced as intended after completing the nemesis quest. (Build 12)
The likely reason is the replaceAll command does not work on your browser version, try another browser.I found lots of error like this below when i were in the local contacts and nearly can't find any picture of those companies.
Error: <<set>>: bad evaluation: State.temporary.tempCompany.replaceAll is not a function
<<set _tempCompany = $Judges[_tempJudge].company, _tempCompany = _tempCompany.replaceAll(" ","")>>
thanks, will do.The likely reason is the replaceAll command does not work on your browser version, try another browser.
View attachment 1887688
Hey obsessionau, thank you for the update!So I was meaning to add relationship events for 30 or so girls and only provide one ore two new ones, but somehow it ended up the other way around.
Other than the new girls, you will notice significant changes to the auditions screen. The receptionists personality will affect what percs you get for the audition.
You can only download Build 12 fromYou must be registered to see the linksfor now. It's 600mb significantly bigger than build 11 due to the new models added.
Date: 14 June 2022
- New - 31 new models have been added. Total 149 by default
- New - New tags have been created for the RelationshipData.lsm file allowing for more flexible text types to be displayed.
- New - Author tag has been created for the RelationshipData.lsm file allowing a creator to identify their own events.
- Change - Model auditions checkbox is now selected by default.
- Change - Auditions for each girl now cost money (default 500) and have to be individually clicked to reveal the model.
- Change - Receptionist personalities will alter the cost for auditions and how many girls can be auditioned. Certain personalities will also allow you to preview model stats.
I will see if I can create an instructional pdf for the events as there is no example in the existing relationshipData file for how to use the "author" tag. but essentially:
Code:"RelationshipEvents":{ "AleciaFox1" : { relationship : 10, flag : "AleciaFox", author : "Your Name", <- add this to your event pgender : "male", eventcontent : [
My aim for this game is to be about smart play and not simply growing and becoming OP. You will want to focus on different things during the game depending on your deception choice and game stage as the punishment otherwise is grind. Currently you can get a new contract every 2, 3 or 5 shoots. If you want more contracts and your models to progress faster, stay doing full time work. If you want less stress and to make more money become self employed.- the number of contract offers per week should increase in dependence to the reputation
(e.g. 1-5 reputation = 1 contract / week; <5 reputation = 2 contracts / week; <10 reputation = 3 contracts / week; etc...)
This would significantly decrease the grind while fasten the pace of acceptance to the girls more revealing shoots.
Particularly when having many models & being self-employed, only one contract/week is much too less and makes the game mechanics tedious!
Plus it's the logical consequence: the more "famous" and reputated in business you'll become, the more contract options you'll get.
This might add a bit too much micro-management to the game trying to avoid this. A alternative is that the contracts are increased massively and get bonus's award if you match the models feature, comp winner or is popular. You then get a % commision based on the models personality and experience. This way you won't have to track anything it would be displayed but you will have to decide, do I want to give the contract to Model X who needs more contracts or to Model Y who will give me more money.- in relation to the reputation and the models popularity (~fame) it would be so great to negotiate and/or refuse "bad" or
"poorly" paid contract offers. That feature could also affect the relationship towards the models positively (if a contract satisfies the model)
or negatively (if the contract does not meet the models "status")?!
I did intend models with open or extroverted personalities to have an easier time doing these shoots, I'm not sure if I have coded anything in yet, but if I do it will likely affect the stability card chance. So Introverted models would have a higher chance of a stability event, and extroverted models would not get affected as much.- high confidence of a model (maybe paired with an open or extraverted personality) should effect the shoots,
the strongly confident/open/extraverted could give you more lewd/daring poses (up to widespreads, masturbation, close-ups etc. perhaps shown in an additional shooting category above the NUDE category ... or as some bonus pics in the NUDE category?!)
Creating an event for a model is very very very very time consuming with the chances of a player getting that model in their game low. As such working on these is not a high priority for me as I can have a bigger impact working on tweaking other components. I am working on improving the optimisation of the event system and making it easier to add and remove mods.
Will look at this for sure!- better accessible & more complete stats for the models in the overview list (for example there's no status shown about the relationships, so you always have to click yourself through each of the models subsites)
... and please list all the required stats in the model competition selection list (as "tatoos" are always missing there)
Concubine was never intended to be a thing (just a feature to cull models), I agree it does feel lackluster and not what a player might hope for. At the bare minimum I would like concubine it to have more of an impact (perhaps a chance for a generic blowjob scene and less stress for the week).- last but not least, I would strongly vote for some short movie/ gif scenes (maybe for the "special concubine events")
as well. These can, but not necessarily must be hardcore p*rn, cause most of your models are softcore actresses.
I do take on all feedback but being free ?fan fiction?, I tend to work on what I feel like as opposed to what should be worked on.I really hope, you'll consider some (or all) of my suggestions in one of the next builds, cause these would definitely improve your already decent game a lot in my opinion.
But even you don't think these suggestion could be constructive (or implementable), thanks again for your hard work and effort to share this one with us !
I currently have this set out for my modded stuff. Depending on the content available for that model, I try to add multiple events that get more saucy as you progress with that model (i.e from tame with special photo shoots with some stripping/nude training or yoga to hardcore/anal/bondage). Currently this can start as early as "friend" but something I can consider is having earlier events that are much more tame. Maybe you ask her to go for dinner/coffee, or out for a walk... etc. Maybe she could give a slight hint she likes you. (maybe an innocent nip slip or "accidental" upskirt).- more (lewd & non-lewd) [side]events, happening in different stages of relationship - not only when "smitten"
Already observed and I am in the process of modifying the way these mods work. As I have added a tonne of girls myself I have split them into two more manageable groups a core and extended group where the extended group needs to be manually loaded in each game.When you combine the main game with my modpack you have just shy of 250 models to choose from and this will only get bigger as the dev, I and other future modders add more. The likelyhood of you getting a model with an event (let alone multieple events) will get slimmer.
BUILD 13
Technically events will only be fired once, however there is currently a bug if the event is linked to multiple models where it can get fired again by the same model when the event is loaded in again for the second model.Questions about the events with models:
- Will they only be fired once?
- Any manual (or should I reverse engineer Plonkers file)?
- Any way to add events to already existing models, or will that cause a name clash? (eg will the model object inherit events?)
window.getLSMData = function () { return {
"ModDescription":"Event's by hotmike fore the base game.",
"RelationshipData":{
"HotM_ElsaJean1" : {
relationship : 9,
flag : "ElsaJean",
pgender : "male",
eventcontent : [
["image", "ElsaJean/event/1.webp"],
["$ModelSelected", "Want to go out on a date sometime?"],
["slug", "You laugh."],
["player", "What, your serious... Yeah sure how about after our next shoot?"]]
["image", "ElsaJean/event/2.webp"],
},
"HotM_ElsaJean2" : {
relationship : 9,
flag : "ElsaJean",
pgender : "male",
eventcontent : [
["$ModelSelected", "Well you ready?"],
["image", "ElsaJean/event/3.webp"],
["player", "Thought you'd never ask!"]]
["image", "ElsaJean/event/4.webp"],
["aside", "Holy shit she's hot in that!"]]
["image", "ElsaJean/event/5.webp"],
}
}}};
I am not sure what do you mean by "virtual" porn stars?Well I probably should keep my mouth shut for now but I must say I am pretty enthusiast seeing the efforts of the dev and the dedication of this modder community (Plonkers you are a prince !). Of course I will indulge in my bad porn habits and try to inject my own deviant pack at some stage. Just a general question, the game being real porn, would it be acceptable to propose virtual porn stars with fake biographies and custom events in the rather extreme range of the porn spectrum ? (I have many ready to fire and the image resolution is a breeze) Etiquette is a thing for me...
So the relationship level is exactly 9, (== 9), not at least 9 (>= 9)?Technically events will only be fired once, however there is currently a bug if the event is linked to multiple models where it can get fired again by the same model when the event is loaded in again for the second model.
Events can be created for existing models yes. Below is an example mod file to add 2 events for Elsa Jean. These events will fire when your relationship gets to 9 and you are a male character. The second event will fire the following shoot with Elsa.
There is nothing stopping somebody writing over the ModelsCore.lsm file and having ALL the models as 3D rendered girls/furries whatever you want.Sorry if I was not clear. I was just asking for the acceptabilty of using 3d renders of Daz Studio/ Rendo (or other) characters instead of internet real shoot pics, true virtual movie/porn stars (I have a bunch of them for various RPG projects and Renpy VN), there will not be technical obstacles, just ethical !)
It is "at least 9". Get 2 relationship cards in a single shoot and your relationship will go up by 2 so you can't have it as ==.So the relationship level is exactly 9, (== 9), not at least 9 (>= 9)?
This is good for events in a certain order, but for general ones, that you would like to play more often and thus enhance the user experience, it would require something like a minimal level. Maybe some label 'random_event' to mark random events?
If the events are only fired once, it is a relatively a lot of work to add them for such a small chance to get shown.