LowLevelLesser

Active Member
Feb 8, 2021
792
1,006
I thought I remembered the dev saying that they were reworking the VN so that choices were actually recognized in game, but it's still a thoroughly on rails experience. A shame, that.
I was just about to make a comment about the fact that the game still acts like you did things with characters even if you didn't... like, just put a "skip scene" option instead of an ultimately pointless option to reject, resist, or ignore them. At least it plays along with your choice in the moment you make it at least, unlike certain other games that will give you 3 to 5 options when you actually only have one and would just shut you down anytime you try choosing anything else.
 
Last edited:

Sancho1969

Message Maven
Modder
Donor
Jan 19, 2020
12,272
47,237
Due to major system upgrades a replay is required.

Is that for the current version?
I've only just now started the mod porting process but I did notice the the dev upped the RenPy version (yet again) from v8.0.3 to v8.2.1

So, maybe. I'll be able to confirm in about half an hour or so... but devs really need to stop doing this. Stick with the damn RenPy version you started with until the VN is complete. Then (if you decide to write a new project VN) up to the most recent stable version of R. But... they will continue to do this unnecessary and futile exercise almost every time.
 

Joubei

Lilith Rising
Game Developer
Aug 17, 2021
460
1,219
I've only just now started the mod porting process but I did notice the the dev upped the RenPy version (yet again) from v8.0.3 to v8.2.1

So, maybe. I'll be able to confirm in about half an hour or so... but devs really need to stop doing this. Stick with the damn RenPy version you started with until the VN is complete. Then (if you decide to write a new project VN) up to the most recent stable version of R. But... they will continue to do this unnecessary and futile exercise almost every time.
Hey bro,
You are absolutely right,
But since I’m no longer the programmer on the project I had to do it as my team was working on 8.2.1.
season 2, is done in the new ver as well.
We’ve been hard at work, to get season 2 ready for public for end of August, so time is not on my side here.

Thanks a bunch for all your help!
 

Sancho1969

Message Maven
Modder
Donor
Jan 19, 2020
12,272
47,237
Hey bro,
You are absolutely right,
But since I’m no longer the programmer on the project I had to do it as my team was working on 8.2.1.
season 2, is done in the new ver as well.
We’ve been hard at work, to get season 2 ready for public for end of August, so time is not on my side here.

Thanks a bunch for all your help!
Let them know they can DL any RenPy version SDK they wish (any version)... I work on dozens of RenPy versions... you are not handcuffed to only one. I'm sure y'all know this but just making it clear just in case. Each SKD operates and runs independent of others installed on the same machine.
 

Sancho1969

Message Maven
Modder
Donor
Jan 19, 2020
12,272
47,237
To answer a question, yes, a new replay is going to be recommended. I'm not done porting the original Core mod content over but there's new content in the previous storyline. For example the Outpost "freeroam" now includes a Jezz Dinner event that wasn't there before, etc. I'm sure there are other examples but as stated, I'm still processing everything so I can actually start working on the update content (this is going painfully slow due to the revisions in coding of the original content).
 
  • Like
Reactions: Havik79 and motseer

Sancho1969

Message Maven
Modder
Donor
Jan 19, 2020
12,272
47,237
Ummm.... what?
You don't have permission to view the spoiler content. Log in or register now.

Joubei, let the team know: you set variables in conditionals after they've been declared in initialization, you don't declare variables in conditionals. This makes absolutely no sense whatsoever. All variables have one declared value... then set them as needed in the scripts via conditionals or other methods (direct setting via choices, Python functions, etc).

The above snippet... I don't think I've ever seen anything like that before... variable declarations via conditionals. It's like an oxymoron of sorts and certainly unorthodox. Maybe I haven't had enough caffeine yet but someone please school me on a base case where this would ever be acceptable in practice... this goes against every coding language documentation that I can think of tbh.
 
  • Thinking Face
  • Red Heart
Reactions: Joubei and WayonF95

motseer

Engaged Member
Dec 17, 2021
2,314
5,180
Ummm.... what?
You don't have permission to view the spoiler content. Log in or register now.

Joubei, let the team know: you set variables in conditionals after they've been declared in initialization, you don't declare variables in conditionals. This makes absolutely no sense whatsoever. All variables have one declared value... then set them as needed in the scripts via conditionals or other methods (direct setting via choices, Python functions, etc).

The above snippet... I don't think I've ever seen anything like that before... variable declarations via conditionals. It's like an oxymoron of sorts and certainly unorthodox. Maybe I haven't had enough caffeine yet but someone please school me on a base case where this would ever be acceptable in practice... this goes against every coding language documentation that I can think of tbh.
I'm guessing the biggest problem with this, other than convention, is that those variables can never have a default state to return to?
 

Sancho1969

Message Maven
Modder
Donor
Jan 19, 2020
12,272
47,237
I'm guessing the biggest problem with this, other than convention, is that those variables can never have a default state to return to?
Well... kind of, yes. Basically one (regardless of coding language) declares (defines) all variables at project initialization... the "base" of the variable's state (doesn't matter if it's integer, boolean, text, etc... it's the same principle). Once the actual coding is executed past initialization then one sets the variables as needed (they've already been declared). Then the rest of the code operates based on the variable setting (which can change of course).

So, you are likely thinking correctly tbh. For example one might have a variable that will be later used to reference an LI's relationship condition. So, we would declare something like "define li_relp = 0", so that the baseline (default) is nothing... no relationship. Then, as the story (in the case of the code being an AVN) we would set it to be something different on an as needed basis. One would NEVER use a conditional to define (declare) variables that I can think of. I've never seen it myself ever, and never seen any language documentation that would state otherwise.

So, that's basically the nitty-gritty summarized in layman's terms... if that makes sense. Bottom line: declaring (defining.. same thing) variables is VERY different that setting variables. Variables must be defined as one base then later set as needed.... never defined willy-nilly based on conditionals (again, that I've every seen or read).

Again, I'd love to be schooled where I'm incorrect (I'm all for learning new shit)... in any coding language (it's not specific to Python but all languages).
 

motseer

Engaged Member
Dec 17, 2021
2,314
5,180
Well... kind of, yes. Basically one (regardless of coding language) declares (defines) all variables at project initialization... the "base" of the variable's state (doesn't matter if it's integer, boolean, text, etc... it's the same principle). Once the actual coding is executed past initialization then one sets the variables as needed (they've already been declared). Then the rest of the code operates based on the variable setting (which can change of course).

So, you are likely thinking correctly tbh. For example one might have a variable that will be later used to reference an LI's relationship condition. So, we would declare something like "define li_relp = 0", so that the baseline (default) is nothing... no relationship. Then, as the story (in the case of the code being an AVN) we would set it to be something different on an as needed basis. One would NEVER use a conditional to define (declare) variables that I can think of. I've never seen it myself ever, and never seen any language documentation that would state otherwise.

So, that's basically the nitty-gritty summarized in layman's terms... if that makes sense. Bottom line: declaring (defining.. same thing) variables is VERY different that setting variables. Variables must be defined as one base then later set as needed.... never defined willy-nilly based on conditionals (again, that I've every seen or read).

Again, I'd love to be schooled where I'm incorrect (I'm all for learning new shit)... in any coding language (it's not specific to Python but all languages).
Thanks for the detailed explanation. Your example is pretty much what I had in mind. I have some coding experience though it mostly resides in the last century... hehe... c++, cobol, fortran, java... I feel certain there are few who could or would want to "school" you in your coding skills and conventions. There may be areas where "thinking outside the box" is good but this is probably not one of them. One always needs a core or base to return to.
 
Last edited:

e6mill

Well-Known Member
Aug 4, 2022
1,390
2,691
you set variables in conditionals after they've been declared in initialization, you don't declare variables in conditionals.
They'll be undefined (throw an error if you try to reference them) if the condition isn't true.
 

Sancho1969

Message Maven
Modder
Donor
Jan 19, 2020
12,272
47,237
They'll be undefined (throw an error if you try to reference them) if the condition isn't true.
No, no.... you're missing the point I'm making. I'm saying the variables should be declared (defined) WITHOUT conditionals. That's what my original post is pointing out. The use of a conditional to declare or define a variables is incorrect. They should always be declared/defined via only one basis and one basis only. In the case of conditionals they should only be used to SET a previously declared variable to a different state. It's two very different things.
 

Sancho1969

Message Maven
Modder
Donor
Jan 19, 2020
12,272
47,237
Joubei, another thing: did the steam app ID change for some reason recently?

In v1.0.2 was:
Python:
ju "{a=https://store.steampowered.com/app/2864850/Lilith_Rising__Season_2/}{u}Please wishlist Season 2 on Steam - click here.{/u}{/a}"
... and now:
Python:
ju "{a=https://store.steampowered.com/app/2424440/Lilith_Rising__Season_1}{u}Please wishlist the game on Steam{/u}{/a}"
Why did the app ID change bud?
 
3.50 star(s) 38 Votes