CurseForge · Minecraft mod
FabricComs
A simple utility to help fabric mods communicate between each other
Quick answer
Which FabricComs release should I use?
FabricComs Fabriccom 1.0.0 targets 1.16.1 with Fabric. The project page does not say whether this file belongs on the client, dedicated server, or both. No extra mods listed for this file.
Where it goes
Is FabricComs required on the client, server, or both?
The project page does not say whether this file belongs on the client, dedicated server, or both.
The source does not explicitly classify this release as client-only or server-only.
What else does FabricComs Fabriccom 1.0.0 need?
Fabriccom 1.0.0. Change the file and its required mods may change too.
This file does not list any required mods. Do not add a library just because a different file uses it.
This file does not list any required or optional mods.
Before you install it
Add FabricComs without breaking your instance.
Built for FabricComs Fabriccom 1.0.0. Pick another file and the loader, install side or required mods may change.
- 01
Stick to this file
Use Fabriccom 1.0.0. It targets 1.16.1 with Fabric; another release may have different loader, side or dependency requirements.
- 02
Bring the mods it needs
This file does not list any required mods. Do not add a library just because a different file uses it.
- 03
Put it on the correct side
The project page does not say whether this file belongs on the client, dedicated server, or both.
- 04
Pick the file you checked
Use the “Get this file” button beside Fabriccom 1.0.0. It opens that exact file at the source.
About this project
What does FabricComs add?
This library adds a couple of classes to facilitate communication between fabric mods. These classes are the FabricCommunicator and the FabricCommunication. Both are found in the com.azuredrake.fabriccom package.
for your build.gradle
Maven Repo: https://raw.github.com/curin/fabriccom/maven/
Dependency Line: modImplementation "com.azuredrake:fabriccom:{Version}"
FabricCommunication is simply a data structure to contain messages sent between mods.
FabricCommunicator is what does the real work.
It has a total of 3 Functions:
- RegisterReciever(modID:String, reciever:Function<FabricCommunication, Integer>)
- Send(modID:string, recipient:String, message:String, data:Object)
- SendGlobal(modID:string, message:String, data:Object)
Send and SendGlobal send to one and all receivers respectively. FabricComs registers one reciever under the id test which will simply output the FabricCommunication to the console. This is useful if you want to test to make sure your Send is working properly. It will also output your Communication if you use sendglobal. If the receiver for your message does not exist, the mod will simply output a warning and the message will be lost. It is important to note that you should always be prepared in your receiver to be sent messages which may not be specifically targeted at you and handle them properly.
Both of the send methods have two overrides one without data, and one without data, message, or modID, but a FabricCommunication instead.
RegisterReceiver is important as it is the method that allows you to receive communications. It is suggested to run this in your modInitializer's constructor (all mods construct prior to initialize running)
My hope is that this will make it easier for mods to communicate in ways which are more stable even if the mod they are looking for is not present.
Project description from CurseForge.
Pick your setup
FabricComs by Minecraft version and loader
Choose the version and loader you play, then open the matching release.
Check the dependencies, then try the file in a copied instance before changing a world you care about.
Recent files
FabricComs versions and loaders
Fabriccom 1.0.0
fabriccom-1.0.0.jar
19 Jul 2020
Looking for an older file? The official CurseForge project page is in Resources.