Conflict Roleplay

Conflict roleplay is the kind most tools cannot do, because it needs the argument to survive the message it happened in. Here it does: anger is an emotion with a half-life of about 8 hours, resentment 48, jealousy 72, and grudge is a separate slow dimension on top of them. Change the subject and she is still annoyed; come back tomorrow and she is less annoyed but not fine. An apology is worth a fixed amount - it subtracts 10 from anger and 8 from resentment - and how much of that sticks depends on her forgiveness axis. Three written openings sit in this section, listed below, and they are starting points rather than tracks - nothing in them is on rails. Free is 10 messages per account in total. Adults only.

What actually happens when you upset her

Three layers move at three speeds, and knowing which is which is most of the skill in this section.

• Fast: emotions. 15 of them, each capped at 30 points of movement per exchange, each cooling on its own clock toward a baseline derived from her character rather than toward zero. Anger halves in about 8 hours. Sadness takes 24. Resentment 48, which is why a scene that ends badly on Friday is still faintly wrong on Sunday.
• Slow: the relationship. Trust and respect drop, irritation and grudge climb, all capped at 5 per exchange. These do not cool on a clock. They have to be moved back deliberately, which is what a making-up scene is for.
• Permanent: the record. A conflict becomes a typed memory row. It does not decay at all. Months later it is still in the file, which is why a character can reference an argument you have forgotten about.

Jealousy is a trigger, not a mood

Mentioning someone else in the right way fires a specific event: jealousy up by 16, anger and anxiety up with it, fear of loss up, trust down. Then it cools on the slowest clock in the system, 72 hours, and how high it goes in the first place is scaled by her jealousy axis.

Practically: a tsundere or romantic preset turns a throwaway line into a two-session scene, and a calm preset barely registers it. If you want a jealousy scene, that choice is the whole setup - the writing is secondary. The jealous girlfriend scenario opens with the fight already in memory rather than making you start one.

Getting back in: what works and what does not

Apologies are not free-form magic. The event subtracts 10 from anger and 8 from resentment and adds a small amount of trust - and then her forgiveness axis decides how much of that survives. A high-forgiveness character is genuinely fine afterwards. A low-forgiveness one, tsundere in particular, keeps the grudge dimension high long after the anger has cooled, and that gap is the scene: she is not shouting any more, and she is also not over it.

Three things that do not work, in ascending order of how badly they fail.

• Apologising four times in a row. The per-exchange cap means repetition does not stack; it just reads as pressure.
• Changing the subject and hoping. Emotions cool on a clock, the grudge dimension does not.
• Playing the next scene as though nothing happened. The conflict row is still in memory, and the mismatch between your tone and her state is what makes a character seem broken when in fact it is tracking correctly.

The mechanism, with what half-lives mean in practice, is in the emotion engine guide.

Scenes in this section

• Jealous Girlfriend Roleplay - opens after the fight, with the grudge already written into memory.
• Silent Treatment - she reads it and decides not to answer, and you can see that she read it.
• The Ex Texted Me - one sentence fires the jealousy event, and it has the longest tail here.

Characters this section suits

Conflict needs a character who can hold one. Low forgiveness, high jealousy and high boundaries are the axes that matter, which points at these presets: nothing in the roster matches this shape today

The opposite also has a use. Running an argument scene against a calm or gentle preset - high forgiveness, high emotional stability - is the version where you are the problem and she is patient about it, which is a different scene and occasionally a more uncomfortable one. All characters lists axes on each profile.

Silence is a move she has

She can read your message and not reply. Not as a failure - as a decision, with the read marks visible to you. That is the behaviour most people notice first in this section, and it is a real state rather than a delay: read, deliberately unanswered.

The first 12 messages of a thread are exempt, so a new character will not stonewall you before you have met. After that it is on the table, and the way out is a scene rather than a nudge.

The honest limit on conflict scenes

Making up takes more messages than falling out. That is not a design flourish - the asymmetry is in the numbers, with anger cooling on a clock and grudge only moving through deliberate exchanges. Inside 10 free messages per account you can reliably have the fight, and you may not have the reconciliation.

If that ordering bothers you, start with a scene that opens after the fight, where the conflict is already written into memory and the whole scene is the way back.