![]() ![]() Similarly to CATEGORY tags, certain Entry tags require specific values in their name attribute for the game to pick it up. The actual text that appears in the game will be written between the opening and closing tag for the Entry. You can place as many Entry elements as you wish inside each CATEGORY element.For instance, the main menu description is required to be within a category named CustomStoryMain. Certain CATEGORY tags require a specific value in the "Name" attribute.Inside the LANGUAGE element, you can place as many CATEGORY elements as you wish, but ensure that every opening tag is always accompanied by a closing tag.This element should only occur once in the entire file. The file MUST start with the opening tag and it MUST end with the closing tag.All text within this file is CASE SENSITIVE, meaning if you write "language" instead of "LANGUAGE" it will not work.There are a few rules to keep in mind when it comes to this file: Hello, this is the description of my story. You can start by pasting in the following: This includes things like descriptions, pop-up text, notes, item names, level names etc. This is another XML file that stores ALL text that will be displayed in your story. Start by creating a new plain text file in your custom story folder named extra_english.lang. ![]() In the image to the right you may notice it says "No description." This is the fallback text that appears if you do not have a functional language file, so let's create that now. Now that you have a functional custom story, it's time to add some other essential files. Match the name and extension and place the file next to your config, and it should render as the background image in the game menu.
0 Comments
Leave a Reply. |