lemonilia commited on
Commit
932c10d
1 Parent(s): 7a1f2a7

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +13 -11
README.md CHANGED
@@ -62,12 +62,12 @@ long) character description made in the style of the various fandom wikis on the
62
  character name as the first line.
63
 
64
  You can refer to the included [Charlotte model card](https://huggingface.co/lemonilia/Limamono-Mistral-7B-v0.3/blob/main/Charlotte.png)
65
- for an example on how characer descriptions can be formatted, but another option is also taking a
66
- hint from the semiempty model output in text-generation-webui or other text completion UIs (note that
67
- you'll likely need to add the _trigger phrase_ for the model to generate text as intended from scratch).
68
- The model will generally output **wiki-style** character sheets in that way. Changing details at the
69
- beginning will affect the rest of the generated sheet. There's no fixed format for it, but the
70
- training data generally followed a pattern similar to this example:
71
 
72
  ```
73
  {{char}}
@@ -94,18 +94,19 @@ of the chat.
94
 
95
  ### Message length control
96
  Inspired by the previously named "Roleplay" preset in SillyTavern, like with LimaRP it is possible to
97
- append a length modifier to the instruction sequences in this way:
 
98
 
99
  ```
100
  ### Response: (length = medium)
101
- {{char}}: {utterance}
102
 
103
  ### Input: (length = tiny)
104
- {{user}}: {utterance}
105
  ```
106
 
107
  This has an effect on bot responses, but as of now it might not always reliably work. The lengths
108
- using during training are: `micro`, `tiny`, `short`, `medium`, `long`, `massive`, `huge`.
109
 
110
  However, it is recommended **not** to use a length modifier at all for character responses, except as a
111
  _temporary measure_ for increasing message length in case they become too short.
@@ -114,7 +115,8 @@ On the other hand, it is suggested to add `(length = tiny)` or `(length = short)
114
  `### Input:` sequence, in order to help the model follow more closely its training data.
115
 
116
  ## Prose style
117
- Only Novel/Forum RP style is supported.
 
118
 
119
  ### Style details
120
  - Narration does not have any delimiter.
 
62
  character name as the first line.
63
 
64
  You can refer to the included [Charlotte model card](https://huggingface.co/lemonilia/Limamono-Mistral-7B-v0.3/blob/main/Charlotte.png)
65
+ for an example on how characer descriptions can be formatted, but another option would be taking a
66
+ hint from the semiempty model output in `text-generation-webui` or other text completion UIs (note that
67
+ you'll likely need to add the _trigger phrase_ for the model to generate text as intended from scratch);
68
+ the model will generally output **wiki-style** character sheets in this way. Changing details at the
69
+ beginning of the sheet will affect the rest of the generation. There's no fixed format for it, but the
70
+ training data generally follows a pattern similar to this example:
71
 
72
  ```
73
  {{char}}
 
94
 
95
  ### Message length control
96
  Inspired by the previously named "Roleplay" preset in SillyTavern, like with LimaRP it is possible to
97
+ append a length modifier to the instruction sequences in this way. Note that the length modifier
98
+ should be placed with a space _after_ the colon:
99
 
100
  ```
101
  ### Response: (length = medium)
102
+ {{char}}: [utterance]
103
 
104
  ### Input: (length = tiny)
105
+ {{user}}: [utterance]
106
  ```
107
 
108
  This has an effect on bot responses, but as of now it might not always reliably work. The lengths
109
+ used during training are: `micro`, `tiny`, `short`, `medium`, `long`, `massive`, `huge`.
110
 
111
  However, it is recommended **not** to use a length modifier at all for character responses, except as a
112
  _temporary measure_ for increasing message length in case they become too short.
 
115
  `### Input:` sequence, in order to help the model follow more closely its training data.
116
 
117
  ## Prose style
118
+ Only the Novel/Forum RP prose style is supported, meaning that narration should always be in third
119
+ person and past tense, and that dialogue lines should always be wrapped with quotation marks.
120
 
121
  ### Style details
122
  - Narration does not have any delimiter.