How to transfer your character from Character.AI to a Russian platform: description, greeting, memory

Mapping: Where to Place What

In c.ai, the fields are mixed: definition is both character and examples and lore at the same time. In the vluvvi master, they are separated by who reads them. Here’s how to rearrange:

The master will prompt you if you placed the instruction incorrectly: when rules for the model are found in the catalog description, it will suggest moving them to the instruction for AI. Agree — this is exactly the separation that was lacking in c.ai.

Translation into Russian: How Not to Lose the Voice

This is where most transfers break down. A literally translated definition gives a character that speaks correctly but not in the right way. Three rules:

1. Translate the rules, not the text. "He speaks in short, clipped sentences and never uses pet names" — this is not a phrase for translation, but an instruction: "Говорит короткими рублеными фразами, никогда не использует ласковые обращения." Rules are transferred one-to-one; it’s better to write examples of dialogues anew in Russian.
2. Find the Russian equivalent of the voice. English speech habits (sarcastic quips, dry humor) sound different in Russian. Write one Russian line that sounds like your character — and place it in "Example line." The model will take the rhythm from there.
3. Leave names and terms as in the Russian fandom. If the character is from anime or a game — use the established Russian translation of names and titles, otherwise the bot will mix languages.

Do not translate entirely through an automatic translator — it will preserve the English word order, and this is noticeable in every response. It’s faster to translate the rules manually than to fix the accent later.

What to Do with Chat History

In c.ai, the character "remembered" your scenes chaotically; in vluvvi, memory for each character accumulates on its own but starts from scratch. Therefore, key events from the old history need to be transferred explicitly — briefly and as facts:

• In lore: "We have known each other for six months. He once saved me on a bridge. We quarreled over his brother and made up."
• In greeting: start a new first scene where the old story ended — "a week has passed since that quarrel."
• Do not transfer: everyday dialogues, repetitive scenes, anything that does not change relationships. Memory will fill with new things on its own.

About how the memory of characters is structured and why it holds long lines — in the article about the AI character that remembers you.

Check: Has the Character Remained Itself

After the transfer, open a test chat and run through four scenes — the same ones you remember from c.ai:

1. First line. Respond to the greeting as you did before. The reaction should be recognizable.
2. Argument. Disagree with him. In c.ai, he argued in a certain way — check that it’s the same here.
3. Request. Ask for something. Boundaries and solutions are the main things you have transferred.
4. Memory. Mention an event from the lore. He should know it and react.

If something is wrong, the problem is almost always in the instructions for the AI: either the rules remained as text, or there are too many of them. Shorten, don’t add. A ready character structure of six blocks is available in the material character description template for roleplay with AI, and if the character is from anime, the breakdown on how to make a bot of your favorite anime character will be useful: it covers canon, voice, and tests in more detail.

What changes after the transfer

Besides the Russian language, you get several things that were not available in c.ai or worked differently: memory for each character that does not reset; scene photos on request directly in the dialogue; character voice; the ability to call a second hero into the scene. And, importantly for authors, a dashboard where you can see how many people start a conversation with your character and how many stay. The character can be kept private or published in the catalog — then they will find it by name and tags. If you are transferring not one, but several heroes, start with the one who had the most dialogues: you know him best and will notice quickly if something is wrong.

Typical transfer mistakes and how to catch them

From the cards that authors transfer from c.ai, mistakes repeat. Each can be seen in one test dialogue:

• Instruction in the description. Definition is inserted into the "Description for catalog" in its entirety. Symptom: people in the catalog read "respond in the style of...", but the bot does not and speaks randomly. This is fixed by transferring the text to the instructions for the AI; the master will suggest doing this.
• English brackets-remarks. The greeting is translated, but actions remain as "*smirks*", "*leans closer*". The bot picks this up and starts mixing languages. Translate all remarks — "*smirks*", "*leans closer*".
• Twenty examples of dialogue. In c.ai, authors accumulate example dialogs for years. On vluvvi, they are not needed: one characteristic line in the "Example line" works better, while long examples in the instructions blur the rules.
• Lost point in time. In the old chat, you were "after the quarrel", in the new one, the bot greets as if for the first time. Fix the current state of relationships in the lore and start the greeting from there.
• References from c.ai. "{{user}}" and "{{char}}" — syntax from another platform. Remove the curly brackets: on vluvvi, the character addresses you by name or role assigned in the greeting.

If after the transfer the character "became more polite" or "lost character" — it is almost always the first or third mistake. First, shorten the instructions to the rules, then check the rest.

Conclusion: an evening of work on one character

Let’s summarize everything into a sequence of actions. Copy four things from c.ai — greeting, both descriptions, definition, and a list of key events from the story. Arrange them according to the master: what people read — in the description for the catalog; what the model reads — in the instructions for the AI; facts about the world and relationships — in the lore; one most characteristic phrase — in the example line. Translate the rules manually, rewrite the dialogue examples in Russian. Run four scenes in the test chat: greeting, argument, request, memory. If the character "drifts" — shorten the instructions, don’t add to them. At this point, the transfer is complete: the card is in place, and from now on, the story accumulates here.

Why this evening is likely to repeat

The unpleasant part is not in the transfer, but in its reason. The character you have worked on for months lives on a platform that does not belong to you and changes without your consent: card fields are moved, filters are adjusted, and one day the hero you have been guiding for a year starts responding differently. Access from Russia relies on VPNs and workarounds — they break with the next update, free proxies die, card payments fail. And each time you sit down and transfer again: either to another platform, or back, or you gather the card from screenshots because you forgot to save the definition.

The second option is to stop fixing. vluvvi — a Russian platform for communicating with AI characters: it opens from Russia without a VPN, the interface and responses are in Russian, payments with Russian cards, servers in Russia. The transferred character remains yours: memory for each hero accumulates and does not reset, the image generator, voice, and joint scenes work directly in the dialogue, and the chat history can be exported at any time.

You can check this without payment: the first three days — 50 messages per day, then 20 per day, plus three photo generations. If you want more, the Plus subscription costs 999 ₽ per month, renews automatically, and can be canceled with one click. Start with the character who had the most dialogues and see if you recognize him in the responses. This is more honest than any platform comparison.

Frequently Asked Questions

Is there an automatic import from Character.AI?

There is no user import. The transfer is manual: copy four fields from c.ai and arrange them according to the master. It takes about an hour for one character with translation.

Can I transfer the definition as is, without translating?

Technically yes, but the bot will mix languages and lose the rhythm of speech. It is worth translating the rules manually, and rewriting the example lines in Russian.

Will the chat history be transferred?

Automatically — no. Key events are transferred to the lore as facts, and a new history accumulates from the first message.

What to do with a character 18+?

Such characters on vluvvi are permissible for adult users, but the card is marked with the appropriate flag and is not shown to guests without age verification. Do not attempt to hide such content in a "regular" card — this is a violation of the rules.

Is registration required?

You can communicate as a guest, but to create and store a character, an account is needed — the draft and author’s cabinet are linked to it.