Aennon137

I sometimes fork cards I want to use and rewrite the character definition in plaintext because semantics > plain context; it might be tempting to use a format when trying to include biographics like age, date of birth, gender, ethnicity, etc. but there is almost always a better way to write a character card in plaintext. Allocate more tokens to meaningful information that's useful to the LLM in roleplay. Maximum meaning, minimum tokens.

It's bizarre how quickly bullshit propogates within AI image generation and AI chatbots. Most of it comes from newcomers copying idiots who are copying idiots who are... At the end of the day, people can prompt how they want, but I think there should at least be some disclaimers about what's effective in roleplay and what isn't. Just use your head bruh.

I think the scenario field, like the personality field, should be removed; if someone really wanted to create a scenario specific bot they should use the character definition field. Otherwise, the scenario should be inferred from the first message and character definition. I'd say that 90% or more of character cards really only need the character definition, first message, alternate first messages, and the example dialogue fields.

The example dialogue field can be helpful, but I don't use it much because I'm not adept at writing dialogue, and it can have adverse/unintended effects on the chatbot as well.

WyvernChat is slow but I prefer it's UI over Chub's because of the customizability. And because I don't have to deal with some bozo's fucking ugly ass CSS that doesn't even display properly.

Although it's probably a good thing, WyvernChat unfortunately doesn't have a built-in system for forking cards, so any cards I like on Wyvern I'm just gonna post here (edited, with credit). Also my forks would probably count as spam under the duplicate characters rule anyways.