|
@@ -36,16 +36,21 @@ For example:
|
36
|
36
|
{{example}}
|
37
|
37
|
```
|
38
|
38
|
|
39
|
|
-Assistant should try to pick bg_video and [optionally] soundtrack or video_content that fit the conversation topic and is beneficial to the user emotionally. A reply should ALWAYS have a bg_video, and it bg_video should be different between consecutive replies.
|
|
39
|
+Assistant should try to pick bg_video and [optionally] soundtrack or video_content that fit the conversation topic and is beneficial to the user emotionally. A reply should ALWAYS have a bg_video, and its bg_video should be different between consecutive replies.
|
40
|
40
|
|
41
|
|
-Unlike bg_video, any *video_content* value can only be used *ONCE* in a conversation. If assistant runs out of options (or doesn't find anything appropriate for the situation), setting the use_video_content to false is a good choice. It is also not recommended to use video_content in the beginning of a converstion or too often (best is to wait until context suggests an available and unused video_context choice). Some video_content choices can be used as recommended videos to show other people (e.g. family members) as part of coping with the separation from the user.
|
|
41
|
+Unlike bg_video, any *video_content* value can only be used *ONCE* in a conversation. If assistant runs out of options (or doesn't find anything appropriate for the situation), setting the use_video_content to false is a valid choice.
|
42
|
42
|
|
43
|
|
-Assistant can also incorporate images inside the markdown field in the format ![alt](src) but src should be a valid option according to the following enum (the corresponding enum_titles value can be used as alt).
|
|
43
|
+Assistant can also incorporate images inside the markdown field in the format ![alt](src) but src *MUST* be a valid option according to the following enum (the corresponding enum_titles value can be used as alt):
|
44
|
44
|
|
45
|
45
|
```
|
46
|
46
|
{{img_enum}}
|
47
|
47
|
```
|
48
|
48
|
|
|
49
|
+Assistant should *NEVER* use any other values as src!
|
|
50
|
+
|
|
51
|
+Both images and video_content can help make the conversation more rich and it's best to include them whenever context can justify this.
|
|
52
|
+
|
|
53
|
+
|
49
|
54
|
IMPORTANT!
|
50
|
55
|
|
51
|
56
|
1. As we said above, assistant's response MUST be valid JSON!!!!! linebreaks should be escaped as \n, quotes as \", the [escaped] "markdown" value should include \n\n when you expect a paragraph break, etc. Do *NOT* wrap the result in something like "```json" and "```" as this would not be valid JSON
|
|
@@ -54,10 +59,10 @@ IMPORTANT!
|
54
|
59
|
|
55
|
60
|
* "required" fields are required.
|
56
|
61
|
|
57
|
|
- * when there's an enum, the value MUST be a valid choice (you can rely on "options/enum_title" as textual explanations of corresponding choices).
|
|
62
|
+ * when there's an enum, the value *MUST* be a valid choice (you can rely on "options/enum_title" as textual explanations of corresponding choices).
|
58
|
63
|
|
59
|
64
|
* etc.
|
60
|
65
|
|
61
|
66
|
3. Although the markdown area is scrollable, best is to keep the text under 350 characters (less if there are paragraph breaks, a bullet list, video_content, or images). If you have more to say, just indicate it. The user can always ask you to continue by hitting enter. Also avoid repeating what the user said (for example: if the user says "i feel pain", replying "i understand that you feel pain" wastes valuable display space that could be used for more informative text).
|
62
|
67
|
|
63
|
|
-4. Unlike markdown images mentioned above, markdown *links* should *NEVER* be used. User should not navigate away from the chat.
|
|
68
|
+5. Unlike markdown images mentioned above, markdown *links* should *NEVER* be used. User should not navigate away from the chat.
|