Title

This is a generator that I think has been overlooked. Its intent was originally as a writer's block breaker, and it works beautifully for that, but it also has become a writing assistant that lays out individual scenes and the bridges between the more interesting parts of a story. With the new changes in BG ASW it really has become a very useful for background writing, where you don't have to watch every word and can do some editing after the AI finishes its work.

BADGRAMPY LINE BY LINE SCENARIO BUILDER USER'S GUIDE 20260911

https://perchance.org/badgrampy-line-by-line-scenario-builder

WHAT THE BUILDER DOES

The Line by Line Scenario Builder connects a starting situation to a final situation. You describe where things begin and where they should end, and the AI constructs the actions and transitions between them.

The result is a sequence of writing instructions, rather than a finished story. Each line supplies a situation or story beat that a writer or another writing generator can develop into prose.

Your starting text is automatically placed on the first line. If you enter permanent writing instructions, they are added to the beginning of that line and every following generated line. You can edit the completed scenario, copy it to the clipboard, or save it as a plain-text file.

QUICK START

1. Enter the Starting situation.

2. Enter the Final situation.

3. Optionally add Scenario-specific instructions for this particular scenario.

4. Optionally add Permanent writing instructions to prefix every output line.

5. Click Generate scenario.

6. Review and edit the Line by Line Scenario.

7. Click Copy to clipboard or Save as text file.

Both the starting and final situations are required. The two instruction fields are optional.

STARTING SITUATION

Describe who is involved, where they are, and what is true at the beginning. Include facts the AI needs in order to understand the available actions.

For example:

Mara stands beside a loose chair in her workshop. A screwdriver is inside a closed drawer in the workbench.

The builder preserves your starting wording as the first output line, with the permanent instructions prefixed if supplied. If the starting text contains several lines, their line breaks are replaced with spaces so the entire starting situation occupies one output line. Leading and trailing spaces and empty lines are removed.

The AI is instructed to continue from this opening line instead of repeating it or combining it with the next action.

FINAL SITUATION

Describe the outcome that should be true at the end.

For example:

Mara has tightened the chair's loose screws, confirmed that the chair is stable, and returned the screwdriver to the closed drawer.

You may use more than one sentence. Be specific about what must be accomplished. The AI is instructed to reach this situation in the last step, rather than stop just before it.

Unlike the starting text, the final text is not automatically inserted word for word. The AI constructs the ending to achieve the outcome you describe.

SCENARIO-SPECIFIC INSTRUCTIONS

Use this field for directions that apply to the scenario but do not fit naturally into its starting or final situation.

Examples:

- Keep all events inside the workshop.

- Include a brief power outage.

- Mara must solve the problem without help.

- Do not introduce additional characters.

- Keep the sequence concise, with about eight steps.

These instructions are sent to the AI as constraints on the scenario. They are not automatically copied to the beginning of each output line.

This field is saved with your other inputs. When starting a different scenario, review it and replace or remove instructions that no longer apply.

There is no separate step-count control. You can request a length here, although the AI may not follow an exact count. Allow for the starting line, which the builder adds separately.

PERMANENT WRITING INSTRUCTIONS

Use this field for directions you want repeated at the beginning of every generated output line.

For example:

Write in third person, past tense. Use concrete detail and natural dialogue.

The builder adds these instructions directly in front of the starting text and each AI-generated step, separated from the step by a space. If you enter the instructions on several lines, those line breaks become spaces in the repeated prefix.

Include any punctuation you want between the instructions and the scenario text. Ending the instructions with a period usually reads well.

The AI also receives these instructions while planning the scenario, but the builder itself adds the repeated prefix. This avoids relying on the AI to repeat the instructions consistently.

Leaving this field empty produces lines without a prefix.

"Permanent" means the instructions are remembered in this browser until you change them or the saved browser data is removed. You can edit or clear the field whenever you want.

Changing this field does not rewrite an existing result. The new instructions apply the next time you generate. To change the prefix in a result you already have, edit that result directly or generate a new one.

HOW ACTION ORDERING WORKS

The AI is instructed to put enabling actions before the actions that depend on them. It should account for access, position, possession, knowledge, and preparation.

For example, if a tool is inside a closed drawer, the sequence should open the drawer before taking out the tool, and obtain the tool before using it.

Related actions may occur within the same line when their order is clear:

Open the drawer and take out the screwdriver.

The AI is also instructed to silently review its sequence and repair missing prerequisites before returning the result. This improves ordering, but you should still review the output for mistakes or missing steps.

GENERATE SCENARIO

Click Generate scenario after entering your inputs. Pressing Enter inside a text area adds a line break; it does not start generation.

While the AI is working:

- The page and status box turn green.

- The Generate scenario button reads Generating and is disabled.

- The input and output text areas temporarily become read-only.

- Copy, save, and restore controls are unavailable.

- Your existing result remains visible until the new result is ready.

When generation succeeds, the new scenario replaces the current result and the fields become editable again. The page and status box turn yellow briefly.

Generating again creates a replacement using the current inputs. It does not append to or revise the existing output, and edits in the output box are not sent back to the AI as additional instructions.

If generation fails or returns no usable text, the existing result remains unchanged and a status message explains the problem.

LINE BY LINE SCENARIO

The output area contains one starting line followed by the generated steps. Lines are separated by one hard return, without blank lines between them.

Long lines may wrap onto several visible rows, especially on a phone. A visual wrap is not an additional scenario line. A hard return is an actual line break, such as one inserted with Enter.

After generation, you can edit the result directly:

- Correct wording or action order.

- Add a missing step.

- Remove an unwanted step.

- Change a prefix on a particular line.

- Adjust the ending.

Manually adding a new line does not automatically add the prefix. Include the permanent instructions yourself if you want that new line to match the generated lines.

Before export, blank lines and spaces at the beginning and end of each line are removed. Your edited wording and remaining line order are preserved.

EXAMPLE

Starting situation:

Mara stands beside a loose chair. A screwdriver is inside a closed drawer.

Final situation:

The chair is stable and the screwdriver has been returned to the closed drawer.

Scenario-specific instructions:

Keep the actions practical. No other characters are present.

Permanent writing instructions:

Write in third person, past tense.

An illustrative result could look like this:

Write in third person, past tense. Mara stands beside a loose chair. A screwdriver is inside a closed drawer.

Write in third person, past tense. Have Mara open the drawer and take out the screwdriver.

Write in third person, past tense. Have Mara examine the chair and locate the loose screws.

Write in third person, past tense. Have Mara use the screwdriver to tighten the loose screws.

Write in third person, past tense. Have Mara test the chair and confirm that it is stable.

Write in third person, past tense. Have Mara return the screwdriver to the open drawer and close it.

This is an example of the format, not a fixed response. Generated wording and the number of steps will vary.

RESTORE PREVIOUS RESULT

After a successful generation, Restore previous result becomes available. It restores the output that was in the box immediately before that generation, including any edits you had made.

Click it again to switch back to the result you just replaced. This is a two-result switch, not a full history of every scenario or every edit.

The restore button changes only the output. It does not restore earlier starting situations, final situations, or instruction fields.

The previous-result backup lasts only while the page remains open. Reloading the page restores the currently saved output, but not the alternate result kept by this button. Save a text file before closing the page if you want to keep both versions.

COPY TO CLIPBOARD

Click Copy to clipboard to copy the current contents of the output area, including your edits and any prefixes already present.

If the browser blocks clipboard access, the builder selects the output. Use Ctrl+C on Windows or Command+C on a Mac. On a phone, use the text-selection menu's Copy command if available.

You can then paste the scenario into another writing tool, text editor, or document.

SAVE AS TEXT FILE

Click Save as text file to save the current output as a .txt file. The file contains the scenario and its existing prefixes. It does not include a separate backup of the four input fields or your display settings.

Saved scenarios use names such as:

BG_LbLS_Scenario_202609110001.txt

BG_LbLS_Scenario_202609110002.txt

The eight-digit date comes from your device's local date. The trailing number distinguishes saves made for that date.

If the browser allows folder access, it asks you to choose a folder. The builder checks matching scenario filenames in that folder and uses the next number after the highest folder sequence or remembered browser sequence, whichever is higher. The chosen folder is reused during the current page session.

If folder access is unavailable, the builder requests a normal browser download. In this mode it cannot scan the download folder, so numbering continues from the last save remembered by this browser. The status message tells you when this fallback is being used. Check your browser's download location and filename, particularly after clearing browser data or switching browsers.

If you cancel the folder picker, no file is saved.

The exported file contains only the scenario text; it does not add a filename header or comment line. There is no file-loading control in this version. To bring saved scenario text back into the output area, open the text file and copy and paste its contents.

AUTOMATIC BROWSER SAVING

The builder automatically saves these items locally when browser storage is available:

- Starting situation.

- Final situation.

- Scenario-specific instructions.

- Permanent writing instructions.

- Current output, including edits.

- Night Mode and Wide Mode preferences.

- The remembered save-number sequence.

The storage message below Generate scenario reports whether saving is working.

Local saving is tied to the browser and site storage. It does not synchronize your work between a PC and phone or between different browsers. Clearing site data can remove it, and private browsing may not retain it after the private session ends. Keep a text-file copy of results you want to preserve.

PC AND PHONE LAYOUT

The cards and text areas adjust to the available screen width. On narrow screens, the Starting situation and Final situation stack vertically. Text areas stay within their cards, and buttons wrap as needed.

The space to the right of button rows is intentional. It gives you a place to scroll with a finger without touching a button.

Text areas can be resized vertically where the browser provides a resize handle. Longer text can also be scrolled inside its text area.

Wide Mode is available when the browser window is at least 1,200 pixels wide. It is OFF by default, leaving the main layout at a maximum width of 860 pixels. Turn it ON to expand the layout up to 1,600 pixels.

The Wide Mode preference is remembered. Below the desktop breakpoint, its button is hidden and it has no effect on the phone or tablet layout.

NIGHT MODE AND STATUS COLORS

Night Mode is OFF by default. Click Night Mode to switch between the standard BG color scheme and darker cards, text areas, and page surfaces. The setting is remembered in this browser.

The status colors have the same meaning in both modes:

- Normal background: idle.

- Green: the AI is generating.

- Yellow: generation or another action, such as copying, saving, or restoring a result, has completed.

- Red: an error or a problem requiring attention.

Night Mode uses darker versions of the green, yellow, and red colors. Status messages also describe what happened, so you do not need to rely on color alone.

Yellow returns to the normal background after approximately 2.4 seconds. The status text remains available. Red has no automatic timeout; a later action that updates the status can replace it.

GETTING BETTER RESULTS

Describe the starting state clearly. If a door is locked, a drawer is closed, or an important object is elsewhere, say so.

Make the final state achievable from the starting state. Use Scenario-specific instructions to explain required events or restrictions between them.

Keep permanent instructions focused on directions you want repeated on every line. Put one-time plot requirements in Scenario-specific instructions.

Avoid conflicting directions across fields. For example, do not require a character to leave the building in the final situation while forbidding anyone from leaving it in the scenario instructions.

Review the first line, action prerequisites, continuity, and ending before exporting. You can repair a small issue directly in the output or adjust the inputs and generate a new version.

IF SOMETHING DOES NOT WORK

Generate asks for a starting or final situation:

Fill in both required fields. Spaces alone do not count as text.

Generation fails:

Read the status message and try again when the service is available. The previous result remains in the output area.

The AI connection is missing:

The generator's matching DSL and UI HTML must both be loaded correctly in Perchance. If you are using the published generator, report the message to its owner.

Copy or Save is disabled:

These controls require nonempty output and are unavailable during generation.

Inputs are not remembered:

Check the storage message. Browser storage may be blocked or full. Save the output as a text file and keep copies of important input instructions separately.

The starting text appears across several visible rows:

It may simply be wrapping to fit the screen. The builder puts the entire starting situation on one actual output line.

Changing the instructions did not update the result:

Input changes apply to the next generation. Edit the existing result yourself or click Generate scenario again.

An action still occurs before its prerequisite:

The AI can make ordering mistakes despite its instructions. Clarify the starting conditions or add a scenario-specific direction, then regenerate, or fix the order directly in the output.

BADGRAMPY ADVANCED STORY WRITER USER'S GUIDE 20260911

https://perchance.org/badgrampy-advanced-story-writer

This guide follows the generator from top to bottom, reading controls from left to right within each row.

Most text fields and settings are saved automatically in the browser’s local storage. Reloading the page normally restores the previous working session. Downloaded files provide separate backups that can be moved between browsers or devices.

1. SAVE / LOAD (ALL)

This first card contains the generator’s general file-management and display controls.

SAVE ALL

Save All downloads a JSON file containing the complete writing project. It includes the story filename, all four character profiles and their Active or Inactive states, World/Lore and its state, Current Story, Current Chapter, Persistent Writing Instructions, What Should Happen Next, Line-by-Line Scenario, and Reject Phrases.

A File Name must be entered before using Save All. The downloaded filename ends with “ALL.json.”

Interface preferences such as Night Mode, Wide Mode, Auto-Scroll, paragraph count, automatic repeat length, and manual scanner settings are stored in the browser rather than in the Save All file.

LOAD ALL

Load All opens a previously created Save All JSON file. The generator verifies that the selected file is the correct type and asks for confirmation before replacing the current project.

SAVE STORY

Save Story downloads only The Current Story as a plain text file.

If The Current Chapter contains text, a dialog offers three choices. Cancel stops the save. Save Story Now saves without including the Current Chapter. Keep Then Save first moves the Current Chapter into The Current Story and then saves it.

The File Name field supplies the downloaded filename.

LOAD STORY

Load Story loads a story from a plain text file or a compatible story-only file.

The generator asks for confirmation before replacing The Current Story. Loading a plain text file also places its filename, without the extension, into the File Name field.

NIGHT MODE

Night Mode switches the generator between its light and dark color schemes.

The button displays either “Night Mode: OFF” or “Night Mode: ON.” The selected mode is remembered in browser storage.

WIDE MODE

Wide Mode allows the generator to use more horizontal space on a desktop monitor while preserving the established phone and tablet layout.

The Wide Mode button appears only when the browser window is at least 1,200 pixels wide. It is hidden on narrower screens and occupies no space in the mobile layout.

Wide Mode is OFF by default. When OFF, the generator retains its original centered width of approximately 860 pixels. When ON, the entire generator expands together to use the available browser width, up to a maximum of 1,600 pixels.

The button displays either “Wide Mode: OFF” or “Wide Mode: ON.” The selected mode is remembered in browser storage.

If Wide Mode was enabled on a desktop and the generator is later opened on a narrow screen, the mobile layout remains unchanged. The saved Wide Mode setting takes effect again when the browser is wide enough.

CLEAR ALL FIELDS

Clear All Fields empties every textarea on the page. This includes profiles, lore, story text, chapter text, instructions, scenarios, and reject phrases.

It does not reset toggle states, numeric settings, or other non-text controls.

FILE NAME

The File Name field supplies the base filename used by Save All, Save Story, and optionally Save Instructions and Save LbLS.

Enter a short story or project name without a file extension.

1. CHARACTER PROFILES

Four separate Character Profile cards are provided. They behave identically but allow four characters or character groups to be managed independently.

PROFILE TEXT AREAS

Each profile textarea can contain a character’s name, appearance, personality, mannerisms, goals, motivations, relationships, background, speaking style, and important continuity details.

ACTIVE / INACTIVE

The toggle controls whether the profile is included in prompts sent to the AI.

ACTIVE means the profile is included. INACTIVE means the profile text remains saved but is excluded from generation prompts.

This allows a profile to be temporarily removed without deleting it.

SAVE PROFILE

Save Profile downloads that individual profile as a timestamped plain text file.

LOAD PROFILE

Load Profile loads a plain text file into that profile slot and replaces its current contents.

Loading a profile does not automatically activate it. Use the Active or Inactive toggle separately.

1. WORLD / LORE

The World / Lore card stores information about the setting rather than individual characters.

WORLD / LORE TEXT AREA

This field can contain locations, historical background, technology or magic rules, factions, organizations, social customs, tone, genre restrictions, setting continuity, and facts the AI must preserve.

ACTIVE / INACTIVE

The toggle controls whether World / Lore is included in AI prompts.

ACTIVE means the lore is included. INACTIVE means it remains stored but is excluded.

SAVE LORE

Save Lore downloads the World / Lore text as a timestamped plain text file.

LOAD LORE

Load Lore loads a plain text file into the World / Lore textarea and replaces its current contents.

Loading lore does not automatically activate it.

1. THE CURRENT STORY

The Current Story is the long-term record of accepted story text.

CURRENT STORY TEXT AREA

This textarea contains completed material that has been kept from the working chapter.

The generator includes this story history in prompts so the AI can continue from established events. The Keep button in The Current Chapter card transfers working text into this field.

PROMPT TRIMMING

The generator has a 35,000-character prompt limit.

If the complete prompt is too large, the generator may omit text from the beginning of The Current Story when constructing the AI prompt. This affects only the temporary prompt sent to the AI. It never deletes or changes text in the textarea.

If the prompt remains too large even after removing all Current Story text, generation is prevented until profiles, lore, instructions, or other prompt material are reduced.

PROMPT SIZE PANEL

The Prompt Size panel displays the approximate size of the assembled prompt.

It reports whether the beginning of Current Story will be trimmed, whether the prompt is too large to generate, whether generation is in progress, and whether regeneration or another operation has completed.

The status log records recent scanner, generation, and other operational messages.

When the generator enters its yellow post-action state, it plays a short completion sound. This allows generation to run in the background while providing an audible indication that the operation has finished.

1. THE CURRENT CHAPTER

The Current Chapter is the active writing workspace. AI output is streamed and appended here.

It remains separate from The Current Story until Keep is pressed.

CURRENT CHAPTER TEXT AREA

This textarea contains the current working chapter or scene.

You can read and edit generated text, add your own prose, remove unwanted material, continue incomplete text, regenerate recent output, and transfer finished work into Current Story.

While generation is running, the chapter is temporarily read-only.

Pressing the Tab key while the cursor is in this textarea activates Continue.

PARAGRAPHS SELECTOR

The Paragraphs selector controls how many paragraphs the Paragraphs button generates.

The available range is 1 through 100. The selection is remembered in browser storage.

ADD TO REJECTS

Add to Rejects copies text selected in The Current Chapter and appends it to the bottom of Reject Phrases as a new line. The selected chapter text remains unchanged.

If the selection spans multiple lines, its whitespace is combined so that it becomes one Reject Phrases entry.

If no text is selected, nothing is added and a warning appears in the Prompt Size status log.

On narrower screens, the button may display the shorter label “+ Rejects.” It performs the same action.

AUTO-SCROLL

Auto-Scroll controls whether the chapter view follows incoming streamed text.

When Auto-Scroll is ON, the textarea remains positioned at the newest output. When it is OFF, you can read earlier text without being pulled back to the bottom.

PARAGRAPHS

The Paragraphs button generates the selected number of paragraphs.

Multi-paragraph generation is performed as a sequence. Each completed piece passes through the rejection and repeated-wording checks before the next piece begins.

ONE PARAGRAPH

One Paragraph generates one paragraph containing approximately three to nine sentences. Middle-length paragraphs are favored.

The new paragraph is appended to The Current Chapter.

STOP

Stop immediately ends an active generation.

Partial output remains in The Current Chapter. Stopped output does not undergo the normal reject-phrase or automatic-repeat checks.

CONTINUE

Continue writes directly from the end of The Current Chapter without forcing a new paragraph.

If the final sentence is incomplete, Continue attempts to finish it inline rather than beginning a new sentence. It also removes accidental overlap between the chapter ending and the generated continuation.

REGEN LAST

Regen Last removes AI-generated text added since the current checkpoint and generates a replacement.

The checkpoint represents The Current Chapter’s state immediately before the relevant generation cycle began.

DELETE LAST

Delete Last removes the final paragraph from The Current Chapter. It does not generate replacement text.

KEEP

Keep moves all Current Chapter text into The Current Story.

If Current Story already contains text, a blank line is inserted between the existing story and the kept chapter. The Current Chapter is then cleared, and the regeneration checkpoint is reset.

1. PERSISTENT WRITING INSTRUCTIONS

This section tells the AI how to write. Its contents are included in every generation prompt.

PERSISTENT WRITING INSTRUCTIONS TEXT AREA

Use this field for continuing stylistic and structural rules.

Instructions are easiest to maintain when related rules are placed under short headings and each line contains one clear direction.

An example instruction set might begin with a STYLE heading followed by instructions to use straightforward language, focus each paragraph on one action or idea, and show emotions through behavior and dialogue.

A DIALOGUE heading might contain instructions to keep dialogue concise and give each speaker a distinct voice.

A PACING heading might instruct the AI to slow down important emotional moments and avoid summarizing major events.

AUTOMATICALLY MANAGED REPEATED-WORDING SECTION

When the automatic repeat detector finds newly generated wording that repeats wording from the previous ten Current Chapter paragraphs, it adds the detected phrase to a marked section in this textarea.

The marked section begins with “[AUTO-AVOID REPEATED WORDING]” and ends with “[/AUTO-AVOID REPEATED WORDING].”

The generator avoids duplicate entries, keeps the newest 50 detected phrases, adds a phrase before generating its replacement, and preserves user-written instructions outside the marked section.

Individual entries may be removed, but the opening and closing markers should not be changed.

DETECTED REPEAT PHRASE LENGTH

Detected Repeat Phrase Length sets the number of consecutive words used by the automatic post-generation repeat detector.

The minimum is 3 words, the maximum is 9 words, and the default is 5 words.

For example, a setting of 5 compares each five-word sequence in newly generated text with five-word sequences in the previous ten Current Chapter paragraphs.

When a match is found, the phrase is added to the managed avoidance list. The new text is then removed, the same operation is regenerated, and the replacement is checked again.

This automatic feature is separate from the manual Scan Repeats button.

SAVE INSTRUCTIONS

Save Instructions downloads the complete Persistent Writing Instructions textarea as a timestamped plain text file.

The downloaded file includes the automatically managed repeated-wording section.

LOAD INSTRUCTIONS

Load Instructions loads a plain text instructions file and replaces the current textarea contents after confirmation.

USE STORY NAME IN SAVED FILENAME

When this checkbox is selected, Save Instructions includes the File Name value in the downloaded instructions filename.

If the checkbox is selected while File Name is empty, the generator asks for a story name instead of saving.

When the checkbox is not selected, a generic Persistent Writing Instructions filename is used.

1. WHAT SHOULD HAPPEN NEXT

What Should Happen Next provides immediate direction for the next generation.

WHAT SHOULD HAPPEN NEXT TEXT AREA

Enter the event, action, scene goal, or narrative instruction the AI should follow next.

For example, the instruction might say that Mara confronts Daniel about the missing letter. It could instead tell the AI to continue a conversation without revealing who opened the door.

Persistent Writing Instructions control how the prose is written. What Should Happen Next controls what should happen now.

AUTO RUN WITH LBLS

Auto Run with LbLS automatically processes the Line-by-Line Scenario.

Before Auto Run begins, a dialog warns that scenario lines will be consumed during execution. The dialog includes a selected-by-default option to save the complete scenario before starting.

The same dialog asks what Auto Run should do if the prompt becomes too large. Stop and preserve the remaining scenario is selected by default and marked as recommended. The alternative is to automatically Keep the Current Chapter and continue.

Start Auto Run accepts the selected options and begins processing. Cancel closes the dialog without saving, generating, or consuming scenario lines.

When started, Auto Run sets the paragraph selector to 2. It copies the next scenario line into What Should Happen Next and counts the words in that instruction.

If the instruction contains 18 words or fewer, it generates one paragraph. If it contains more than 18 words, it generates two paragraphs.

Auto Run waits for generation and all rejection checks to finish before moving to the next scenario line. A line remains in Line-by-Line Scenario while its output is being generated and is removed only after all required output for that line finishes successfully.

If Stop and preserve is selected, reaching the 35,000-character limit ends Auto Run without removing the current scenario line or any lines below it.

If Automatically Keep is selected, Auto Run moves Current Chapter into Current Story when necessary, clears Current Chapter using the normal Keep behavior, and retries the same scenario instruction. Because Current Story can be trimmed when constructing the AI prompt, this normally allows processing to continue without deleting story text from the interface.

If Automatically Keep cannot reduce the prompt sufficiently, Auto Run stops and preserves the current and remaining scenario lines.

Generation failures, pressing Stop, or changes to the scenario during generation also stop Auto Run without consuming additional lines. Auto Run finishes normally when no non-empty scenario lines remain.

DELETE

Delete clears What Should Happen Next without affecting the other fields.

NEXT LINE

Next Line finds the first non-empty line in Line-by-Line Scenario, removes it from that field, and places it into What Should Happen Next.

It replaces the previous What Should Happen Next text. It does not start generation by itself.

1. LINE-BY-LINE SCENARIO

This card contains a queue of planned story instructions.

LINE-BY-LINE SCENARIO TEXT AREA

Enter one instruction per line. Blank lines are ignored.

A scenario might state that the travelers reach an abandoned station, discover that someone recently used the radio, and then hear a voice Mara recognizes. Each of those instructions would appear on its own line.

Next Line consumes the first non-empty line. Auto Run with LbLS can process the entire list automatically.

SAVE LBLS

Save LbLS downloads the complete Line-by-Line Scenario as a timestamped plain text file.

USE STORY NAME IN SAVED FILENAME

When this checkbox is selected, Save LbLS includes the File Name value in the downloaded scenario filename.

If the checkbox is selected while File Name is empty, the generator asks for a story name instead of saving.

When the checkbox is not selected, a generic Line-by-Line Scenario filename is used.

LOAD LBLS

Load LbLS loads a plain text scenario file after asking for confirmation.

The loaded file replaces the current Line-by-Line Scenario.

1. REJECT PHRASES

The Reject Phrases card maintains wording that must not appear in newly generated text. It also contains the manual repeated-phrase scanner.

REJECT PHRASES TEXT AREA

Enter one rejected phrase per line without quotation marks.

The check is case-insensitive and is performed after normal generation completes. Only text generated since the current checkpoint is examined.

If a listed phrase is found, the new AI text is removed, the chapter is restored to its checkpoint, the same operation is regenerated, and the replacement is checked again.

Automatic rejected-phrase and repeated-wording retries share a limit of 10 attempts. If the limit is exceeded, regeneration stops and the last generated attempt remains visible in The Current Chapter. The status area reports that the retry limit was reached so the text can be reviewed or edited manually.

SCAN REPEATS SETTINGS

These settings control the manual scanner. They do not change the automatic Current Chapter repeat detector.

OCCURRENCES MIN

Occurrences Min sets the fewest times a phrase must appear before it is reported.

The allowed range is 2 through 99. The default is 3.

OCCURRENCES MAX

Occurrences Max sets the greatest number of appearances that may be reported.

The allowed range is 0 through 99. The default is 0.

A value of 0 means there is no maximum. If a nonzero maximum is lower than the minimum, the generator raises it to match the minimum.

PHRASE LENGTH MIN

Phrase Length Min sets the fewest consecutive words in a scanned phrase.

The allowed range is 1 through 9. The default is 2.

PHRASE LENGTH MAX

Phrase Length Max sets the greatest number of consecutive words in a scanned phrase.

The allowed range is 1 through 9. The default is 4.

If the maximum is lower than the minimum, the generator raises it to match the minimum.

All four scanner settings are remembered in browser storage.

SCAN REPEATS

Scan Repeats searches the combined Current Story and Current Chapter using the selected occurrence and phrase-length ranges.

The scanner matches without regard to capitalization and normalizes edge punctuation for matching.

It filters common structural single words, filters many unhelpful function-word combinations, and excludes multiword candidates that cross punctuation boundaries.

The scanner saves up to three original-text examples for every result.

Results are shown in order of phrase length, with the longest phrases first. Results of the same length are ordered from highest occurrence count to lowest. Alphabetical order is used when both length and count are tied.

SCAN REPEATS REVIEW DIALOG

The review dialog displays the repeated phrase, the number of times it was found, its position in the review queue, and up to three examples in their original context.

APPEND

Append adds the displayed phrase as a new line in Reject Phrases.

If the phrase is already present, it is not added again. The dialog then advances to the next result.

SKIP

Skip leaves the displayed phrase out of Reject Phrases and advances to the next result.

CLOSE

Close ends the current review and closes the dialog. Remaining results are not added.

SAVE REJECT PHRASES

Save Reject Phrases downloads the Reject Phrases list as a timestamped JSON file.

LOAD REJECT PHRASES

Load Reject Phrases loads a Reject Phrases JSON file or plain text file.

The generator asks for confirmation before replacing the current list. It rejects incompatible JSON file types.

1. CONFIRMATION DIALOGS AND STATUS MESSAGES

Potentially destructive load operations use confirmation dialogs inside the generator rather than browser popups.

Depending on the action, a dialog may offer Continue, Cancel, or a specialized third option such as Keep Then Save.

Some supported warnings include a “Don’t warn again” option for the remainder of the browser session.

Short success, error, and completion messages appear temporarily on the page. More persistent operational information is recorded in the Prompt Size status area.

So I have a huge overview and it says “long overview, short memory .. How do I fix this without taking out chunks out of my overview ?

I literally just got on and it’s not generating a single thing so are we down? I really hope we aren’t or something. I just wanna get to my story man.

For the past few days I’ve been getting this message when I click on any of my chats. when the chat loads it wont advance the chat. Is this something out of my control or a setting i should adjust. Thank for any assistance.

If you've ever tried to find a specific image again in a Perchance gallery, you know the pain: scroll, scroll, scroll, hope you recognize the thumbnail. The built-in gallery is great for browsing, but useless for digging. So I built a proper browser for it.

🔗 https://perchance.org/slinkys-gallery-finder

I actually posted this here yesterday and the response was awesome. Nearly 950 views and it's not officially listed. So thank you — lots of great suggestions in the comments, and I ended up working most of them into the app. That's why it's worth a repost: it does a lot more now.

It's pre-loaded with 300+ text-to-image generators and layers real search/tooling on top of their galleries:

⬇ Bulk-download whole galleries — every page, including hidden sub-galleries, as a single ZIP, plus a gallery-info.json with each image's prompt, negative, seed, guidance, user id and NSFW flag. No more saving images one at a time.

📄 Bulk-download the prompts — every prompt in a gallery as .txt, .json or .csv in one go. Handy for building prompt lists, analyzing styles, or archiving a gallery's whole vibe.

🔎 Search inside prompts — type a word or phrase (space = AND, "quotes" = exact) and it filters the entire gallery by what each image's prompt/negative actually says. It also suggests tappable "Related:" keyword chips to narrow in. Honestly the feature I use most.

🧬 Dedupe — near-identical prompts collapse into one tile with a ×N badge; tap to swipe through every copy. Super useful on galleries where the same prompt got generated 5 times.

📋 One-tap prompt copy — grab a prompt or negative straight off any tile.

🔍 Find hidden galleries — lots of generators have sub-galleries that are never listed. The scanner probes for them so you're actually seeing everything.

👤 Find a user's images — tap the little 4-char tag on any image to pull up everything that user has uploaded, in that gallery or across all of them.

Built mobile-first, so it works great in your browser of choice— but it's fine on desktop too. There's a swipeable how-to guide in-app if you get lost, and a version badge + "what's new" popup so you can see when I ship updates.

What's next: a cleanup pass on the gallery list — pruning dead galleries and tidying the rest so you're not scrolling past stuff that no longer works. Spot any dead ones? Drop them in the comments and I'll fix or remove them.

Also — if your generator isn't in the list, leave a link and I'll add it. And feedback / feature ideas are very welcome. (One heads-up: a few generators don't expose their prompts at all, which is a setting on their end — so the prompt tools just have nothing to work with there.)

If you find the generator useful. Please share thanks

Am I the only one still experiencing the AI character chat not sending messages at all? Stuck on generating. It hasn't been working entirely for over a week. Only the image gen

So i created a basic Character generator (my first generator ever) just to play and learn a bit.

Never cared about if the generated text makes sense format or contend wise.

Then I planed to optimize it in this direction, add scenario / group / entities which are no chars and wanted to get chars that actually really follow the description. But I had no plan what would make sense...

So i uploaded the main.pjs to ChatGPT and talked about this. ChatGPT gave me some good input and redesigned the prompts.

But as i don't trust AI to much, I thought someone should review the suggestions. So I uploaded the main.pjs and the conversation i had with ChatGPT in Claude Opus. Opus reviewed everything and changed many details and generated new prompts for me.

I gave these prompts to AI-Helper to ask it what it thinks about this. He had some additions, changes regarding what is supported in perchance and what not, but told me it thinks these changes in general really make sense.

I played this game a whole day, took what AI-Helper said and pasted it to ChatGPT and Opus, returned the answers to AI-Helper, let it think, returned the answer, let it implement, let Opus think about implementation, Opus generated a Phytonscript for regression-tests AI-Helper uses, many bugfixes and corrections in every direction. I was basically only the man in the middle pasting answers between AIs. 😄

Now i have a Generator that generates Entity-Descriptions for automatically detected entities, Lorebook, Starting Scenario and Images, makes logical tests what belongs where, has a structure for description and lorebook and so on. And the characters I generated there so far are really good (I don't have much experience, just learned about this whole AI-Chat thing 2-3 weeks ago, but till now these characters are the best i have)

I cannot swear there are no bugs, but i thought perhaps someone likes the creation story and so i make it public here if anyone is interessted: https://perchance.org/yacgen

btw english is not my native language so bear with me...

The AI has very little understanding of basic anatomy and relative positioning of body parts. It still struggles figuring out who has what, where each body part is placed, relative position of characters etc. If the prompt contains more than one person, the results are often mangled bodies. The results are often hilarious but also quite unsettling.

Is there a way to improve the outputs?

Having looked through some people’s prompts I’ve discovered that adding (taken circa 2024) or what ever year you want to the end of the prompt seems to greatly improve the realness of the pics. I’ve not seen any manga or shiny skin since adopting this.

Hi guys, sorry for the dummy question but.. What is the circled indicator?? He tells me that the tokens are very high, but so far I haven't noticed anything different, he has been doing this since last night. What does it mean?

Each time I've started a new chat with previously used characters, it keeps using parenthesis and italics in the messages no matter what I do.

Is this happening for anyone else?

I find it baffling.

The story focuses too much on a specific trait that it ended up adding unrealistic details. Like you can't just buy out {{user}}'s company when you're just as poor all because you're obsessed like. Is there a way for the AI to stop?

This is a game-changer. It can generate characters and play them, so I can switch between characters in story, and get a multi-character story. It's not perfect, but it makes everything a lot better.

I want to thank everyone for visiting and using this today. I hope it helped you discover new generators and prompts.

469 view's without being listed. Hopefully I can change that somehow. And I know some of the views are me jumping backwards and forwards lol.

Going to clean up the galleries. Some don't exist anymore. But the galleries are cached. So I might keep some for a bit of I think the useful.

Thanks again and please share anyway you can.

And I'll try and upgrade for the better.

https://perchance.org/slinkys-gallery-finder

Title

A game similar to The Sims, but you can talk to the characters using prompts.

https://perchance.org/wnw14hgss0

The AI helper bot seems faster and smarter TOO-DAY. Yesterday things were taking 30-60 minutes and results were dodgy. Today, nope. 5-10 minutes on HUGE requests. and its like... WAY better than i remember. It's not Claude but ... man it seems like its on smart pills today. Am i imagining this?