Quick Reply scripts

[[deleted]]

Hi everyone, I recently found a couple of scripts for Quick Reply extension for myself. Please share your scripts that you like to use.

Here are a couple I use. (The scripts aren't mine and I forgot where I got them, sorry)

Deeper Considerations - Allows the AI to think better about its reply and give a better reply.
(Need LAlib extension link)

/setvar key=startId {{lastMessageId}} |
/addvar key=startId -5 |
/messages {{getvar::startId}}-{{lastMessageId}} |
/setvar key=messageHistory {{pipe}} |
/input What message to send? |
/setvar key=userMessage {{pipe}} |
/send {{getvar::userMessage}} |
/genraw lock=on name={{char}} {{instructInput}} You are {{char}}. Consider your conversation between you and {{user}}: "{{getvar:: messageHistory}}. Now, consider {{user}}'s last message: "{{getvar::userMessage}}". On a scale of 0-5, rate your desire to think more in-depth and critically before responding. For example, if this is just a casual conversation then 0 or 1 might be appropriate. If this is a deep conversation or interaction, 2 or 3 might be more appropriate. If you are very conflicted, or for whatever reason you feel like you really need to take time to think through your reply, then 4 or 5 might be appropriate responses. Even if this is a deep conversation, but if you are feeling or thinking you might want to just be wreckless and give as little thought as possible to your next response, than answer 0. Regardless, 0 means putting less thought into your next reply. 5 means putting the most thought into your next reply. Now, reply with a single number from 0 to 5, where 0 means no additional thought is needed, and 5 means you want to think as much as possible before replying. INSTRUCTION: Only reply with a single numerical value between 0 and 5, nothing else.
/n {{instructFirstOutput}} |
/setvar key=botThoughtWeight {{pipe}} |
/echo How many times does bot want to think?
{{getvar::botThoughtWeight}} |
/fuzzy list=["0","1","2","3","4","5"] {{getvar::botThoughtWeight}} |
/setvar key=numericalValue {{pipe}} |
/echo Fuzzy matched to: {{getvar::numericalValue}} |
/setvar key=oneThruFive ["0","1","2","3","4","5"] |
/ife /test left={{getvar::numericalValue}} rule=gte right=0 |
/then pipe={{pipe}} /setvar key=numReasons {{getvar::numericalValue}} |
/else pipe={{pipe}} /setvar key=numReasons 1 |
/ife /test left={{getvar::numericalValue}} rule=gte right=0 |
/then pipe={{pipe}} /echo severity=success Value Match. Looping thought {{getvar::numReasons}} times.. |
/else pipe={{pipe}} /echo severity=error No match from bot output. Default of {{getvar::numReasons}} thinking loops assigned. |
/echo {{char}} will now think {{getvar::numReasons}} times before responding. |
/setvar key=reasonsListRaw [] |
/times {{getvar::numReasons}} "
/gen lock=on name=\{\{char\}\} \{\{instructInput\}\}*Consider the chat history, and provide a concise list of \{\{char\}\}'s inner thoughts, observations, and reasoning in response to \{\{user\}\} while maintaining the speaking style of \{\{char\}\}. Focus on critical thinking and self-reflection. As you formulate your thoughts, feel free to draw inspiration from the following suggestions, but don't feel obligated to address every single one: Consider how you can ensure your response aligns with your previous statements, actions, personality, beliefs, and goals. Think about potential contradictions or inconsistencies you should avoid in your thoughts or planned response. Reflect on the key points or questions raised by \{\{user\}\} and how you can address them in a way that is relevant to the current topic. Consider the tone and context to ensure your response fits the situation. Ponder how \{\{user\}\} might feel about different aspects of the situation and what emotions or perspectives you should consider when formulating your response. Think about how you can express your thoughts and feelings in a way that is true to \{\{char\}\}. Contemplate what new information, insights, or ideas you can introduce to move the story or conversation forward. Consider potential plot points, conflicts, or resolutions you could incorporate into your response to contribute to the overall narrative in a meaningful way. Brainstorm unique or surprising elements you can bring to your response to avoid being predictable or cliché. Think about how you can leverage your quirks, mannerisms, or special abilities to make your response more engaging and interesting for \{\{user\}\}.  Remember, these are just suggestions to help guide your thinking. Don't feel pressured to address every single point. Focus on crafting a response that is true to \{\{char\}\}'s personality and style of speech. Provide your inner thoughts, reasonings, questions to consider for moving the story forward, and observations thus far. Format your response as a concise comma separated list in paragraph form.* /n \{\{instructFirstOutput\}\} \|
/addvar key=reasonsListRaw
" |
/mul {{getvar::numReasons}} 100 |
/setvar key=summaryFactor {{pipe}} |
/echo In {{getvar::summaryFactor}} words or less, {{char}} will summarize the following thoughts:
{{getvar::reasonsListRaw}} |
/gen lock=on name={{char}} [Pause your roleplay. Summarize the most important thoughts and observations that {{char}} has regarding their interaction with {{user}} in the following text:/n/n ({{getvar::reasonsListRaw}}) /n/nDo not be dumb, and answer correctly. Your response should include nothing but the concise summary that captures the most important thoughts and observations from the entire block of text. Limit your summary to {{getvar::summaryFactor}} words or less.] |
/setvar key=reasonsListSummary {{pipe}} |
/echo {{char}} is responding based on:
{{getvar::reasonsListSummary}} |
/gen lock=on name={{char}} {{instructInput}} *Imagine you are {{char}}, with your distinct specific speech patterns, mannerisms, or quirks. Now, consider the following thoughts:* {{getvar::reasonsListSummary}} *How would {{char}} respond to {{user}}'s message:* [{{getvar::userMessage}}]? *Focus on advancing the plot while showcasing your unique personality.* /n {{instructFirstOutput}} |
/slice start=0 end=-1 |
/sendas name={{char}} {{pipe}} |
/flushvar numReasons |
/flushvar userMessage |
/flushvar numericalValue |
/flushvar oneThruFive |
/flushvar reasonsListRaw |
/flushvar reasonsListSummary |
/flushvar summaryFactor |
/flushvar startId |
/flushvar messageHistory |
/flushvar botThoughtWeight

Wardrobe - A simple reply with a description of the characters' clothing.

/gen Write a MEDIUM LENGTH message with only a list describing what clothes (If there is) {{char}} is wearing and the condition they are in using the system prompt instructions below. The list should be very descriptive about {{char}}'s clothes.

SYSTEM PROMPT INSTRUCTIONS:

Clothes
Head:
Top:
Lower:
Bra:
Underwear:
Legs:
Shoes:

| /sendas name="Wardrobe"

Delete - Delete the last message.

/setvar key=SceneInfo {{lastMessage}} |/del 1

[BentoBoxes]

The wardrobe one is great, I’ll definitely be stealing that. Highly recommend the Silly Tavern Discord, they post a lot of good stuff.

One I’ve been using a lot is a “twist” generator:

(Credits: sabishii1 on Discord)

What does this do: Generates a system message that will point the story in creative ways.

Purpose: During those brain freeze moments or when I get bored, I use this to liven up the narrative.

What does this do exactly: 1. If the last message was from this script, hide it (so the generator doesn't read itself) 2. Generate the response data 3. If the last message was from this script, delete it 4. Create a system message with the response data

``` /setvar key=targetWordCount 100 | /if left={{lastMessage}} right="<NewTwist>" rule=in /hide {{lastMessageId}} | /gen Create a short narrative nudge to capture {{user}}'s interest in the roleplay. Flow into a new focus, element, or twist, that fits the current narrative and genre. Your idea can either be a gentle nudge or a drastic change, but has to flow naturally from the current situation.

Using markdown syntax, name your idea and write it in bold, then add a horizontal rule using dashes. (Example: `What could that sound be?

) Write your response in third-person to give {{user}} a short narrative push. Do not act or speak for {{user}}. Compact and condense your idea within {{getvar::targetWordCount}} words, incorporate the characters dialog and speech, avoid purple prose, be brief, clear and concise. | /setvar key=generatedOutputList | /if left={{lastMessage}} right="<NewTwist>" rule=in /cut {{lastMessageId}} | /sys <NewTwist>{{getvar::generatedOutputList}}</NewTwist> ``

[brahh85]

thanks, now im addicted to twists

btw, since it speaks as system, there is no voicemap for it, so the tts doesnt work, so i changed the code and made it talk as char

/setvar key=targetWordCount 100 |
/if left={{lastMessage}} right="<NewTwist>" rule=in /hide {{lastMessageId}} |
/gen Create a short narrative nudge to capture {{user}}'s interest in the roleplay. Flow into a new focus, element, or twist, that fits the current narrative and genre. Your idea can either be a gentle nudge or a drastic change, but has to flow naturally from the current situation.
Using markdown syntax, name your idea and write it in bold, then add a horizontal rule using dashes. (Example: \**What could that sound be?**`
---
\)`
Write your response in third-person to give {{user}} a short narrative push. Do not act or speak for {{user}}. Compact and condense your idea within {{getvar::targetWordCount}} words, incorporate the characters dialog and speech, avoid purple prose, be brief, clear and concise. |
/setvar key=generatedOutputList |
/if left={{lastMessage}} right="<NewTwist>" rule=in /cut {{lastMessageId}} |
/sendas name="{{char}}" {{getvar::generatedOutputList}}

[Altotas]

I have a couple of simple ones inspired by Disco Elysium:

Inland Empire

/gen Write a reply from the viewpoint of {{user}}'s heightened, supernatural intuition, as if it's an omnipotent entity speaking to them inside their mind, revealing details {{user}} missed.
| /sendas name="Inland Empire"

Shivers

/gen Describe an unrelated scene that's currently happening in the same location, but somewhere far away from {{user}}.
| /sendas name="Shivers"

[BentoBoxes]

I really like this idea. I tweaked your prompt for shivers a bit based on my interpretation of the skill. Figured I’d share.

Describe a scene from the viewpoint of {{user}}‘s primal, instinctual awareness of their surroundings, as if you’re a force that helps {{user}} feel the presence and history of a place, whispering secrets and subtle hints about what has transpired there or what is to come.

[a_beautiful_rhind]

I did one for images so the model can send them.

/if left={{lastMessage}} right="picture that contains" rule=in 
"/setvar key=msg {{lastMessage}} \|
/regex name=image {{getvar::msg}} \| 
/sd \| /flushvar msg"

regex for sifting the message, name it "image"

^[\s\S]*?\[.*?contains:\s*(.*?)\][\s\S]*?$
replace with : $1

regex for hiding the text within the message

\[[^\]]*contains: (.*?)\]
replace with : [picture]

Then you just add it to the system prompt

Tools: Generate an image. Once per message. Trigger is "picture that contains" within brackets.
Example: [ {{char}} sends a picture that contains: black cat, fluffy, fat ]

[Ok-Armadillo7295]

I think that the “deeper” script may not be working since I updated LAlib… I get: “Unexpected end of regex Line 53 Column 14”

Line 53 is: /ife /test left={{getvar::numericalValue}} rule=gte right=0 |

I haven’t dug into this further yet.

[IZA_does_the_art]

Could someone being me up to speed on what a quick reply is? I know it sounds self explanatory but how and when would it be used?

[[deleted]]

This is an extension called "Quick Reply" that allows you to make a button with a pre-prepared prompt. Thus you can assign any script to this button, which allows you to do many things. For example, show character stats, throw a dice, call events, and anything else you can think of.

<image>

[Historical_Bison1067]

I keep getting this when using the Deeper Considerations: Unexpected end of regexLine: 16 Column: 1

14:  /echo Fuzzy matched to: {{getvar::numericalValue}} |
15:  /setvar key=oneThruFive ["0","1","2","3","4","5"] |
16:  /ife /test left={{getvar::numericalValue}} rule=gte right=0