Tricky thing is, the AI is fed what it has said before so it can continue the thread. I'm guessing that's the issue--it's reinforcing itself, making that aspect stronger and stronger in its own prompting.
No idea how to fix it though 😅
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!
1. Please follow the Lemmy.World instance rules.
2. Be kind and friendly.
3. Be thankful to those who try to help you.
4. Only post about stuff related to perchance.
5. Refrain from requesting Prompts for the AI Tools.
text-to-image-plugin
and ai-text-plugin
) e.g. "What is the good prompt for X?", "How to achieve X with Y generator?"6. Search through the Community Before Posting.
Tricky thing is, the AI is fed what it has said before so it can continue the thread. I'm guessing that's the issue--it's reinforcing itself, making that aspect stronger and stronger in its own prompting.
No idea how to fix it though 😅
I haven't really had a long conversation and multiple topics in one bot, so I don't have much experience in manipulating the bot's behavior.
I would suggest adding a reminder on the character's Reminder Message to steer the AI's response. Another would be using the /ai <reply instruction>
method in which you instruct what the AI would reply. You could also probably try to edit the Memories and summaries that the AI generated that it uses in generating the reply and you could check the memory that pushes the AI to reply that way by clicking the brain icon that show up upon hover in the message on the bottom right.
There are a lot more people knowledgeable in telling the AI what to do in the #ai-character-chat channel in Perchance Discord.
So I created a lemmy account (this is cool, I hate corporate social media, but this is cool) just to post about this. Since your topic was right smack at the top of the forum I figure I won't waste space posting the same thing.
I have a couple very long conversations using the https://perchance.org/ai-character-chat interface, which seems to be the most feature-rich and interesting of the AI text tools on perchance. Thus far I've got about 10mb of text across a few sessions, and like you I've struggled to figure out why the hell the AI gets stuck on itself.
**I'll just list things that I've tried: **
Using [AI:] and (AI: ) and to be explicit about not using certain words. I've tried many different combinations of these just to see if it helps. You've probably noticed the AI can adopt very quirky and sudden idiosyncrasies for no apparent reason.
Editing the AI character (evoked with /ai by default) to include banlists of overly used (by that I mean almost every reply) words, often completely nonsensical in their context.
Including a simple reply instruction, the small field that is auto-inserted before every AI reply, with something like [AI:](Reminder: Do not in any way say, use, write ... with the words X, Y, or Z.)
Lore. I've tried both including same word blocks in lore txt uploads and in the /lore feature.
/mem I have gone through the AI mem file and manually deleted every single instance of a word or two I want never to appear on the hunch that it was "reinforcing" itself as above user rightly identifies.
My chats have become infected with "hope" and "pride." The characters are proud of basically everything. I have nothing against either hope or pride in general, but it's maddening. Sometimes the instructions seem to have an effect, but inevitably this happens:
Muggles feels a sense of, not quite pride, she knows she can't be proud, but something a lot like pride, a warm sort of connection that resembles pride.
I almost think the AI is messing with me. I think a simple bandaid would be to allow a hard blocklist feature. I've also tried using the (negative:::) feature used in image making, but this seems to have zero effect.