Post by Kyrah Abattoir in Kesash's dynamic Renpy phone system comments

Kesash's dynamic Renpy phone system » Comments

Viewing post in Kesash's dynamic Renpy phone system comments

I've played with this most yesterday, and I'm really impressed with how well it actually works. I however have a few questions:

1. Is there a convenient way to create a "finished" conversation for a contact without using a large block of "kps_send_message_to_phone"? For example: A love interest's text history is used as a bit of a lore dump, but it is important to maintain the illusion that this is an exchange with the MC that happened several days ago, no new message notification and the conversation should be finished.

2. I have not found a setting to reveal what the MC will type when the user presses the reply button, is that an option? I'd rather avoid using single-option choices for that.

3. Would it be possible to add an option that allows the player to "call" a contact? In practice, it would ring and return occupied/non present unless it has been enabled (and then could be used to trigger a label jump/command/test conversation?

4. Is there a way to make the system a little less name-dependent? I like to allow the player to choose the name/gender of the MC, and it forces me to use a nickname for them in the phone, I also can't find a way to make conversations insert the player's current name/pronouns, unless I initialize every single conversation after the player has made their choice.

Thank you again for this rather amazing add-on!

Kesash5 days ago (3 edits)

1- Yep, the whole conversation is stored in conversation_name['all_dialogue'], so by extending that conversation with a conversation list it will be there as an already had conversation. So mc_whoever['all_dialogue'].extend({"mc":"Hey"}, {"whoever":"Hey"}) will add those messages, in that order, whenever its run. Want them at the start then just run it right after the start label (the other option is to just use the function to send a message a few times before the game propperly starts, easier but would mean more writing)

2- Not currently an option, it's been something I've been looking at. The code is all there to make it possible, its just changing how the button is displayed.

3-That would need an entirely new screen, it's not something that's currently planned.

4-The name dependency was for simplicity, without it creating conversations would require about 3 times more code than they currently do. You would need to assign every conversation to the phone from every direction it can be viewed from etc. The simplest solution would be to change the title of the conversation screen to show whatever the player entered instead of 'mc' if it should be 'mc'. So just adding this check in the main ui, the bit in between the two ###

And the same thing in the contacts list:

Then default var_kps_new_mc_name anywhere, just so anything, or an empty string, then after they have chosen the name just run $ var_kps_new_mc_name = their_chosen_name

Then wherever that name is displayed on the phone it will be changed to the new one :)

So if now run this at the start:

Opening Sarah's phone in the demo now shows this:

Kyrah Abattoir5 days ago

Woah thank you for the fast & detailed response, I'll try to make good use of it.

For point n°2, I really like the choice format, would it be possible to make the conversation jump argument optional?

As a future addition, would it be possible to have some sort of variable eval within text messages? Just so that dynamic texts that rely on a variable content can be taken in account by the phone conversations? Something like "character: Oh hello %firstname%, today is %current_day%.

Kesash5 days ago (1 edit)

What do you mean the jump argument optional?

They already do accept vars! Examples of how is in test_char_4 :)

you just need to use the actual dict format and not the shorthand when you make the line that uses a var, and then f string the message

Kyrah Abattoir4 days ago

Oh I must have missed this! Sorry about that.

By making the jump optional, I mean, something like this:

[["Option 1"],["Option 2"]]

Where the destination the choice lead to is omitted.

Effectively, the player is presented with 1 or more reply choices, but omitting the target conversation makes the conversation continue to the next line in the same conversation.

Kesash4 days ago

Ohhhhh, no, it will error if you leave it out. The button display logic needs to be changed. I have done it, and its planned for the full release, but I'm not sure how long that will take. I'm currently making a separate 'premium' release that is more 'game ready' that the current one with a LOAD more features, and that's one of them. I think it will take another hundred hours or so.

Deleted post5 days ago

Deleted 5 days ago

itch.io

Viewing post in Kesash's dynamic Renpy phone system comments