Sponge Mixin configuration

Configuration file for SpongePowered's Mixin library

*.mixins.json

Validate

Check your file against this schema

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

Validate a *.mixins.json → View raw schema

Reference

Fields

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

Field	Type	Description
`parent`	`string`	The name of a parent configuration that options get inherited from
`target`	`string`	Target selector. Either the specifies the phase directly or use "@env(PHASE)" separated by '&', '\', or ' '
`minVersion`	`string`	Minimum version of the mixin subsystem required for this configuration
`compatibilityLevel`	`string`	Minimum compatibility level required for mixins in this set
`required`	`boolean`	Determines whether mixin failures in this configuration are considered terminal and stop the game
`priority`	`integer`	The priority of this configuration. Will be inherited if smaller than 0 default: `-1`
`mixinPriority`	`integer`	Default mixin priority for this configuration. Will be inherited if smaller than 0 default: `-1`
`package`required	`string`	The target package where the mixin classes reside
`mixins`	`array`	Mixin classes to load in all environments. Class names get prepended with the specified package
`client`	`array`	Mixin classes to load ONLY on client. Class names get prepended with the specified package
`server`	`array`	Mixin classes to load ONLY on server. Class names get prepended with the specified package
`setSourceFile`	`boolean`	Sets whether targets' source files will be updated to the mixin source file
`refmap`	`string`	The path to the reference map resource to use for this configuration
`verbose`	`boolean`	Increases log detail level from DEBUG to INFO default: `false`
`plugin`	`string`	Name of the mixin config plugin to use for this config
`injectors`	`object`	Injection options
`injectors.defaultRequire`	`integer`	Sets the default minimum of injections that must be successfully applied per injector default: `0`
`injectors.defaultGroup`	`string`	Sets the default injector group default: `"default"`
`injectors.injectionPoints`	`array<string>`	Registers injection points for this configuration
`injectors.maxShiftBy`	`integer`	Sets the maximum allowed number of opcodes that can be shifted in @At annotations. This is hard capped at 5 default: `5`
`overwrites`	`object`	Overwrite options
`overwrites.conformVisibility`	`boolean`	Sets whether the visibility of overwritten methods should be conformed to the target class
`overwrites.requireAnnotations`	`boolean`	Sets whether overwriting methods must explicitly be declared through @Overwrite annotations default: `true`

Audit

What we found in this schema

Declared draft: draft-07
Validates cleanly against its own meta-schema.
23 properties, 91% carrying a description, max nesting depth 6.

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"
`default`	JSON Schema Validation, draft 2020-12	§9.2 — "default"
`description`	JSON Schema Validation, draft 2020-12	§9.1 — "title" and "description"
`items`	JSON Schema Core, draft 2020-12	§10.3.1.2 — "items"
`maximum`	JSON Schema Validation, draft 2020-12	§6.2.2 — "maximum"
`minimum`	JSON Schema Validation, draft 2020-12	§6.2.4 — "minimum"
`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