온라인으로 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:

태그