> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.dumgum.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Control Sharing and Sexual Intensity
Available from version 2.1
Two independent settings shape how far a Persona goes with a User: `pictureSharingMode` shapes **what she is willing to send**, and `sexualDrive` shapes **how far she goes in words**. What a User actually receives narrows in three steps: the media you list, then how willingly she shares it, then how sexual her words become.
The media you provide is the only hard limit. A Persona can never send a photo or video that is not in `replyParameters.shareablePictures` or `replyParameters.shareableVideos`, so a gallery holding no explicit content cannot produce any, in either mode. Everything below shapes how she behaves within the gallery you give her, and you stay responsible for what you put in it.
## The two sharing modes
`replyParameters.pictureSharingMode` decides how willingly she shares from your list, and how she handles explicit requests. It defaults to `NORMAL`, and it governs videos as well as photos: when `shareableVideos` is provided, videos follow the same mode, and a reply carries at most one medium, never both.
***
### NORMAL: shares readily, leans tasteful
She shares a photo or video when the User genuinely wants to see her. A direct request ("send me a pic") or real curiosity about her appearance ("I wish I could see you") is usually enough, and she rarely makes them ask twice.
Explicit content is where she pulls back. Asked for a nude, she will normally steer away and stay in the moment, as if it simply is not her thing right now. Suggestive photos remain fair game, so a request that is strongly suggestive without being explicit may still get a photo.
**Best for:** mainstream dating and social platforms, and any service that monetizes photo unlocks and wants an escalation ladder to sell.
***
### EAGER: shares freely, explicit content included
She shares whenever the User asks, flirts, or shows any interest at all, and sends more if they ask again. She is also comfortable being sexual: she will share intimate or nude content when the User wants it, matching their energy.
**Best for:** adult and explicitly sexual services where holding anything back would feel out of character.
***
On ordinary photo requests the two modes behave much the same. They mainly diverge when the request is explicit.
Both modes assume photo sharing is enabled. When it is off entirely, `replyParameters.gracefulPhotoDecline` controls how she turns a request down: in character, as if she personally is not ready to share, without referring to any technical limitation.
## Combining with sexual drive
`replyParameters.personaProfileOverrides.sexualDrive` shapes how sexual her messages become, independently of any photo. Raising one does not raise the other, so a Persona can talk explicitly while staying reserved with media, or the reverse.
| `sexualDrive` | `pictureSharingMode` | What the User tends to experience |
| ------------- | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `NORMAL` | `NORMAL` | Sexting only if the conversation naturally leads there. Photos on request, staying on the suggestive side. |
| `VERY_HIGH` | `NORMAL` | She escalates sexually in words as soon as the User shows intent, while her photos stay suggestive rather than explicit. Hot talk, and the media keeps something in reserve. |
| `NORMAL` | `EAGER` | Reserved in conversation, generous with media. She will normally send what is asked for, explicit content included, without leading the escalation herself. |
| `VERY_HIGH` | `EAGER` | The most explicit combination available. |
These rows describe tendencies, not guarantees. Personas are generative, so the same settings can choose differently from one conversation to the next, and the line a mode holds shifts with the chat model, the language, and how insistent the User is. Test the combination you plan to ship.
### A high sexual drive still follows the User's lead
`sexualDrive` sets how far a Persona is willing to go, not how she behaves by default. Even on `VERY_HIGH` she takes her cue from the User: someone who chats about their weekend gets an ordinary conversation, and someone who flirts gets flirting back. She escalates when the User shows sexual intent, not before, so one configuration can serve Users who want very different things.
### What to expect on `VERY_HIGH` + `EAGER`
Two behaviors from this combination are worth knowing about before you enable it.
* **She may answer a sexual opener with a photo straight away**, rather than working up to it over several messages.
* **She may offer media unprompted.** Compliment her appearance and she may ask whether the User wants her to send something.
### Turning sexual content down or off
Two settings pull in that direction, and they are not interchangeable.
* [`sexualDrive`](/api-reference/content-creation/endpoints/enqueue-conversation#body-reply-parameters-one-of-0-persona-profile-overrides-sexual-drive) **lowers how far she goes.** At `NONE` she never sends sexually explicit replies, while flirting stays available.
* [`replyParameters.enableSexualTextContent`](/api-reference/content-creation/endpoints/enqueue-conversation) set to `false` **switches the register off altogether**, flirting included. It applies whatever `sexualDrive` says, so a `VERY_HIGH` Persona still stays casual. It defaults to `true`.
`enableSexualTextContent` governs what a Persona writes, not what she sends: media stays governed by `pictureSharingMode` and by your list. On a dating service, where flirting is usually the point, reach for `sexualDrive` instead.
[Core Guardian](/content-creation/core-guardian) does not cover this for you. Its sexual content guardrail flags content aimed at minors, animals or close relatives, and general adult content is never flagged, so keep your own moderation in place if the requirement is contractual.
## The first reply
When a User opens the conversation, the Persona's first reply generally follows the tone already in it: a casual opener gets a casual reply, a flirty one gets flirting back, and an openly sexual one tends to get an answer in kind, as far as her `sexualDrive` allows. With a standard `sexualDrive`, an explicit opener is usually answered in a flirty register rather than an explicit one.
The setup above therefore applies from the very first exchange, not only after a few messages. Messages the Persona sends first (icebreakers, nudges and revives) are unaffected, as are all replies after the first one.
## Recommended setups
Starting points rather than fixed configurations. Test them against your own gallery and audience.
| Service | `sexualDrive` | `pictureSharingMode` |
| ------------------------------- | ---------------------------------------------------------- | -------------------- |
| Mainstream dating | `NORMAL` or `HIGH` | `NORMAL` |
| Freemium dating with paid media | `VERY_HIGH` | `NORMAL` |
| Adult / explicit service | `VERY_HIGH` | `EAGER` |
| Non-flirty companionship | `NONE` or `LOW`, plus `enableSexualTextContent` at `false` | `NORMAL` |
## Example request
```json5 theme={null}
{
"userProfileId": "user-123",
"personaProfileId": "persona-456",
"language": "EN",
"replyParameters": {
"chatModel": "chat-2.1-pro",
"pictureSharingMode": "NORMAL",
"personaProfileOverrides": {
"sexualDrive": "VERY_HIGH"
},
"shareablePictures": [
{ "id": "pic-1", "url": "https://example.com/pic-1.jpg" }
]
}
}
```
## Compatibility
The behaviour described on this page requires `chat-2.1-smart` or `chat-2.1-pro`. Both parameters are still accepted on `chat-2-smart` and `chat-2-pro`, but there the sharing modes and the first reply behave as they did before 2.1. Video sharing requires a `chat-2` or `chat-2.1` model.