- Aug 17, 2020
- 442
- 456
A lot of those we fixed during the development of 0.0.20 (which is due in a few days actually!). I'll still double check for the Gym in particular as I don't recall fixing anything there.There are many timing issues with when locations open.
There's a few distinct types of issues:
I think some of this might be happening if 1 hour or 60 minutes is being added or subtracted wrongly. Looking at the check for the closing time in the following code for walking to the Mall from the Gym, it should be: 60 * 20 - 45 = 1155 as opposed to 1215, and the opening time should be 60 * 8 - 45 = 435, instead of 60 * 9 - 45 = 495
- The operating hours before a location opens are different then what is listed when they open.
- The check against $time for when the location opens doesn't match the operating hours quotes to the player.
- When check against $time if travel time will let you arrive when the store opens, time was added to the check instead of subtracted (instead of leaving 15 minutes early to arrive right when a store opens, it is checking for leaving 15 minutes late) (this is rare).
- Inconsistent use of gt and gte to arrive on the minute.
- Some combinations of the above.
Here we can see an example of most of those errors for the opening time and some issues for the closing time when traveling from the Gym (passage "Travel").
<<if ($time gt 495) and ($time lt 1215)>><span title="Open 9:00-20:00"><<link "Mall - (0:45)">><<goto "Mall">><<set $time to $time+45>><</link>></span><<else>><span style=color:#ec0000>Mall (Open 8:00-20:00)</span><</if>>
Also, when using the buss from the starter apartment (passage "Travel 1a"):
<<if $time gte 532 and $time lte 1250>><span title="Open 9:00-20:00"><<link "Mall - (0:08)">><<goto "Mall">><<set $time to $time+8>><</link>></span><<else>><span style=color:red>Mall (Open 8:00-20:00)</span><</if>>
Yeah, coding isn't really my biggest strenght as you probably noticed. This being said, I will definitely change the code as optimization is always great. I'll answer to the Kam.io stuff in the next little section of reply. As of the main suggestion, the social media is a major addition I really want to do in the future, but I am uncertain about having exact breakdowns there or anywhere. Not all checks need to be publicly available.Also: the dildo gag on the gag chance for dominance loss seems to be adding to $ASkill, IDK if that was intended instead of $OSkill
Also #2: The $kamcap doesn't currently do anything because it gets applied after $moneygain is added to $money:<<set $money to $money+$moneygain>><<if $moneygain gt $kamcap>><<set $moneygain to $kamcap>><</if>>
Also the Third: In passage "Sissy Hypno", $plug is checked for "Gem Plug" instead of "Gem Buttplug"
Suggestion: maybe a social media thing on the computer that's like you are posting a pic of yourself online and asking if you are passing, with them giving you the Convincegness score or even a break down of the Checks?
Suggestion Secundo: A modification to your coding style to make your code more compact and easier to make additions for. Let's take assigning the gym outfit's top in "GymOutfit" as an example.
The original code:
You don't have permission to view the spoiler content. Log in or register now.
Changed code:
You don't have permission to view the spoiler content. Log in or register now.
Now each outfit and its radio button is only being checked once, a new top gets appended to the end, and the check in case there are no suitable tops still works.
The way you write it still have a couple of issues. viewers need to be calculated before money as they are part of the viewers of the stream where you are getting payed out. Putting it at the end actually breaks it. Same goes for the cap. By moving the code around, you make it so the money gain multipliers supercede the hard limit for income. There is still one issue you address and mention however that definitely deserves a fix, so i'll get to that.Separate post about this one:
Passage "KamStream" still has problems, but it's simple to solve, the last few lines of calculating $moneygain are out of order. I've cleaned it up a bit from the .html and posted it and currently v0.0.19b works like this:
You don't have permission to view the spoiler content. Log in or register now.
What it should be (I assume) is this:
You don't have permission to view the spoiler content. Log in or register now.
Moving $viewerskamgain makes it have no further effect on viewers gained, and is moved to the end to prevent it from interfering with the other modfications $kamtype does to $moneygain. Given that $viewerskamgain isn't usable the way the rest of the passage is written now, I assume your current intention is to make all $kamtypes have the same outcomes?
Removing<<set $viewerskam to ($viewerskam+$viewerskamgain)>>
from the section preceding the code I posted and placing it after the modified version I showed would make everything work as expected.
All in all, thank you a lot for all the feedback, reports and suggestions, they really help me to improve the game!