AI Chat & Roleplay (online, free, no sign-up, unlimited)
perchance.org
A completely free & simple roleplay AI / "Character AI" chat using Perchance's new AI text generation feature - chat with AI characters. Just create a character and a scenario for the chat/roleplay, and send a message. A simple roleplay AI chat bot with no login/sign-up needed - completely free! No account needed 😌 It's fast and has no limits on daily usage. Can do basically any character/scenario type - stories, anime characters, warrior cats roleplay, funny/silly/cute/wholesome, friend/companion/romantic/boyfriend/girlfriend AI/chatbot, movie and TV show characters - if you can describe it, then you can probably create your own chat bot for it. Basically a CAI / Character AI alternative. This AI chat has no filter, so 18+ chat content can be produced if the character/chat scenario is NSFW. You can define restrictions, or lack thereof via the character's description.

Hello. This is my first post here.

I’ve been playing around with the Ganyu AI Chat-Bot for roleplay and I’ve been enjoying it, but for some reason, I just got hit with a few of these: “An error has occurred somewhere in your code (in lists or HTML): An unhandled promise rejection occurred: QuotaExceededError: The quota has been exceeded.”

Along with the “This Page Has Errors” when I try to load what I have saved before it happened. I got around it by pasting in what my characters have said one at a time, but it’s a bit tiring. If anyone can help me out, I’d appreciate it because I don’t want to start over the story I made with this chat-bot.

  • @perchanceMEnglish
    2•4 days ago

    Hmm, this error is related to your device’s storage limits - since chats are stored on your device rather than on a server. Is your device’s storage nearly full? Or is your chat massive (i.e. multiple novels worth of text in the chat logs)? If you could paste chat logs into a character counter, and let me know, and also let me know the device/OS and browser you’re using (e.g. Samsung A50 + Chrome, or iPhone + Safari), that would be helpful so I can try to replicate this error on my end.