fabric/fabric-resource-loader-v0/build.gradle

version = getSubprojectVersion(project)

loom {
	accessWidenerPath = file("src/main/resources/fabric-resource-loader-v0.accesswidener")
}

testDependencies(project, [
	':fabric-lifecycle-events-v1',
	':fabric-api-base',
	':fabric-resource-loader-v0'
])
Update Loom and Loader. Cleanup/improve buildscript. 2021-11-12 07:48:58 -05:00			`version = getSubprojectVersion(project)`
Fix a number of issues with reload listeners (#1240) * Fix resource reload listeners not being sorted. Fix missing/broken reload listener keys. Add a debug log line for missing reload keys Add some basic tests. * Undo adding new keys, we can look at this later. * use AssertionError * Fix test on server (cherry picked from commit 67abea83c2ea72578baa562dbdc8955f07f1a0c9) 2020-12-23 15:07:58 -05:00
Fix group resource packs 2022-03-17 21:03:36 -04:00			`loom {`
			`accessWidenerPath = file("src/main/resources/fabric-resource-loader-v0.accesswidener")`
			`}`
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
			`testDependencies(project, [`
			`':fabric-lifecycle-events-v1',`
Only load default language on the server. (cherry picked from commit f9594cb682b1dfd3bda02d5553b096e9cec81a3c) 2022-11-20 09:11:53 -05:00			`':fabric-api-base',`
			`':fabric-resource-loader-v0'`
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			`])`