FabricMC/fabric
1
0
Fork 1
mirror of https://github.com/FabricMC/fabric.git synced 2024-11-24 16:48:02 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions
fabric/settings.gradle

53 lines
1.4 KiB
Groovy
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
pluginManagement {
repositories {
jcenter()
gradlePluginPortal()
maven {
name = 'Fabric'
url = 'https://maven.fabricmc.net/'
}
mavenLocal()
}
}
build to fabric-api
2019-04-24 13:15:08 -04:00
rootProject.name = "fabric-api"
final module name refactor prior to release, hopefully
2019-05-11 17:48:33 -04:00
include 'fabric-api-base'
Fabric Biomes API (#200) Co-authored-by: Prospector <prospectordev@gmail.com> Co-authored-by: coderbot16 <coderbot16@gmail.com>
2019-07-03 14:53:25 -04:00
include 'fabric-biomes-v1'
19w38b API Fixes (#370) * Fix compilation errors (untested) * Random fixes * Various modded rendering fixes * Restore contract of RenderAttachedBlockView * Bump versions as needed * Add API for BlockRenderLayer * Minor format / name cleanup Will do a more comprehensive pass as part of separate refactor PR * Bump versions not handled earlier * Bump loader/mc bounds for dependent modules * Update fabric-blockrenderlayer-v1/src/main/java/net/fabricmc/fabric/impl/blockrenderlayer/v1/BlockRenderLayerMapImpl.java Co-Authored-By: liach <7806504+liach@users.noreply.github.com> * Update fabric-blockrenderlayer-v1/src/main/java/net/fabricmc/fabric/impl/blockrenderlayer/v1/BlockRenderLayerMapImpl.java Co-Authored-By: liach <7806504+liach@users.noreply.github.com> * Minor clean ups * Improve docs, minor format corrections. * Update MC dependency
2019-09-20 19:50:49 -04:00
include 'fabric-blockrenderlayer-v1'
fabric-climbable-api-v1 - Re-implementing minecraft:climbable on 1.15 (#558)
2020-04-22 04:41:13 -04:00
include 'fabric-climbable-api-v1'
final module name refactor prior to release, hopefully
2019-05-11 17:48:33 -04:00
include 'fabric-commands-v0'
Migrate commands to v1 (#539) * Migrate commands to v1 * Update fabric-commands-v1/src/main/resources/fabric.mod.json Co-Authored-By: liach <7806504+liach@users.noreply.github.com> * Update fabric-commands-v1/src/main/java/net/fabricmc/fabric/api/command/v1/CommandRegistrationCallback.java Co-Authored-By: liach <7806504+liach@users.noreply.github.com> * commands -> command and improved javadoc. * Fix the stragglers * swap dedicated and dispatcher params * Update fabric-command-v1/src/main/java/net/fabricmc/fabric/api/command/v1/CommandRegistrationCallback.java Whoops forgot that one Co-Authored-By: Juuxel <6596629+Juuxel@users.noreply.github.com> * module name order has been restored. Co-authored-by: liach <7806504+liach@users.noreply.github.com> Co-authored-by: Juuxel <6596629+Juuxel@users.noreply.github.com>
2020-04-29 17:05:43 -04:00
include 'fabric-command-api-v1'
final module name refactor prior to release, hopefully
2019-05-11 17:48:33 -04:00
include 'fabric-containers-v0'
include 'fabric-content-registries-v0'
include 'fabric-crash-report-info-v1'
include 'fabric-events-interaction-v0'
include 'fabric-events-lifecycle-v0'
Lifecycle Events V1 [1.15] (#619) * Lifecycle Events V1 Now includes Chunk and (Block)Entity (un)load events * Add some tests to verify worlds are ticking in the log * Lambda boogaloo * Add some docs. Distinguish between a server starting to stop and server which has stopped. * Split up test mods, some tweaks to (block)entity (un)load events. Bind the ServerWorld being closed during shutdown to unload (block)entities. * Shift around a few profiler variables and finalize * Complete the tests, Block entities on server should be reliably tracked now. Entities on the server obviously still need to be wrangled. * Drop Server Entity Unload callback. Believe me, this was a hard decision but it stands on the fact that about 20-40% of entities silently unload without going through the proper "unloadEntity" method in ServerWorld. No amount of debug hacks, double tracking unload events and even replacing the entity maps do not fix this issue. So I have decided to drop this from the feature set. * checkstyle * generic-events -> item-api * Server start -> Server started * Allow getting current server from Lifecycle People have asked for this, but it is not encouraged for obvious reasons. Should be staged well enough to revert if we decide to. * checkstyle lol * update injection name * Checkstyle lol: Redundant modifiers * Add client starting, stopping and stopped callbacks. * Loicenses * Reorganize so each event category has it's own class. Also this collapses the pretty widely reaching interfaces into more specific inner classes to avoid issues with generics. * Some docs and slight name changes * Add start tick callbacks to worlds, server and client * Enhance some client related docs to life cycle * Deprecate for reasons of discouraging singletonish server getter methods in lifecycle * Add some description related to integrated server on server stopping. * Add small test to verify tick starts are right spot of load * Docs and a tiny bit more testing. * Try clarifying client docs * Drop a slightly unnessecary event * Actually call and implement START_SERVER_TICK event * Remove non-existent test * again * Refer to minecraft itself in client lifecycle docs * Refer to Minecraft itself within ServerLifecycleEvents * Remove primary server getters * IJ DO YOU SPEAK RESOLVING IMPORTS (cherry picked from commit c9257e8a11d8361469349f4171263121bb111af7) * Prune the tests that shouldn't exist * Listen here checkstyle you bugger (cherry picked from commit 9701bba4002cec089c9d3738b1f226128078c130) * Split up events to individual interfaces. Make Chunk events use WorldChunk instead.
2020-06-25 17:28:49 -04:00
include 'fabric-item-api-v1'
final module name refactor prior to release, hopefully
2019-05-11 17:48:33 -04:00
include 'fabric-item-groups-v0'
include 'fabric-keybindings-v0'
migrate to fabric-keybindings-v1 and remove builder (#615) * Edited Clone of #244 - Fixed checkstyle issues - Migrated to fabric-keybindings-v1 - Removed sticky keybindings from #244 as it sounds useless and you can just around it by simply adding that functionality yourself, I might add it back if someone can tell me the advantages of sticky keys except bloat - Added a test mod - Added FabricKeyBinding#getBoundKeyOf for getting vanilla bound keys with ease - Renamed `registered` to `automaticallyRegister` as that is more of a better name - Added a couple Objects.requireNonNull validations * Add back StickyFabricKeyBinding as it is in vanilla, did not notice. * Remove extra "key." * Bump to 1.0.0 * build().register() * Remove `register()` Signed-off-by: shedaniel <daniel@shedaniel.me> * Fix test Signed-off-by: shedaniel <daniel@shedaniel.me> * Rename module Signed-off-by: shedaniel <daniel@shedaniel.me> * Fix checkstyle violation Signed-off-by: shedaniel <daniel@shedaniel.me> * major refactor Signed-off-by: shedaniel <daniel@shedaniel.me> * revert some stuff Signed-off-by: shedaniel <daniel@shedaniel.me> * fix build Signed-off-by: shedaniel <daniel@shedaniel.me> * major stuff Signed-off-by: shedaniel <daniel@shedaniel.me> * fix license, of course Signed-off-by: shedaniel <daniel@shedaniel.me> * Add resource loader v0 Signed-off-by: shedaniel <daniel@shedaniel.me> * Let's not break the api. Signed-off-by: shedaniel <daniel@shedaniel.me> * Rename to buildAndRegister Signed-off-by: shedaniel <daniel@shedaniel.me> * resolve reviews Signed-off-by: shedaniel <daniel@shedaniel.me> * Use GLFW Signed-off-by: shedaniel <daniel@shedaniel.me> * Dump the builder entirely Signed-off-by: shedaniel <daniel@shedaniel.me> * Rename to Key Binding Signed-off-by: shedaniel <daniel@shedaniel.me>
2020-06-12 06:18:17 -04:00
include 'fabric-key-binding-api-v1'
Lifecycle Events V1 [1.15] (#619) * Lifecycle Events V1 Now includes Chunk and (Block)Entity (un)load events * Add some tests to verify worlds are ticking in the log * Lambda boogaloo * Add some docs. Distinguish between a server starting to stop and server which has stopped. * Split up test mods, some tweaks to (block)entity (un)load events. Bind the ServerWorld being closed during shutdown to unload (block)entities. * Shift around a few profiler variables and finalize * Complete the tests, Block entities on server should be reliably tracked now. Entities on the server obviously still need to be wrangled. * Drop Server Entity Unload callback. Believe me, this was a hard decision but it stands on the fact that about 20-40% of entities silently unload without going through the proper "unloadEntity" method in ServerWorld. No amount of debug hacks, double tracking unload events and even replacing the entity maps do not fix this issue. So I have decided to drop this from the feature set. * checkstyle * generic-events -> item-api * Server start -> Server started * Allow getting current server from Lifecycle People have asked for this, but it is not encouraged for obvious reasons. Should be staged well enough to revert if we decide to. * checkstyle lol * update injection name * Checkstyle lol: Redundant modifiers * Add client starting, stopping and stopped callbacks. * Loicenses * Reorganize so each event category has it's own class. Also this collapses the pretty widely reaching interfaces into more specific inner classes to avoid issues with generics. * Some docs and slight name changes * Add start tick callbacks to worlds, server and client * Enhance some client related docs to life cycle * Deprecate for reasons of discouraging singletonish server getter methods in lifecycle * Add some description related to integrated server on server stopping. * Add small test to verify tick starts are right spot of load * Docs and a tiny bit more testing. * Try clarifying client docs * Drop a slightly unnessecary event * Actually call and implement START_SERVER_TICK event * Remove non-existent test * again * Refer to minecraft itself in client lifecycle docs * Refer to Minecraft itself within ServerLifecycleEvents * Remove primary server getters * IJ DO YOU SPEAK RESOLVING IMPORTS (cherry picked from commit c9257e8a11d8361469349f4171263121bb111af7) * Prune the tests that shouldn't exist * Listen here checkstyle you bugger (cherry picked from commit 9701bba4002cec089c9d3738b1f226128078c130) * Split up events to individual interfaces. Make Chunk events use WorldChunk instead.
2020-06-25 17:28:49 -04:00
include 'fabric-lifecycle-events-v1'
Loot table manipulation API (#160)
2019-06-09 15:47:28 -04:00
include 'fabric-loot-tables-v1'
final module name refactor prior to release, hopefully
2019-05-11 17:48:33 -04:00
include 'fabric-mining-levels-v0'
include 'fabric-models-v0'
include 'fabric-networking-v0'
include 'fabric-networking-blockentity-v0'
Object builders v0->v1 migration (#537) Co-authored-by: modmuss50 <modmuss50@gmail.com>
2020-04-29 18:44:34 -04:00
include 'fabric-object-builder-api-v1'
final module name refactor prior to release, hopefully
2019-05-11 17:48:33 -04:00
include 'fabric-object-builders-v0'
1.14 Updates and Render Fixes (#394) * Fix EntityRenderDispatcher hook (again) * Add fabric-particles-v1 * Add a sync() method to BlockEntityClientSerializable * Prevent CME due to off-thread block entity updates (#367) * Restore rendering features disabled in first 19w39a release * Remove rendering stuffs no longer needed due to snapshots * Bump versions as needed
2019-09-29 21:21:38 -04:00
include 'fabric-particles-v1'
final module name refactor prior to release, hopefully
2019-05-11 17:48:33 -04:00
include 'fabric-registry-sync-v0'
[#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
include 'fabric-renderer-api-v1'
Fix resource-loader
2019-09-18 18:24:15 -04:00
include 'fabric-renderer-indigo'
Wip 19w39a (#386) * 19w39a fixes (#387) * Bump versions * Breaks: BlockEntityRendererRegistry and EntityRendererRegistry * Remove broken parts of rendering, bump major version * Add renderer-registries, replaces broken parts of rendering api * Slap a band-aid on renderer/Indigo - won't render properly, but runs * Bump distribution versions, add renderer-registries to main build * Clean up blockrenderlayer implementation package name
2019-09-28 21:07:04 -04:00
include 'fabric-renderer-registries-v1'
final module name refactor prior to release, hopefully
2019-05-11 17:48:33 -04:00
include 'fabric-rendering-v0'
fabric-rendering-v1 module & added HudRenderCallback (#359)
2019-12-28 10:29:04 -05:00
include 'fabric-rendering-v1'
[#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
include 'fabric-rendering-data-attachment-v1'
[#111] fluid rendering hooks
2019-05-17 17:24:37 -04:00
include 'fabric-rendering-fluids-v1'
final module name refactor prior to release, hopefully
2019-05-11 17:48:33 -04:00
include 'fabric-resource-loader-v0'
include 'fabric-tag-extensions-v0'
include 'fabric-textures-v0'
fabric-rendering-v1 module & added HudRenderCallback (#359)
2019-12-28 10:29:04 -05:00
include 'fabric-dimensions-v1'
fabric-mining-levels-v0 -> fabric-tool-attribute-api-v1 (1.15 edition) (#460) Moves the ToolManager and tool tags declared in fabric-mining-levels-v0 to a new fabric-tool-attributes-v1, along with adding new interfaces to be implemented on tools so that mining speed, mining level, and entity attribute modifiers can be decided by the itemstack.
2020-04-21 23:30:02 -04:00
include 'fabric-tool-attribute-api-v1'
Reference in a new issue Copy permalink