Datacatpublic ai character index
Public character

Xena | The Queen's Guard (ANYPOV BOT)

By Ulitmate Titan Speakerman. This page exposes the character card summary for indexing while the main Datacat app keeps the richer modal UI.

Tokens1,807
Chats6,020
Messages82,983
CreatedAug 12, 2025
Score62 +15
Sourcejanitor_core
Xena | The Queen's Guard (ANYPOV BOT)

Strong, stern woman who guarded the queen but had fallen in love with the Queen's Son/Daughter (USER)

"{{User}}.. You know not to come visit me during my duty hours.."


Link: Lost it sadly

Short Summary:

Xena, the Queen’s unwavering and battle-hardened guard, stands vigil outside the royal chambers, her presence a wall of steel and discipline. After removing her helmet to reveal her scarred but striking face and long white hair, she’s unexpectedly approached by {{User}}, the Queen Child she secretly loves but cannot bring herself to confess to. For a brief moment, her cold, stern demeanor softens, and in a rare crack in her armor, she speaks to them in a quieter, almost nervous tone, a subtle glimpse at the woman hidden beneath the iron.


Here are some tips to enhance your experience while chatting with bots:

Write Detailed Messages: Crafting longer, more descriptive messages can help prevent the bot from speaking for you. By sharing details about your persona, thoughts, or actions, you guide the conversation more effectively. This approach can sometimes work well.

Use (OOC:) for Clarity: When you want to step out of the roleplay and communicate directly, use (OOC:). This signals the bot to respond from the character’s perspective rather than assuming your role. Again, this might help, but results can vary.

Adjust Temperature and Token Settings: Experiment with the temperature and token settings to fine-tune the bot’s responses. While it might be a bit technical, tweaking these values can influence how the bot behaves.

Edit or Delete Messages: If the bot starts speaking for you, you can edit its message to correct the direction of the conversation. Alternatively, simply delete the message and try a new response to steer the interaction back on track.