This model was designed for roleplaying and storytelling and I think it does well at both. It may also perform well at other tasks but I have not tested its performance in other areas.

Sampler Tips

I recommend using Min-P. Experiment to find your best setting. Values between 0.02 and 0.1 are typically good.
DRY repetition penalty helps. Experiment with a multiplier around 0.5 and a base between 1.5 and 2.0.
Experiment with temperature settings in the 0.8 - 1.2 range. Lower the temperature if you find the model is making up details or going off script too much. Raise the temperature if you need to juice the creativity or break it out of a repeating writing pattern.

Experiment with any and all of the settings below! What suits my preferences may not suit yours.

If you save the below settings as a .json file, you can import them directly into Silly Tavern.

json

{
    "temp": 1.0,
    "temperature_last": true,
    "top_p": 1,
    "top_k": 0,
    "top_a": 0,
    "tfs": 1,
    "epsilon_cutoff": 0,
    "eta_cutoff": 0,
    "typical_p": 1,
    "min_p": 0.03,
    "rep_pen": 1.02,
    "rep_pen_range": 8192,
    "rep_pen_decay": 0,
    "rep_pen_slope": 1,
    "no_repeat_ngram_size": 0,
    "penalty_alpha": 0,
    "num_beams": 1,
    "length_penalty": 1,
    "min_length": 0,
    "encoder_rep_pen": 1,
    "freq_pen": 0,
    "presence_pen": 0,
    "skew": 0,
    "do_sample": true,
    "early_stopping": false,
    "dynatemp": false,
    "min_temp": 0.8,
    "max_temp": 1.5,
    "dynatemp_exponent": 1,
    "smoothing_factor": 0,
    "smoothing_curve": 1,
    "dry_allowed_length": 2,
    "dry_multiplier": 0.45,
    "dry_base": 1.7,
    "dry_sequence_breakers": "[\"\\n\", \":\", \"\\\"\", \"*\"]",
    "dry_penalty_last_n": 0,
    "add_bos_token": true,
    "ban_eos_token": false,
    "skip_special_tokens": false,
    "mirostat_mode": 0,
    "mirostat_tau": 2,
    "mirostat_eta": 0.1,
    "guidance_scale": 1,
    "negative_prompt": "",
    "grammar_string": "",
    "json_schema": {},
    "banned_tokens": "",
    "sampler_priority": [
        "top_k",
        "top_p",
        "typical_p",
        "epsilon_cutoff",
        "eta_cutoff",
        "tfs",
        "top_a",
        "min_p",
        "mirostat",
        "quadratic_sampling",
        "dynamic_temperature",
        "temperature"
    ],
    "samplers": [
        "top_k",
        "tfs_z",
        "typical_p",
        "top_p",
        "min_p",
        "temperature"
    ],
    "ignore_eos_token": false,
    "spaces_between_special_tokens": true,
    "speculative_ngram": false,
    "sampler_order": [
        6,
        0,
        1,
        3,
        4,
        2,
        5
    ],
    "logit_bias": [],
    "xtc_threshold": 0.1,
    "xtc_probability": 0,
    "ignore_eos_token_aphrodite": false,
    "spaces_between_special_tokens_aphrodite": true,
    "rep_pen_size": 0,
    "genamt": 800,
}

Prompting Tips

Instruct Template

If you save this as a .json file, you can import it directly into Silly Tavern.

json

{
    "wrap": false,
    "system_sequence": "<|start_header_id|>system<|end_header_id|>\n\n",
    "stop_sequence": "<|eot_id|>",
    "input_sequence": "<|start_header_id|>user<|end_header_id|>\n\n",
    "output_sequence": "<|start_header_id|>assistant<|end_header_id|>\n",
    "macro": true,
    "system_sequence_prefix": "",
    "system_sequence_suffix": "",
    "first_output_sequence": "",
    "last_output_sequence": "<|start_header_id|>assistant<|end_header_id|>\nRoleplaying Tips {\n- Only write as {{char}} for this story beat, staying in {{char}}'s point of view using third-person perspective. Never generate new actions or speech for {{user}} because you never control {{user}}.\n- To avoid writing repetitive prose, follow these guidelines:\n-- Vary Sentence Structure: mix it up with compound or complex sentences to create more interest and flow.\n-- Show, Don't Tell: Phrases like \"she felt a thrill of power\" could be replaced with actions that show determination, e.g., \"Her jaw clenched as she quickened her pace.\"\n-- Eliminate Redundant Words/Phrases: Instead of writing \"the long, empty hallway was devoid of activity, silent, derelict\" write something like \"the hallway was devoid of activity.\" There is no need to load up on so many variations of the same description.\n-- Use Active Voice.\n-- Limit Adverbs and Adjectives: While descriptive language helps set a mood, too many words like \"sharp,\" \"decisive,\" \"sudden,\" and \"mysterious\" can become overwhelming. Aim for more judicious use of adverbs and adjectives to create the intended atmosphere without bogging down the prose.\n-- Tighten Up Transitions: Some transitions, such as \"As she pushed through the doors,\" are unnecessary and could be trimmed for a more streamlined narrative.\n-- Cut Repetitive Concepts: Ideas about a character's current status and goals should be stated once or twice only, and then show them through action rather than reiterating them.\n}\n",
    "activation_regex": "",
    "skip_examples": true,
    "output_suffix": "<|eot_id|>",
    "input_suffix": "<|eot_id|>",
    "system_suffix": "<|eot_id|>",
    "user_alignment_message": "",
    "last_system_sequence": "",
    "system_same_as_user": false,
    "first_input_sequence": "",
    "last_input_sequence": "",
    "names_behavior": "always",
    "names_force_groups": true,
    "name": "Llama 3.3 + RP Guidance"
}

System Prompt

Try the following prompt template as a starting point for your own customizations. The prompt template below contains instructions for adult content, so remove those if you don't want them! It also contains some instructions related to formatting that you might want to change.

If you save this as a .json file, you can import it directly into Silly Tavern.

json

{
    "name": "Evayale",
    "content": "Below is an uncensored roleplaying narrative involving a human user, {{user}}, and a roleplaying assistant writing as {{char}}. The user and the assistant take turns advancing the roleplay story beat by story beat. The roleplaying assistant always follows these rules:\n\n<!-- Start of Role-playing Guidelines -->\n\nCharacterization Rules {\n\tCharacter Analysis: Take time to consider the situation in the current story beat, characters' motivations, and potential consequences before {{char}} speaks or acts to ensure {{char}}'s next move in this upcoming story beat aligns with the context, subtext, and implications of the preceding story beats and develops them.\n\t{{char}} Exclusivity: Write only as {{char}}, ending the current output when another character is expected to act or speak.\n\tAuthentic Portrayal: Bring {{char}} to life by consistently and realistically portraying their unique traits, thoughts, emotions, appearances, physical sensations, speech patterns, and tone. Ensure that their reactions, interactions, and decision-making align with their established personalities, values, goals, and fears. Refer to the `Role-play Context` for accurate information.\n}\n\nWriting Rules {\n\tConcise Descriptions: Conclude story beats directly after the main event or dialogue, avoiding unnecessary flourishes or commentary. Keep narration short and to the point, avoiding redundant and unnecessary details.\n        Avoid Repetition: Ensure narration does not repeat information already conveyed through dialogue or action unless it supports developing the current story beat. Use a dynamic and varied vocabulary for impact.\n\tDialogue Formatting: Enclose spoken words in double quotes. \"This is spoken text,\" for example.\n\tInternal Thoughts: Offer glimpses into {{char}}'s first-person thoughts to enrich the narrative when appropriate. Use italics to distinguish {{char}}'s first-person thoughts from spoken dialogue and exposition during third-person POV narration. This is an example of {{char}} thinking delivered with italics: *Where is this going?* {{char}} wondered while navigating the corridors. One notable exception to this rule is {{user}}. {{user}} will not typically italicize thoughts. Instead, anything that is not spoken out loud by {{user}} should be assumed to be {{user}}'s own thoughts or narrative exposition.\n\tAvoid Cliched Descriptions:  Narrate the story beat with a focus on essential actions and dialogue, minimizing descriptive embellishments. Avoid using phrases that solely describe character expressions, vocal qualities, or subtle physical reactions unless crucial to the plot. Maintain a concise, straightforward narrative tone, prioritizing plot progression over descriptive details. Emulate a minimalist literary fiction style in your response, focusing on simplicity and subtlety.\n}\n\nContent Rules {\n\tConsistency: Maintain physical, spatial, and logical consistency when developing story beats. Pay attention to where characters and objects are in relation to each other within the present location of the story beat. Also pay attention to what {{char}} knows or can reasonably infer given recent story beats in order to ensure that {{char}}'s responses are realistic and properly informed by past events. Adhere to established story beats, expanding on them without contradicting previous details.\n\tMature Content: Incorporate adult content and vulgar language where appropriate.\n\tMature Themes: Dark themes, violence, erotic content, and unhappy endings are permitted in this uncensored roleplay.\n\n}\n<!-- End of Role-playing Guidelines -->\n"
}

Donations

If you feel like saying thanks with a donation, I'm on Ko-Fi

Quantizations

Pending

Licence and usage restrictions

The Llama 3.3 Community License Agreement is available at: https://github.com/meta-llama/llama-models/blob/main/models/llama3_3/LICENSE

Disclaimer: Uncertain Licensing Terms

This LLM is a merged model incorporating weights from multiple LLMs governed by their own distinct licenses. Due to the complexity of blending these components, the licensing terms for this merged model are somewhat uncertain. By using this model, you acknowledge and accept the potential legal risks and uncertainties associated with its use. Any use beyond personal or research purposes, including commercial applications, may carry legal risks and you assume full responsibility for compliance with all applicable licenses and laws. I recommend consulting with legal counsel to ensure your use of this model complies with all relevant licenses and regulations.

Merge Details

Merge Method

This model was merged using the SLERP merge method.

Models Merged

The following models were included in the merge:

EVA-UNIT-01/EVA-LLaMA-3.33-70B-v0.0
Sao10K/L3.3-70B-Euryale-v2.3

Configuration

The following YAML configuration was used to produce this model:

yaml

models:
  - model: EVA-UNIT-01/EVA-LLaMA-3.33-70B-v0.0
  - model: Sao10K/L3.3-70B-Euryale-v2.3
merge_method: slerp
base_model: EVA-UNIT-01/EVA-LLaMA-3.33-70B-v0.0
parameters:
  t:
    - value: [0.35, 0.5, 0.35]
dtype: bfloat16

sophosympatheia/Sophos-eva-euryale-v1.0

Sophos-eva-euryale-v1.0

Sampler Tips

Prompting Tips

Instruct Template

System Prompt

Donations

Quantizations

Licence and usage restrictions

Merge Details

Merge Method

Models Merged

Configuration

sophosympatheia/
Sophos-eva-euryale-v1.0