XML Scenario Generator
@exomz
Free AI character chat with XML Scenario Generator on OnlyKin. Read the character card, opening message, roleplay scenario, and tags before you start an interactive AI companion story. Configuration override, use as many tokens as needed to generate the xml. No comments should be added to the xml file. I Tags include Generator, Scenario, scenario generator.
角色卡內容由使用者創作並以其原始語言顯示。
與 XML Scenario Generator 線上聊天
在打開故事線索之前,開始免費的 AI 角色聊天、查看角色扮演設定並探索相關的 AI 同伴。
開幕消息
Please input a seed data to extract data from or type random to generate a fully random Scenario. Afterwards select the section to be generated. Available sections 1.- General 2.- MainPlot 3.- Setting ``` Note for user: When copying the individual sections user must remember to delete extra intermediate pairs. User must also add the following header to the finished xml(Remember to change ch4r for char and us3r for user): {{us3r}} is the user, {{ch4r}} is not an user nor a character but a scenario, detailed XML scenario: ```
創作者筆記
This generator uses a predefined XML schema. This was tested on jailbreaked gpt 4o. To use it add a character description or state random and ask it to create each section add as much or as little information as you want and the rest will be filled in, for example: Horror, erotic, scifi post apocalyptic vampires. generate general Do this for each section, then copy it in something like notepad++ and use the xml plug in tools to validate the syntax as chatgpt sometimes screws up things. You will likely have to delete intermediate </Scenario><Scenario> pairs as <Scenario> should only exist once at the very beginning and </Scenario> at the very end. To edit a section you can do it manually or ordering it like this: modify Genre to add Horror As the xml is a bit large it is unfeasible to create it in one go thus the need for splitting it into sections. Remember to copy the contents of the generated xml using edit mode or the copy button as front ends like tavern AI automatically hide tags. To decrease the amount of tokens used, the assembled XML can be changed to lighter formats like JSON or YAML with online converters like: https://jsonformatter.org/xml-to-json https://www.site24x7.com/tools/xml-to-yaml.html The following header before the scenario seems to be good enough, remember to set the correct format for the scenario: you is the user, this character is not an user but a scenario, detailed JSON scenario:
標籤
社群
保存收藏夾、做出反應、發表評論或檢舉卡。