Kit Reference
Context: HL Kit
This section details all of the specific formats and mechanisms used within the Kit. This encompasses all of the different file formats, all the scripting contexts and transitions, required and pre-defined elements, and anything else that requires specification. Click on the various topics below to delve into the details for that facet of the Kit.
IMPORTANT! This section of the documentation is not yet complete. Topics that have been written will be found at the top of the list below and possess live links. Other topics are simply identified by name, sometimes along with a few notes about what the topic will contain. These topics will be added over time to complete the documentation.
XML Details
Most of the basics regarding the Kit's use of XML files and their implications can be found in the section on XML Files. Additional reference details are outlined in the topics below.
Conventions Used Below
The reference section of this documentation utilizes a variety of notational conventions for presenting how things work. This includes the syntax used for data files, as well as the formats for other types of files, which are outlined in the topics below.
Tags and Tag Expressions
Tags are a fundamental building block that a wide range of mechanisms leverage through the Kit. Tags are utilized to identify and classify objects through tag expressions. The following topics delve into the various facets of using tags.
Scripting Language
The types of behaviors that exist within the realm of RPGs is limitless. As such, it's impossible for HL to anticipate everything, so the Kit provides a versatile scripting language that enables data files to adapt to virtually any game system. The scripting language has many facets that you should be familiar with, and the topics below outline the information you'll need.
- Scripting Language Overview
- Language Syntax
- Declaring Variables
- Basic Language Mechanisms
- Flow Control
- Other Language Statements
- Language Intrinsics
- Special Symbols
- Script Macros
- Re-usable Procedures
- Debugging Mechanisms
- Compiler Error Messages
Script Data Access
The majority of your scripts will focus on accessing and manipulating the data managed within HL. This will involving identifying both the structural and visual elements throughout the data hierarchy. The following topics detail the various pieces involved in data access.
IMPORTANT! Be sure you are familiar with the basics of data manipulation before reviewing this content.
- Script Contexts
- Context Transitions
- Target References
- Data Access Examples
- Employing Script Macros
- Script Types
Structure of Data Files
There are a number of different types of files that comprise the data files for a game system. Each of the topics below describes the structure of one of these file types.
Auto-Defined Elements
The Kit automatically defines a variety of different structural and visual elements for use in common situations. These auto-defined elements help to streamline and simplify the authoring process, and they are detailed in the topics below.
- {{fl|Pseudo-Fields}
- {{fl|Auto-Defined Tags and Tag Groups}
- {{fl|Auto-Defined Components and Fields}
- journal, transact, stackable, gear, shortname, etc.
- {{fl|Auto-Defined Component Sets}
- {{fl|Auto-Defined Things}
- {{fl|Auto-Defined Sort Sets}
- {{fl|Built-in Resources}
- {{fl|System Resources}
[TBD]
- Evaluation cycle
- Relative timing of Leads vs. masters vs. minions
- Rules for sequencing of tasks with the same phase and priority
- Visual Elements
- Rules for auto-sizing and default sizing
- Required Elements
- Components
- Component Sets
- Timing report contents and structure
- Skeleton Data Files
- What's provided
- How things work
- Why elements are provided
