Lusting my religion Version 0.4 Public release


Lusting my religion Version 0.4 has been released to public!!!

Files

Lustingmyreligion-0.4-pc.zip 517 MB
Aug 30, 2023
Lustingmyreligion-0.4-android.apk 530 MB
Aug 30, 2023

Get Lusting my religion(NSFW +18)[Remake Version 0.1.4]

Comments

Log in with itch.io to leave a comment.

(+1)

Lovely game so far. My only gripe with it is that the characterization seems a bit unclear. Not sure if the MC is selfish or not, and from Momo I’m really unsure if she’s super manipulative or earnest.

Small bug report. In the “She’s not a…” quest after you hand in the 8 logs and talk to Elizabeth, the previous quest step will uncheck itself and you will need to have another 8 logs in your inventory to finish it.

Also, I’m not sure if this is temporary, but having a percentage of your current money taken away every week doesn’t make much sense. That just incentivizes me to only sell things when I need the money. A system like in Scarlet Law, where you often need to make large purchases and have to pay a fixed amount every week that increases the more nuns you have, seems more fitting. Although in Scarlet Law not having that money would result in a game over. Maybe there’s a better alternative.

(+1)

Thank you so much for playing my game and for giving some feedback.

Although I don't consider myself as a good writer or anything like that at all I like characters having more than one "characteristic"  I think people behaves differently with certain people/situations and they change their behavior over time so I always try to do it that way when writing my characters. Nevertheless I should pay more attention to those details.

That bug has been already fix :)

That's exactly what will happen in later updates. That feature is in a very early development state right now.

(+1)

10/10 game

Thank you so much my friend!

(+1)

pro I'm just saying the truth thes game the amazing 

:)

(+1)

yay, new release!

and more or less the very first sentence after a fresh start has a typo :P

beacuse->because (twice in the scripts, ./src/chapters/prologue.rpy:21 and ./src/chapters/chapter1.rpy:825)

(+1)

as idea to improve the performance, especially on slower devices

you use "show" to display full screen images and animations. this renpy function adds the displayables to a layer and never removes them from the scene, they are still in memory and active, just hidden behind the next full screen image/video you show.

this is mostly noticable in the sex scenes, the more videos you show the slower everything gets (my poor old couch laptop stutters a lot when the third animation is started and the two former ones are still running, only invisible)

using "scene" instead of "show" has the same effect as you only use full screen displayables, but "scene" clears the whole screen and removes the former images/videos from the active layer and they are not kept in memory anymore.

this does not matter a lot for static images but on my device rather important for animations - your original variant with "show" was a stuttering mess, displaying the videos with "scene" instead smooth as butter.

as an example, from chapter2.rpy starting around line 720, my changes marked with '# was "show"'

     hide screen disable_Lmouse
     image mne_ch21 = Movie(play="anims/chapters/chapter2/mne_ch21.webm", loop=True, xalign=0, yalign=0)
     scene mne_ch21 with dissolve # was "show"
     melinda "This sensation..."
     melinda "I..."
     melinda "I just can't resist it"
     image mne_ch22 = Movie(play="anims/chapters/chapter2/mne_ch22.webm", loop=True, xalign=0, yalign=0)
     scene mne_ch22 with dissolve # was "show"
     melinda "The way it feels inside my mouth..."
     melinda "I like..."
     melinda "I like this so much!"
     image mne_ch23 = Movie(play="anims/chapters/chapter2/mne_ch23.webm", loop=True, xalign=0, yalign=0)
     scene mne_ch23 with dissolve # was "show"
     melinda "I must hurry!"
     melinda "Annie or Momo could be here at any moment!"

when you want to keep the better control of "show" with its layer management you could opt to "hide" the animations before the next one is started, this removes them from the active layer and they are not kept in memory anymore. don't think you benefit from it, though. a lot of hassle without great advantages, imo.

(+1)

talking to Elizabeth on the first free-roam day crashes the game as the quest "shes_not_a" is not yet defined

While running game code:
   File "game/src/events/elizabeth/elizabeth_events.rpy", line 6, in script
     menu(screen="left_choice"):
   File "game/src/events/elizabeth/elizabeth_events.rpy", line 10, in <module>
     "I've got the 8 logs" if shes_not_a.goals["Get 8 logs"] == True: 
NameError: name 'shes_not_a' is not defined </module>

a fugly hack is adding the needed chapter as first condition to the "if" (returns false, the faulty second condition is not even considered)

"I've got the 8 logs" if player.in_chapter >= 4 and shes_not_a.goals["Get 8 logs"] == True:

it would be probably better to prefill all quest variables with "False", as default values from the beginning of the game. the fugly hack above will be hell to maintain

Thank you so much for your help my friend. I really appreciate it