For example, could convert to a button reading “Let the colonists go”. Add conditions to incoming or existing colonists (injury, radiation sickness etc.)Īll ID’s with a hashtag # refer to a text in a localization file, which are converted to an actual text string in-game.Give more colonists (but not take away).Various content options allow you to tweak sound and 3D models attached to the situation. Triggers enable you to tie the event to a specific time of day, building present in the colony and so on. You can create simple events such as survivors coming over to ask for food or more elaborate ones with several different options and outcomes. Event XML file named “Eventnamehere.event”.This can simply be done by renaming your file, if it ends in. Event XML files should always follow the following naming convention: “Eventnamehere.event”. This document will go over the syntax and everything you need to write an event, even from scratch. Other ready made event examples can be found at the end of this document.Įvery game event requires text for descriptions, sounds, choices and an illustration to put it all together. Use the localization file for adding texts and the pre-existing event can be modified with 'Notepad++ or a similar editor(set language to XML to get color-coded tags). In the pre-existing 'Mod' file you need to add a name, a description and an icon for your mod, as well as input the preferred version number. Once you have your mod tool project ready, you will need a localization file and an event folder that should already be there. Just like any other mod, you first need to do a basic modding setup detailed in Modding:Basics. You can create your own in-game encounters and add them to the game as mods. 1.9 Full event example document (Example.event).
0 kommentar(er)
