FabricMC/fabric
1
0
Fork 1
mirror of https://github.com/FabricMC/fabric.git synced 2024-12-08 15:21:30 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions
fabric/fabric-item-group-api-v1/src/main/resources/fabric.mod.json

39 lines
1.1 KiB
JSON
Raw Normal View History

[#148] Migrate to a modular JAR-in-JAR system, update to Loader 0.4.x
2019-04-23 18:46:23 -04:00
{
"schemaVersion": 1,
22w42a 🐫 (#2599) Co-authored-by: shartte <shartte@users.noreply.github.com> Co-authored-by: Juuz <6596629+Juuxel@users.noreply.github.com>
2022-10-22 15:38:33 -04:00
"id": "fabric-item-group-api-v1",
"name": "Fabric Item Group API (v1)",
[#148] Migrate to a modular JAR-in-JAR system, update to Loader 0.4.x
2019-04-23 18:46:23 -04:00
"version": "${version}",
Add more metadata to the modules (#353) * Add fabric-api-base as a dep to fabric-networking-v0
2019-09-08 19:24:40 -04:00
"environment": "*",
[#148] Migrate to a modular JAR-in-JAR system, update to Loader 0.4.x
2019-04-23 18:46:23 -04:00
"license": "Apache-2.0",
22w42a 🐫 (#2599) Co-authored-by: shartte <shartte@users.noreply.github.com> Co-authored-by: Juuz <6596629+Juuxel@users.noreply.github.com>
2022-10-22 15:38:33 -04:00
"icon": "assets/fabric-item-group-api-v1/icon.png",
Add more metadata to the modules (#353) * Add fabric-api-base as a dep to fabric-networking-v0
2019-09-08 19:24:40 -04:00
"contact": {
"homepage": "https://fabricmc.net",
"irc": "irc://irc.esper.net:6667/fabric",
"issues": "https://github.com/FabricMC/fabric/issues",
"sources": "https://github.com/FabricMC/fabric"
},
"authors": [
"FabricMC"
],
add proper depends lists to mods
2019-05-17 17:08:53 -04:00
"depends": {
22w42a 🐫 (#2599) Co-authored-by: shartte <shartte@users.noreply.github.com> Co-authored-by: Juuz <6596629+Juuxel@users.noreply.github.com>
2022-10-22 15:38:33 -04:00
"fabricloader": ">=0.14.9",
add proper depends lists to mods
2019-05-17 17:08:53 -04:00
"fabric-api-base": "*",
"fabric-resource-loader-v0": "*"
},
Add more metadata to the modules (#353) * Add fabric-api-base as a dep to fabric-networking-v0
2019-09-08 19:24:40 -04:00
"description": "An API for adding custom item groups.",
[#148] Migrate to a modular JAR-in-JAR system, update to Loader 0.4.x
2019-04-23 18:46:23 -04:00
"mixins": [
22w42a 🐫 (#2599) Co-authored-by: shartte <shartte@users.noreply.github.com> Co-authored-by: Juuz <6596629+Juuxel@users.noreply.github.com>
2022-10-22 15:38:33 -04:00
"fabric-item-group-api-v1.mixins.json",
Split client only code into its own sourceset. (#2179) A common source of crashes on modded Minecraft servers comes from modders accidently calling client only code from the client, this PR is another large step towards elimitating that. This PR has been months in the making and years in the planning, requiring major changes to Loom & Loader. In recent Minecraft versions Mojang has made it easier than ever to cleanly split the jar, going against the status-quo of merging the client and server into one jar. From the start we have designed Fabric to have a very clear split between client and common (client & server) code. Fabric has always encoraged keeping client only code seprate from the server, this can be seen at a fundamental level with the entrypoints in Loader. Fabric API's have all been designed with this mind. This PR provides a compile safety net around Fabric API using client only code on the server. Even though there are almost 400 changed files, minimal changes beyond moving the files were required to achieve this in Fabric API, thanks to the effort of all contributors in the past. These changes should not affect modders or players in anyway, a single "universal" jar is still produced. Im happy to awnswer any questions.
2022-05-21 11:26:46 -04:00
{
22w42a 🐫 (#2599) Co-authored-by: shartte <shartte@users.noreply.github.com> Co-authored-by: Juuz <6596629+Juuxel@users.noreply.github.com>
2022-10-22 15:38:33 -04:00
"config": "fabric-item-group-api-v1.client.mixins.json",
Split client only code into its own sourceset. (#2179) A common source of crashes on modded Minecraft servers comes from modders accidently calling client only code from the client, this PR is another large step towards elimitating that. This PR has been months in the making and years in the planning, requiring major changes to Loom & Loader. In recent Minecraft versions Mojang has made it easier than ever to cleanly split the jar, going against the status-quo of merging the client and server into one jar. From the start we have designed Fabric to have a very clear split between client and common (client & server) code. Fabric has always encoraged keeping client only code seprate from the server, this can be seen at a fundamental level with the entrypoints in Loader. Fabric API's have all been designed with this mind. This PR provides a compile safety net around Fabric API using client only code on the server. Even though there are almost 400 changed files, minimal changes beyond moving the files were required to achieve this in Fabric API, thanks to the effort of all contributors in the past. These changes should not affect modders or players in anyway, a single "universal" jar is still produced. Im happy to awnswer any questions.
2022-05-21 11:26:46 -04:00
"environment": "client"
}
Add custom value denoting module lifecycles. (#1253) * Add custom value denoting module lifecycles. * Make the module validation work. My hand has been forced - we must use buildSrc since JsonSlurper is not available in main buildscript. * Apply task to each project and dont cross projects * A horrible hack * Wait what * It works now. * Not needed * Drop unneeded maven repo, cache map lookup (cherry picked from commit daa38b3d8212614c0ab4f4436695acff567d3fb9)
2021-01-19 13:48:09 -05:00
],
22w42a 🐫 (#2599) Co-authored-by: shartte <shartte@users.noreply.github.com> Co-authored-by: Juuz <6596629+Juuxel@users.noreply.github.com>
2022-10-22 15:38:33 -04:00
"accessWidener": "fabric-item-group-api-v1.accesswidener",
Add custom value denoting module lifecycles. (#1253) * Add custom value denoting module lifecycles. * Make the module validation work. My hand has been forced - we must use buildSrc since JsonSlurper is not available in main buildscript. * Apply task to each project and dont cross projects * A horrible hack * Wait what * It works now. * Not needed * Drop unneeded maven repo, cache map lookup (cherry picked from commit daa38b3d8212614c0ab4f4436695acff567d3fb9)
2021-01-19 13:48:09 -05:00
"custom": {
22w42a 🐫 (#2599) Co-authored-by: shartte <shartte@users.noreply.github.com> Co-authored-by: Juuz <6596629+Juuxel@users.noreply.github.com>
2022-10-22 15:38:33 -04:00
"fabric-api:module-lifecycle": "stable",
"loom:injected_interfaces": {
"net/minecraft/class_1761": ["net/fabricmc/fabric/api/itemgroup/v1/IdentifiableItemGroup"]
}
Add custom value denoting module lifecycles. (#1253) * Add custom value denoting module lifecycles. * Make the module validation work. My hand has been forced - we must use buildSrc since JsonSlurper is not available in main buildscript. * Apply task to each project and dont cross projects * A horrible hack * Wait what * It works now. * Not needed * Drop unneeded maven repo, cache map lookup (cherry picked from commit daa38b3d8212614c0ab4f4436695acff567d3fb9)
2021-01-19 13:48:09 -05:00
}
rename: -> fabric-item-groups
2019-04-23 18:27:12 -04:00
}
Reference in a new issue Copy permalink