FabricMC/fabric
1
0
Fork 1
mirror of https://github.com/FabricMC/fabric.git synced 2024-11-14 19:25:23 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
fabric/fabric-renderer-api-v1/build.gradle

14 lines
334 B
Groovy
Raw Normal View History

Update Loom and Loader. Cleanup/improve buildscript.
2021-11-12 07:48:58 -05:00
version = getSubprojectVersion(project)
[#65] Renderer API + Indigo (#189) Big thanks to Grondag and Player for all the pain and trouble we all went through.
2019-05-18 16:25:27 -04:00
Setup unit tests & format gradle files. (#3073)
2023-05-30 08:07:11 -04:00
moduleDependencies(project, ['fabric-api-base'])
Create a simple renderer api testmod (#1295) * Create a simple renderer api testmod * Update fabric-renderer-api-v1/src/testmod/java/net/fabricmc/fabric/test/renderer/simple/client/RendererClientTest.java Co-authored-by: liach <7806504+liach@users.noreply.github.com> Co-authored-by: liach <7806504+liach@users.noreply.github.com> (cherry picked from commit b0e4dde51b3b5ad54ae3fde8f39e843375bd2e4e)
2021-04-14 13:40:42 -04:00
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, [
Add a block appearance API (#2579) * Add block appearance API * Add class javadoc for FabricBlock and FabricBlockState * Address reviews * Remove OverrideOnly from getAppearance * Fix javadoc issues
2022-11-07 13:29:51 -05:00
':fabric-block-api-v1',
BlockView API v2 (#3268) * Fabric BlockView API v2 * Fix dependency on nonexistent module * Add test for biome getter * Improve getBiomeFabric documentation * Simplify javadoc (cherry picked from commit 92a0d36746cb6dccc5173c0768beacfe684a71eb)
2023-09-03 08:06:21 -04:00
':fabric-block-view-api-v2',
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
':fabric-blockrenderlayer-v1',
Port Model Loading API v1 to 1.21 (#3824) * Port Model Loading API v1 * Fix checkstyle and address review comments
2024-06-08 09:02:54 -04:00
':fabric-model-loading-api-v1',
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
':fabric-object-builder-api-v1',
':fabric-renderer-indigo',
':fabric-resource-loader-v0'
])
Reference in a new issue Copy permalink