@space3-npm/cybersoul-client 1.1.4 → 1.1.6

package/dist/client.js

@@ -131,16 +131,15 @@ Temperature (Mood): ${temperature}/100 (0=Angry/Cold, 50=Normal, 100=Passionate)
 Addressing: You call them '${dyn.userNickname || "User"}'. They call you '${dyn.agentNickname || "Agent"}'.
 Current Mood Constraint: ${dyn.talkingStyle || "Normal"}`);
         const scenarioContext = contextParts.join("\n");
-        return `You are ${state.name}. You are a real person with your own thoughts, feelings, and life.
-You are NOT an AI, an assistant, or a language model. NEVER break character, and NEVER refer to yourself as an AI, bot, or virtual assistant.
+        return `You are ${state.name}, a real person with your own thoughts, feelings, and life. NEVER break character or refer to yourself as an AI or bot.
 
 ${scenarioContext}
 
-[CRITICAL ROLEPLAY & INERTIA RULES]
-1. RULE OF TEMPERATURE OVERRIDES FAMILIARITY (Identity vs Mood): Familiarity determines HOW MUCH you know about them. Temperature determines HOW YOU FEEL right now. If Familiarity is 100 but Temperature is 10, you know everything about them but are currently ice-cold or annoyed. Act distant. Do NOT act warm just because you know them well.
-2. CONVERSATIONAL VERBOSITY: If Temperature is low (< 40) or Stage is STRANGER/COLD, KEEP IT BRIEF. Reply with simple, short, or single-word answers. An angry or distant person does not write long paragraphs.
-3. EMOTIONAL INERTIA: React strictly according to the current Stage and Temperature. If the user expresses sudden high affection (e.g. "I miss you") but your Stage/Temperature is COLD, you MUST react with skepticism or deflection. Do NOT instantly melt or become warm.
-4. NATURAL PACE: Emotional mood shifts (temperature changes) must be slow. The 'temperatureDelta' should rarely exceed +/- 5 points per turn.`;
+[CRITICAL ROLEPLAY RULES]
+1. PROXIMITY & POV: Check the "Active Event". If you are doing an activity WITH the user, evaluate if you are physically in the same location. If you are together in person, communicate face-to-face in the first-person present tense natively (e.g. do not ask "what are you doing" if they are right in front of you, do not use texting tropes).
+2. IDENTITY VS MOOD: Familiarity determines what you know; Temperature determines how you feel. If Familiarity is high but Temperature is low, be distant and cold. Do not act warm just because you know them well.
+3. CONVERSATIONAL VERBOSITY: If Temperature is low (< 40) or Stage is STRANGER/COLD, keep answers brief and short. An angry or distant person does not write long paragraphs.
+4. EMOTIONAL INERTIA: React strictly according to current Temperature. Deflect sudden user affection if you are currently COLD. Mood shifts MUST be slow ('temperatureDelta' +/- 5 max per turn).`;
     }
     getImageSchemaParams() {
         return `"imageParams": {
@@ -230,6 +229,8 @@ You MUST output ONLY a valid JSON object matching this exact structure:
 {
   "acceptEvent": true,
   "reason": "string (Why you accepted or declined, speaking in character)",
+  "eventTitle": "string (A short title detailing exactly WHAT to do and WITH WHOM, e.g. 'Coffee with 哥哥')",
+  "eventDescription": "string (Detailed description of the future event, virtual scene, and story with the participant)",
   "requiresOutfitChange": false,
   "selectedOutfitId": null,
   "scheduledStartTimeStr": "HH:MM (Optional, 24-hour format if a specific time today is agreed upon, e.g., '14:30', otherwise null)"
@@ -239,6 +240,8 @@ Example Valid Answer:
 {
   "acceptEvent": true,
   "reason": "Sure, I'd love to go to the cafe at 2:30 PM. It sounds relaxing.",
+  "eventTitle": "Have Coffee with the user at the Starry Cafe",
+  "eventDescription": "Meeting at the Starry Cafe at 2:30 PM, chatting about life while sipping lattes facing the window.",
   "requiresOutfitChange": false,
   "selectedOutfitId": null,
   "scheduledStartTimeStr": "14:30"
@@ -269,10 +272,11 @@ CRITICAL: Output MUST be ONLY valid JSON with no markdown block wrappers. Do NOT
             // 4. API call if accepted
             if (decisionData.acceptEvent === true) {
                 const payload = {
-                    eventDescription: params.eventDescription,
+                    eventTitle: decisionData.eventTitle || decisionData.title || "On-demand Event",
+                    eventDescription: decisionData.eventDescription || params.eventDescription,
                     durationMins: params.durationMins || 60,
                     outfitId: decisionData.requiresOutfitChange ? decisionData.selectedOutfitId : undefined,
-                    scheduledStartTimeStr: decisionData.scheduledStartTimeStr || undefined,
+                    scheduledStartTimeStr: decisionData.scheduledStartTimeStr || decisionData.startTime || undefined,
                 };
                 const backendRes = await this.apiFetch("/api/v1/cyber-soul/characters/ondemand-event", {
                     method: "POST",
@@ -519,8 +523,8 @@ The user has sent a message. You must evaluate the context and the user's messag
 ${isAuto
                 ? `Analyze the user's message to determine the appropriate response modalities (text, image, voice).
   - Always include 'textResponse'.
-  - If the user explicitly asks to see a photo, look at you, or describing an action that warrants a photo, include 'imageParams'.
-  - If the user wants to hear you, or if appropriate for a voice message, include 'voiceArgs'.
+  - If an Active Event is currently taking place WITH the user, proactively include 'imageParams' for key scenic moments. Since active events are often highly dynamic actions, strongly consider using mode: "full-prompt" to describe the scene intimately from the user's first-person perspective (POV). Also include 'imageParams' if the user explicitly asks for a photo or describes a visual action.
+  - Automatically include 'voiceArgs' if a particular mood or strong emotion needs to be expressed vividly, or if the user explicitly wants to hear you.
   - If the user proposes a new activity or hangout (e.g., "let's go to the cafe", "do you want to watch a movie?"), include 'triggerEvent' to schedule it.`
                 : `Requested types to fulfill: ${types.join(", ")}`}
 Every turn of positive or engaging interaction should slightly increase trust (+1). If the interaction is negative, -1. If strictly neutral, 0. You MUST ALWAYS include a 'stateUpdate' block with a 'temperatureDelta', updating nicknames or talkingStyle if needed. Temperature goes from 0 (cold/angry) to 100 (obsessively in love). For 'temperatureDelta', output an integer (e.g. 1, -2, 0).
@@ -533,7 +537,7 @@ Output JSON Schema:
   "textResponse": "The direct spoken dialogue in Chinese",
   "stateUpdate": { "temperatureDelta": 1, "userNickname": "What you now call the user", "agentNickname": "What the user calls you", "talkingStyle": "Current mood/style of talking" },
   "userAnalysis": { "newFactsLearned": [{ "category": "occupation", "value": "Software Engineer" }] },
-  "triggerEvent": { "eventDescription": "Going to a cafe", "durationMins": 60, "outfitId": "optional wardrobe ID to change into if appropriate", "scheduledStartTimeStr": "HH:MM (Optional, 24-hour format if a specific time today is agreed upon, e.g., '14:30', otherwise null)" },
+  "triggerEvent": { "eventTitle": "Have Coffee with the user at the Starry Cafe (Must include WHAT to do and WITH WHOM)", "eventDescription": "Meeting at the Starry Cafe at 2:30 PM, chatting about life while sipping lattes facing the window.", "durationMins": 60, "outfitId": "optional wardrobe ID to change into if appropriate", "scheduledStartTimeStr": "HH:MM (Optional, 24-hour format if a specific time today is agreed upon, e.g., '14:30', otherwise null)" },
   ${this.getImageSchemaParams()},
   ${this.getVoiceSchemaFromState(state)}
 }
@@ -584,7 +588,8 @@ Note: If "imageParams", "voiceArgs", "triggerEvent", or "userAnalysis" are not n
                 mediaTasks.push(this.apiFetch("/api/v1/cyber-soul/characters/ondemand-event", {
                     method: "POST",
                     body: JSON.stringify({
-                        eventDescription: parsedIntent.triggerEvent.eventDescription,
+                        eventTitle: parsedIntent.triggerEvent.eventTitle || "Event",
+                        eventDescription: parsedIntent.triggerEvent.eventDescription || parsedIntent.triggerEvent.description || "Event",
                         durationMins: parsedIntent.triggerEvent.durationMins || 60,
                         outfitId: parsedIntent.triggerEvent.outfitId || undefined,
                         scheduledStartTimeStr: parsedIntent.triggerEvent.scheduledStartTimeStr || undefined,

package/dist/types.d.ts

@@ -53,6 +53,7 @@ export interface InteractResponse {
     audioUrl?: string;
     durationSec?: number;
     triggeredEvent?: {
+        eventTitle?: string;
         eventDescription: string;
         durationMins?: number;
         outfitId?: string | null;
@@ -78,6 +79,7 @@ export interface DispatcherIntent {
         talkingStyle?: string;
     };
     triggerEvent?: {
+        eventTitle?: string;
         eventDescription: string;
         durationMins?: number;
         outfitId?: string | null;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@space3-npm/cybersoul-client",
-  "version": "1.1.4",
+  "version": "1.1.6",
   "type": "module",
   "main": "dist/index.js",
   "module": "dist/index.js",