It is as the OP said on their edit. The temperature and other fields are not sent on the JSON that is sent to the backend server. If one checks it through the browser console, it only has the final prompt that is sent to the AI and some other fields, but none that the OP edited. Very likely this is having no effect at all.

The AI Text Plugin has a section where it takes only specific attributes. It is possible to change it to take these into account and add them to the JSON, but it would not matter anyway if the Perchance backend server does not use them.

Props to GrumblePuss for explaining how the AI works perfectly. It doesn't save anything, it will get overwhelmed eventually and a new field on ACC is just text that gets added at a specific location in the final prompt the AI receives.

This is an example what I refer to as a "final prompt", which is what the AI actually receives when a message is requested.

So, as you can see, no field does anything magic of any sort. It is just placed somewhere in the wall of text the AI receives and how it interprets things is up to it.

Needless to say, that there are a lot of models out there. ACC only works with Perchance, but there are other AI chat platforms with the same or better capabilities out there.

SillyTavern allows you to connect to any API through its API key or to models you can run locally in your computer. It has almost all the same features and there is also a community that makes extensions to provide more functionality. It also provides you a lot of customization for the final prompt and explicitly shows you token information such as how many you are using.

It doesn't commit the sin of ACC, which is to truncate the character descriptions violently without letting the user know, making them wonder why their 6400+ long description char does not have its description being used properly.

I've switched to SillyTavern using Gemini 2.5 Pro or 2.5 Flash and haven't looked back ever since. My lore alone is like 10k tokens at this point, more than what ACC can handle in its entirety and Gemini absorbs and uses it without a sweat.

Of course, you can't use these big boy corpo AIs if you play around with NSFW content, which is not my problem as I have no interest in that. If that's your case, then running locally or waiting for the new model is your best bet.

The Perchance AI chat can be run on Perchance only. But there are many alternatives out there such as SillyTavern or Talemate. Both can either connect with AI models through API keys or if you run locally.

I don't really have much to add since most of your suggestions are reasonable and valid.

One thing I must say is that in my experience, 90% to 95% of the user base actually uses ACC for NSFW and sexual stuff with their characters lmao, and not narrative driven RP with lore rich stories and long dramas. At least for most of discord and reddit this is what I see. Last one that wasn't was a user that had images and nice lore about a black ooze on Reddit. I even wished more people were interested in this sort of use for AI Chats as I'd be interested in sharing and reading stories, but it seems to be a rarity.

Still, without accurate data, we can only guess what people actually use it most for.

The image upgrade was much better than I was expecting, so at least we can be hopeful the new model will be just as good and provide good uses for both ACC and specific use cases like AI RPG (which also might need improvements to match ACC's features).

Some of these suggestions are related to the interface itself (ACC), not the model (AI) that runs on the server. Modding ACC's features are possible since the code is open for anyone to edit. The rest will be only significantly improved when the model is upgraded.

In my view, ACC is more of a generic platform to chat with the bots in several separate threads, not really one that is focused solely on being an RPG adventure (like AI RPG for example). Something like this might be a different goal than what ACC intends to be. An upgrade to AI RPG with these features would sound more appropriate, I believe.

That is why AI Dungeon is called that, it is focused on a specific type of AI roleplay and usage. ACC is a general chatting platform, and more advanced users have tools available to modify it to their use case, similar to SillyTavern, for example.

Most of the AI problems you mentioned have to do with the low context window (6k tokens) it has. It's not able to ingest that much information, so unless it is properly curated with what is happening, the AI will miss things and details. Many other models on the market have immense context windows, from 64k or 128k to 1 million (or so Google claims). Until the text model is upgraded, the best you can do is curate the information available to it (past messages, summaries, character descriptions and General Writing Instructions are the most important).

Now, about the AI issues, let's start with chars not leaving the scene. I faced this problem a lot more with narrator characters or using a single character. One thing to keep in mind is that the description of the main AI of the thread is always sent to the AI on every message. So, if you're having an actual character as the main AI, even if they left the scene, their description is always sent. This can cause the AI to keep referring to them, especially if their description is long.

I started using a narrator character (more of a "hub" character just to host common lorebooks and other things) and never posted as them, but with my main chars. This description was always sent to the AI and improved the narrative instead, but on very rare occasions it would still refer to them as "The Narrator".

Using multiple chars made this a lot more consistent, and the AI was able to read previous messages to better decide what was their status. Had a long 2v2 battle between chars, and once two of them died, they stayed dead, had no issues there. Make sure to always track your summaries and memories to avoid wrong information being fed to the AI.

I eventually found out multiple chars in the same thread causes all their descriptions to be sent (for the chars that posted on the last 20 messages), so this made the AI receive more information about them instead of it being only collected from previous messages or only occasionally retrieved if on the lorebook (which has a low limit of how many entries can be retrieved).

Perchance uses an old text model, curating the information, understanding its limitations, and knowing what information it's receiving helps improving you dealing with it better and improving your experience. You'll have to micromanage? Sure, but the AI is not magical, it has limitations that can become apparent after a while unless you work around them. There are several tricks available like using character injection or hidden system messages.

Eventually, I decided to code a script to adjust which char description was sent, so that I could conserve tokens and also better indicate that a character has left the immediate area. This solved the problem of chars being mistakenly referred to as if they were still around. It is available on my fork that VioneT posted, at the options bar on the bottom right.