this post was submitted on 10 Mar 2026
5 points (100.0% liked)

Perchance - Create a Random Text Generator

1806 readers
5 users here now

⚄︎ Perchance

This is a Lemmy Community for perchance.org, a platform for sharing and creating random text generators.

Feel free to ask for help, share your generators, and start friendly discussions at your leisure :)

This community is mainly for discussions between those who are building generators. For discussions about using generators, especially the popular AI ones, the community-led Casual Perchance forum is likely a more appropriate venue.

See this post for the Complete Guide to Posting Here on the Community!

Rules

1. Please follow the Lemmy.World instance rules.

2. Be kind and friendly.

  • Please be kind to others on this community (and also in general), and remember that for many people Perchance is their first experience with coding. We have members for whom English is not their first language, so please be take that into account too :)

3. Be thankful to those who try to help you.

  • If you ask a question and someone has made a effort to help you out, please remember to be thankful! Even if they don't manage to help you solve your problem - remember that they're spending time out of their day to try to help a stranger :)

4. Only post about stuff related to perchance.

  • Please only post about perchance related stuff like generators on it, bugs, and the site.

5. Refrain from requesting Prompts for the AI Tools.

  • We would like to ask to refrain from posting here needing help specifically with prompting/achieving certain results with the AI plugins (text-to-image-plugin and ai-text-plugin) e.g. "What is the good prompt for X?", "How to achieve X with Y generator?"
  • See Perchance AI FAQ for FAQ about the AI tools.
  • You can ask for help with prompting at the 'sister' community Casual Perchance, which is for more casual discussions.
  • We will still be helping/answering questions about the plugins as long as it is related to building generators with them.

6. Search through the Community Before Posting.

  • Please Search through the Community Posts here (and on Reddit) before posting to see if what you will post has similar post/already been posted.

founded 2 years ago
MODERATORS
 

When a message has a saved (kept) image, changing any of the metadata fields like "hidden from AI", "hidden from user", etc. can sometimes cause the saved image to disappear and show as blank. Editing the message text itself seems fine, it's specifically the behind-the-scenes fields that trigger it. The saved image data is still in the database (in customData.__savedImages), keyed by the exact prompt string including the uniqueness tag ((img0:0), (img1:0), etc.). Something in the re-render flow after a metadata update seems to strip or mismatch that key, so the image lookup fails. Worth checking around line 6672 where (imgN:0) tags get stripped for AI context. if that stripping somehow touches the stored message string rather than just a copy, the key would no longer match what's saved in __savedImages. This bug might seem unlikely to hit in normal usage, but there's a pretty natural scenario where it comes up. Say someone generates an image with the intention of deleting it later, but the generation comes out perfect by luck. They decide to keep it but also want to hide the message from the AI so it doesn't see it in the chat context. So it's not a common occurrence. To reproduce: generate an image, keep it, then change any hiddenFrom option on that message and confirm. Sometimes the image will be gone.


Side note: also noticed that clicking the 🖼️ Image button sometimes generates images with a completely empty prompt (example of what gets stored: (img1:0)), resulting in random unrelated images. Didn't check exact cause.

you are viewing a single comment's thread
view the rest of the comments
[–] perchance@lemmy.world 4 points 2 weeks ago

Thanks for your detailed investigation here. I'm not sure, but I think editing "hidden from AI" / etc. is actually just triggering a re-render, which "shows" the issue, rather than actually causes it.

One possibility is that you're using some custom code in that character that (likely via oc.messageRenderingPipeline) purposefully/inadvertantly edits the prompt inside the <image>...</image> tag, which would cause a mismatch.

I was thinking I could match it via a heuristic like just checking (imgN:0) if the initial __savedImages exact-prompt-match fails, but I think that would mean editing the message to change an image prompt wouldn't work - i.e. it'd just load the stale one rather than loading the new one. I could maybe make imgN increment for any prompt that's manually edited, but I haven't thought that through fully and my suspicion is that that gets a bit iffy. I think we do need to keep exact-match, and if so, then any custom code that 'renders' a message (oc.messageRenderingPipeline) shouldn't touch anything inside <image> tags. Same goes for custom code that edits the actual content of a message of course.

sometimes generates images with a completely empty prompt

Thanks! Fixed.