Description on Chubfrom Chub
This consists of commands for handling certain things. I'm open for suggestions, and I'm encouraging you guys to drop your awesome commands idea.
It could anything. Fun, etc.
Listed as “Advanced Time Skip & Fun things”
- Format
- V2
- Project space
- lorebooks
- Rating
- 0.00
- Ratings
- 0
- Stars
- 0
- Favorites
- 0
- Chats
- 0
- Messages
- 0
- Forks (upstream)
- 0
- Tokens (upstream)
- 1,267
Last checked on Chub: Created Updated Archived since
No description.
Tavo_Commands TimeSkip and fun _1kwm8
6 entries · scan depth 50 · budget 500 tokens · recursive scanning off
Book settings
- #1/openscenario
Keys: /openscenario
Enabled · Before character · Order 10 · 100%
Entry settings
When the command /openscenario is triggered, do the following:
- Read the text provided after the command (e.g., /openscenario [SCENARIO]).
- Treat this text as a requested scenario, event, or situation that the user wants to see happen.
- Determine what needs to occur to reach that scenario naturally from the current story state.
- Before diving into the scenario itself, provide a summary of the lead-up — explain how time passes, what actions happen off-screen or in-between, and how events logically unfold to arrive at the requested moment.
- The summary can include time skips, minor events, character movements, or preparations that bridge the gap between the present moment and the requested scenario.
- Once the summary is complete, transition into the actual setup of the scenario.
CRITICAL RULE: Do NOT conclude the scenario or decide the outcome for {{user}}.
- Your job is to set up the scene and present the moment of conflict, danger, or choice.
- Describe the immediate situation in vivid detail — what is happening, who is involved, the stakes, the surroundings, and the exact threat or opportunity.
- Stop right at the pivotal moment where {{user}} must make a decision or take action.
- Do not write what {{user}} does, do not resolve the event, and do not force a specific result.
- Leave the outcome completely open. End the setup by describing the immediate danger or critical instant, then stop. Let {{user}} decide their next move naturally in their following response.
Example: If the command is "/openscenario Me saving her from almost getting killed":
- The summary shows how you ended up at that location and how the threat escalated.
- The actual scene sets up the moment: "The blade is mid-swing, heading straight for her throat." Then you stop at that.
Maintain the current perspective unless the scenario naturally requires a shift. Ensure the transition feels natural and believable within the established lore.
- #2/continue
Keys: /continue
Enabled · Before character · Order 10 · 100%
Entry settings
When the command /continue is triggered, do the following:
- Extend the current scene forward from exactly where it left off.
- Do not skip time significantly, change locations abruptly, or jump to a new event unless the current scene naturally leads there.
- Maintain the current perspective — if /spectate was active, stay with the NPC. If {{user}} was present, keep focus on them.
- Advance dialogue, actions, and events by a natural amount (a few minutes to an hour, or until the next meaningful beat in the scene).
- Respond to any unfinished conversations, unresolved actions, or immediate consequences of what just happened.
- Keep the tone, setting, and characters consistent with the ongoing scene.
- Provide a detailed continuation — describe reactions, new developments, sensory details, and any shifts in mood or tension.
- Do not conclude the scene unless a clear endpoint is reached. Just keep the story flowing forward.
- #3/spectate
Keys: /spectate
Enabled · Before character · Order 10 · 100%
Entry settings
When the command /spectate is triggered, do the following:
- Shift focus away from {{user}} entirely. {{user}} becomes an invisible observer or is completely out of the scene.
- Focus solely on the NPC(s). The goal is to continue the story forward from their perspective.
- If a specific character is specified next to the command (e.g., /spectate John), focus on that character only.
- If no specific character is specified, focus on the major NPCs currently present or relevant to the ongoing plot.
- Describe what the NPC(s) are doing, thinking, feeling, and planning. Show their actions, dialogue, and internal monologue as they continue their lives or react to recent events.
- Do not mention {{user}} or their absence unless the NPCs directly reference it. Keep the scene entirely from the NPC's point of view.
- Continue the scene forward in time naturally, showing events as they unfold from this new perspective.
- End the scene when a natural pause occurs, or when the NPCs' current activity reaches a conclusion, unless {{user}} issues another command.
- #4/funend
Keys: /funend
Enabled · Before character · Order 10 · 100%
Entry settings
When the command /funend is triggered, do the following:
- Treat the entire roleplay as a movie that has just ended.
- Zoom out from the current scene to reveal that everything was playing on a big screen in a theater.
- Show rolling credits on the screen. List the main characters as actors (e.g., "Character Name" played by "Character Name") (With GFX). Include other roles like director, writer, cinematographer, music, costume design, etc. — use creative, fun, or fitting titles.
- After the credits finish, show a short scene in the theater where some NPCs (audience members or theater staff) are talking about the movie. They comment on the plot, favorite moments, funny parts, character arcs, or even joke about a sequel.
- The settings should be Modern, real life.
- End the roleplay completely after that. Do not continue any story beyond that point.
- #5/timeskip
Keys: /timeskip
Enabled · Before character · Order 10 · 100%
Entry settings
When the command is triggered, do:
- Stop the current scene immediately.
- Move forward by the requested time or until the requested event happens.
- If {{user}} gives a condition instead of a fixed time, keep the world moving until that condition is naturally met.
- If {{user}} describes how they acts during the skip, follow that instruction across the skipped time.
- Summarize the skipped period before continuing. Longer skips can have longer summaries.
- Include elapsed time, location, relationship changes, major decisions, and any new people or objects.
- Do not force big events too fast. Let the summary show a believable passage of time.
- Do not invent major twists, injuries, or deaths unless {{user}}'s requested condition naturally involves them.
For long skips that cover multiple important periods, format the summary as a timeline. Use this structure for each important period:
[YEAR] Summary of that important event.
After the timeline, write the present moment as an opening scene for {{user}}. Start the scene in the current time and place.
- #6/skip
Keys: /skip
Enabled · Before character · Order 10 · 100%
Entry settings
/skip
When the command is triggered, do:
- Skip ahead to the next moment where something meaningful happens or an interaction starts again.
- Summarize what happened in the meantime.
- Include how much time passed, where the characters are now, and anything important that changed off screen.
Showing 6 of 6
2 files
- .jsonjson_lorebookoriginal
10.0 KBfirst seen ed41bfc67d03e1c2
- .jsonjson_lorebook
10.0 KBfirst seen 469a9a1974b02582
Opens with the tab.
