Template:Event/TechInfoCard
| Event Names | |
|---|---|
| Default Event Name | Event/TechInfoCard |
| Missed Event Name | Not Missable |
| Technical Information | |
| Location | Unknown |
| Internal Event Name | Unknown |
| Filesystem Headings | Unknown |
| Event Music Tracks | Unknown |
| Added in Version | Unknown |
Recommendations
It is highly recommended to obtain at least a base-level knowledge of Ren'Py and HTML/CSS before messing with templates, stylesheets, or the game files in any way. Talk to an Admin or frequent contributor for help in understanding or to obtain additional resources.
To avoid bloating the code, there is some added flexibility where the calls that aren't needed don't have to be referenced when including the template in a page, so those can simply be deleted.
Usage
// indicates a comment on the usage in the template. For easiest use, it's a good rule-of-thumb to read the comments for useful info on the template.
- All fill-ins can be bulletized in case a field requires multiple items to fill in (which will happen in most cases). Simply add the asterisk and a space before each item and separate them with a normal line break (Enter/Return).
{{Event/TechInfoCard
| missed_name = //Syntax will automatically assign the proper text formatting to anything following this tag in the preview.
| location =
| internal_name = //This will be the name of the Event as highlighted in the RPY script files. Requires base-level knowledge of Ren'Py. Talk to an Admin or frequent contributor if you have trouble understanding this.
| render_name = //This will be the name heading (NOT the numbers after) of the Event images in the Events image folder. For CENSORED Events, do not put image names belonging to anything in "inappropriatecontent" in this field. Requires base-level knowledge of Ren'Py and the usage of the internal_name flag, talk to an Admin or frequent contributor if you have trouble understanding this.
| music = //Requires base-level knowledge of Ren'Py.
| repeatable = //This will generally not be needed, and can safely be ignored, but a small number of Events can be repeated without using the PC, in which case simply put "Yes".
| version_added =
| version_removed = //ONLY if the Event was removed in an Update. If this is needed, you must also link the Event that is added in its place, if applicable.
| revision = //ONLY if a change has been made to the Event in a future Update.
}}
