Schema registry

HEMTT

HEMTT Project File

hemtt.jsonhemtt.toml

Validate

Check your file against this schema

Opens the validator with this schema already loaded. Paste your hemtt.json and it validates in your browser — nothing is uploaded.

Validate a hemtt.json → View raw schema

Reference

Fields

Generated directly from the schema, following local $refs, to two levels of nesting.

Field	Type	Description
`name`required	`string`	Long name of your project. default: `""`
`prefix`required	`string`	Prefix used for CBA macros and the release directory name. default: `""`
`author`required	`string`	Author of the project. default: `""`
`version`	`string`	HEMTT will look for ```addons/main/script_version.hpp``` and use it for the version number. If you are not using the CBA project structure or do not have that file you can add a version number in the HEMTT project file. default: `""`
`files`	`array<string>`	HEMTT will copy the files to the release directory after a successful release build. Supports glob patterns. default: `null`
`include`	`array<string>`	HEMTT will include matching relative or absolute paths when building. default: `null`
`exclude`	`array<string>`	HEMTT will exclude matching files when building. default: `null`
`optionals`	`array<string>`	HEMTT will build the specified addons from the ./optionals folder. default: `null`
`folder_optionals`	`boolean`	HEMTT will by default build optionals into their own mod folders, which can be directly launched by the user. This can be turned off to build optional PBOs directly into optionals folder. default: `false`
`skip`	`array<string>`	HEMTT will skip building the specified addons. default: `null`
`headerexts`	`array<string>`	HEMTT will apply specified header extensions to each PBO. Supports templating. default: `null`
`modname`	`string`	HEMTT will use the specified mod name (without @) to form @mod folder. Supports templating. default: `""`
`keyname`	`string`	HEMTT will use the specified key name for .bikey and .biprivatekey names. Supports templating. default: `""`
`signame`	`string`	HEMTT will use the specified signature name as part of the full signature (.bisign) name. Supports templating. default: `""`
`sigversion`	`integer`	HEMTT will use the specified signature version. Currently Supported: V2, V3 (Experimental). default: `2`
`reuse_private_key`	`boolean`	If set to true, HEMTT will use (and reuse) releases/keys/{keyname}.biprivatekey. It will be generated if it doesn't exist. The default behaviour is to generate a new private key each time and discard it immediately. HEMTT strongly default: `false`
`postbuild`	`array<string>`	— default: `null`
`prebuild`	`array<string>`	— default: `null`
`releasebuild`	`array<string>`	— default: `null`
`scripts`	`object`	— default: `null`

Audit

What we found in this schema

Declared draft: draft-07
Validates cleanly against its own meta-schema.
28 properties, 75% carrying a description, max nesting depth 7.

Standards

Specification sections for the keywords in this schema

Keyword	Document	Section
`$id`	JSON Schema Core, draft 2020-12	§8.2.1 — The "$id" Keyword
`$ref`	JSON Schema Core, draft 2020-12	§8.2.3.1 — Direct References with "$ref"
`$schema`	JSON Schema Core, draft 2020-12	§8.1.1 — "$schema"
`anyOf`	JSON Schema Core, draft 2020-12	§10.2.1.2 — "anyOf"
`default`	JSON Schema Validation, draft 2020-12	§9.2 — "default"
`description`	JSON Schema Validation, draft 2020-12	§9.1 — "title" and "description"
`enum`	JSON Schema Validation, draft 2020-12	§6.1.2 — "enum"
`examples`	JSON Schema Validation, draft 2020-12	§9.5 — "examples"
`items`	JSON Schema Core, draft 2020-12	§10.3.1.2 — "items"
`not`	JSON Schema Core, draft 2020-12	§10.2.1.4 — "not"
`pattern`	JSON Schema Validation, draft 2020-12	§6.3.3 — "pattern"
`properties`	JSON Schema Core, draft 2020-12	§10.3.2.1 — "properties"
`required`	JSON Schema Validation, draft 2020-12	§6.5.3 — "required"
`type`	JSON Schema Validation, draft 2020-12	§6.1.1 — "type"

Documents

JSON Schema Core, draft 2020-12 — JSON Schema: A Media Type for Describing JSON Documents, A. Wright, H. Andrews, B. Hutton, G. Dennis, Eds., 2022. draft-bhutton-json-schema-01. An expired Internet-Draft with no formal standing in the IETF standards process; it is nonetheless the specification of record for JSON Schema 2020-12, published by json-schema.org.
JSON Schema Validation, draft 2020-12 — JSON Schema Validation: A Vocabulary for Structural Validation of JSON, A. Wright, H. Andrews, B. Hutton, Eds., 2022.
RFC 8259 (STD 90) — The JavaScript Object Notation (JSON) Data Interchange Format, T. Bray, Ed., 2017. The format a schema describes.
RFC 6901 — JavaScript Object Notation (JSON) Pointer. Defines the pointer syntax used by $ref fragments and the ~0 / ~1 escapes.

Source

Attribution

This schema comes from SchemaStore, distributed under the Apache License 2.0. Copyright 2015–present Mads Kristensen and contributors. View the original file. The field table and audit on this page are generated by JSONTools.tools; the schema itself is unmodified.

← All schemas