fabric/settings.gradle

54 lines
1.5 KiB
Groovy
Raw Permalink Normal View History

pluginManagement {
repositories {
jcenter()
gradlePluginPortal()
maven {
name = 'Fabric'
url = 'https://maven.fabricmc.net/'
}
mavenLocal()
}
}
2019-04-24 13:15:08 -04:00
rootProject.name = "fabric-api"
include 'fabric-api-base'
include 'fabric-biomes-v1'
include 'fabric-blockrenderlayer-v1'
include 'fabric-climbable-api-v1'
include 'fabric-commands-v0'
include 'fabric-command-api-v1'
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'
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'
2019-06-09 15:47:28 -04:00
include 'fabric-loot-tables-v1'
include 'fabric-mining-levels-v0'
include 'fabric-models-v0'
include 'fabric-networking-v0'
Fabric Networking API V1 (#1081) * Networking api v1 Some final docs? Licenses and testmod Fix a bunch o imports and make things work for v1 (v0 is bork) Make the testmod pass checkstyle and work Docs for v1 * Deprecate v0 and implement using v1 * Drop files down one package due to package check error * Fix issue with channel registration, add another testmod * jaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaavadoc * Make javadoc use `code`, move impl interface to package access * this things * Rename a few internal methods * Mark all client side stuff client only, move client mixins * Add null checks around the place, clarify some javadoc and method names * Make FutureListeners uninstantiable * Some internal nullable annotations * An impl class I forgot to rename * Some comments and clarify some client login handler javadoc * Add a missing FunctionalInterface annotation * Split play and login, move client stuff to right package * No interface left behind * Inline channel registries in api * Login and play subpackages not needed * Add helper method to create play custom packets * hasGlobalChannel -> hasGlobalReceiver * Just rename the collection method for now * Inline PlayPacketSender into static methods * Start on testmod idea for verifying dynamic registration * Add client login events * You don't say hello when talking to yourself. Also more testmod stuff * Make event names present tense * Some javadoc and impl interface rename * Change the test keybinding * Begin working on dynamic reg * Dynamic reg works, just need a lot of cleanup and reimpling global * A few renames, readd global methods * Try to reduce the amount of duplicate registration logic * Reimplement dynamic accessors * More impl * Start reimplementing global receivers. Still very hacky solution. * Reimplement some server global reciever stuff * Add login init event for server login. * Implement client login query start event * Move event invocations into addon, don't dual register global recievers * Finally reimplement global recievers for all networking phases * A revelation: Send packets properly This also finds the issue with screen getting the proper S2C channels, current on TODO list. * Disconnect event does not need a packet sender * Clarify, add methods to get channels net handler can recieve on client * Unregister actually works now * Bunch of null checks, add simpler login delay test for vanilla clients * Add some debug logging entries, fix unregister on client's session reg * Play channel event javadoc and rename login query handlers * More channel -> channelName * thisening * Introduce the basics infrastructure for tracking global receivers * Add more substantial javadoc to login connection events * Javadoc, reimplement unreg methods on v0, 1 impl fix * Implement tracking for global recievers * Dont forget to start tracked sessions in 3/4 cases * Global receiver docs and move methods in classes * Complete null checks * big boi javadoc part 1 * Finish the main javadoc, usage javadoc is left * Set so has method is not needed * Rename receiveable and sendable methods * Add the two missing private ctors * buildscript update to upstream * Split out player finding stuff to networking player tracking API v1 Signed-off-by: liach <liach@users.noreply.github.com> Forward v0 PlayerStream to new module, add entity track events Rename module to player tracking Well javadoc can make sense Decide on tracking for the name Update fabric-player-tracking-api-v1/src/main/java/net/fabricmc/fabric/api/networking/player/tracking/v1/package-info.java Co-authored-by: Erlend Åmdal <erlend@aamdal.com> Remove exceptions from javadoc that are not thrown javadoc fix again Handle a case where the player manager happens to be null rename player tracking to player lookup Yeet * Cherrypick #1092 * Remove some redundant client networking methods, rename `(un)register` to `(un)registerReceiver` * Simplify access to dynamic reg on client * Param shifting, let users get sender. * Warning about time and distance units * Make sure these are client only * Fix control flow in ClientPlayNetworking#send * Correct example code javadoc * javadoc correction in server login * Put login delay tests behind system property Also remove unnecessary junk added by old module that was merged together. * Fix ordering so channel registrations during `PHASE`_INIT work * Fix prod bug and an oversight * Fix login when connecting to dedicated server * Update registry sync to v0 to prevent issue with reg sync hanging client * this is done (cherry picked from commit fd11873744b4a194f4866f383acb84fca2dd874c)
2020-12-05 14:06:42 -05:00
include 'fabric-networking-api-v1'
include 'fabric-networking-blockentity-v0'
include 'fabric-object-builder-api-v1'
include 'fabric-object-builders-v0'
include 'fabric-particles-v1'
include 'fabric-registry-sync-v0'
include 'fabric-renderer-api-v1'
2019-09-18 18:24:15 -04:00
include 'fabric-renderer-indigo'
include 'fabric-renderer-registries-v1'
include 'fabric-rendering-v0'
include 'fabric-rendering-v1'
include 'fabric-rendering-data-attachment-v1'
2019-05-17 17:24:37 -04:00
include 'fabric-rendering-fluids-v1'
include 'fabric-resource-loader-v0'
include 'fabric-tag-extensions-v0'
include 'fabric-textures-v0'
include 'fabric-dimensions-v1'
include 'fabric-tool-attribute-api-v1'