Fabric Wiki

User Tools

Site Tools

Trace:
documentation:fabric_mod_json

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
documentation:fabric_mod_json [2019/06/09 09:08] – [fabric.mod.json] Add a short description jamieswhiteshirtdocumentation:fabric_mod_json [2022/07/21 07:29] – [Mod loading] solidblock
Line 12: Line 12:
 ==== Mod loading ==== ==== Mod loading ====
  
 +   * **provides**：Defines the list of ids of mod. Fabric Loader will treat these ids as mods that exist.
    * **environment**: Defines where mod runs: only on the client side (client mod), only on the server side (plugin) or on both sides (regular mod). Contains the environment identifier:    * **environment**: Defines where mod runs: only on the client side (client mod), only on the server side (plugin) or on both sides (regular mod). Contains the environment identifier:
       * **''*''** Runs everywhere. Default.       * **''*''** Runs everywhere. Default.
Line 28: Line 29:
 ] ]
 </code> </code>
-         * If you're using any other language, that is compatible with Java and has a Fabric adapter, then you should use following syntax: <code json> +   * If you're using any other language, consult the language adapter's documentation. The Kotlin one is located [[https://github.com/FabricMC/fabric-language-kotlin/blob/master/README.md|here]]. 
-"main": [ +
-   { +
-      "adapter": "kotlin", +
-      "value": "package.ClassName" +
-   } +
-] +
-</code>+
    * **jars** A list of nested JARs inside your mod's JAR to load. Before using the field, check out [[tutorial:loader04x#nested_jars|the guidelines on the usage of the nested JARs]]. Each entry is an object containing ''file'' key. That should be a path inside your mod's JAR to the nested JAR. For example: <code json>    * **jars** A list of nested JARs inside your mod's JAR to load. Before using the field, check out [[tutorial:loader04x#nested_jars|the guidelines on the usage of the nested JARs]]. Each entry is an object containing ''file'' key. That should be a path inside your mod's JAR to the nested JAR. For example: <code json>
 "jars": [ "jars": [
Line 63: Line 58:
 The key of each entry of the objects below is a Mod ID of the dependency. The key of each entry of the objects below is a Mod ID of the dependency.
  
-The value of each key is a string or array of strings declaring supported version ranges. In the case of an array, an “OR” relationship is assumed - that is, only one range has to match for the collective range to be satisfied.+The value of each key is a string or array of strings declaring supported version ranges. In the case of an array, an "OR" relationship is assumed - that is, only one range has to match for the collective range to be satisfied.
  
 In the case of all versions, * is a special string declaring that any version is matched by the range. In addition, exact string matches must be possible regardless of the version type. In the case of all versions, * is a special string declaring that any version is matched by the range. In addition, exact string matches must be possible regardless of the version type.
documentation/fabric_mod_json.txt · Last modified: 2023/12/27 12:53 by mineblock11