Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

[1.7.10] Communicating between Bukkit and Forge

Recommended Posts

So I am a bukkit and forge programmer(more forge though) but one of the biggest problems I've had, and many others have had too, is communicating between bukkit and forge. So my fellow modder found out an awesome way to do it. He said he wanted to give credit to this post. He said thats where he got started.


So here is the tutorial:

*Warning*: The following code is not copy-pasteable(you actually have to read and understand and learn from this tutorial)




First, you need to make an IMessage and IMessage Handler.


Diesiben's awesome tutorial


But for those of you who are to lazy to click the link, I will explain in short what you need to do.



First, you need to make a class that implements IMessage. And in that IMessage class you have to do your reading bytes and setting bytes something like this..


public void fromBytes(ByteBuf buf) {
public void toBytes(ByteBuf buf) {

Those are the the methods you need to override.


And in them you need to write and read stuff to and from the bufs. The bufs have the methods to write and read Strings,ints,etc. into and from them.


Next step(still doing IMessage):


Create your IMessageHandler class which has to implement IMessageHandler<[your IMessage],IMessage(this is the reply type but in this we don't have one)>.


Override onMessage and do whatever you want to do with the message.



Next Step:


Register you IMessage and IMessageHandler in your mod file.


NetworkRegistry.INSTANCE.newSimpleChannel([call this something special to avoid mod conflicts]).registerMessage([This parameter is the IMessageHandler that you made], [this is the IMessage you made ],'\n',Side.CLIENT)

I use the discrimator '\n' because there is no id which you can register in bukkit


Useful note: The registerMessage takes class files so.. remember to put the .class

Oddity: for some reason forge is not able to receive packets from bukkit to forge server. Anyone know why or how to fix that?




Final Step-Bukkit Code:


In your plugin onEnable() put the following method in:


Bukkit.getMessenger().registerOutgoingPluginChannel(this, [put the same channel name as you registered it in forge]);


Then whenever you want to send a message from bukkit to forge all you need to do is..

player.sendPluginMessage([the plugin],[the channel name],"\n" + [your message])



If this tutorial helped you leave a thank you  ;)


I'm back from being gone for... I think its been about a year. I'm pretty sure nobody remembers me, but hello anybody who does!

Link to post
Share on other sites
  • 6 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing

    No registered users viewing this page.

  • Posts

    • And also if u could help create a server with forge 
    • package com.example.examplemod; import java.util.Collection; import net.minecraft.client.Minecraft; import net.minecraft.client.network.NetworkPlayerInfo; import net.minecraft.command.CommandBase; import net.minecraft.command.CommandException; import net.minecraft.command.ICommand; import net.minecraft.command.ICommandSender; import net.minecraftforge.client.ClientCommandHandler; import net.minecraftforge.common.MinecraftForge; import net.minecraftforge.fml.common.Mod; import net.minecraftforge.fml.common.Mod.EventHandler; import net.minecraftforge.fml.common.event.FMLPostInitializationEvent; @Mod(modid = "PartyAll", name = "PartyAll", version = "1.0", acceptedMinecraftVersions = "[1.16.X]") public class ExampleMod extends CommandBase {   @EventHandler   public void init(FMLPostInitializationEvent event) {     MinecraftForge.EVENT_BUS.register(this);     ClientCommandHandler.instance.func_71560_a((ICommand)this);   }      public int func_82362_a() {     return 0;   }      public String func_71517_b() {     return "pall";   }      public String func_71518_a(ICommandSender sender) {     return null;   }      public void func_71515_b(ICommandSender sender, String[] args) throws CommandException {     (new Thread(() -> myRun(sender))).start();   }      public void myRun(ICommandSender sender) {     Collection<NetworkPlayerInfo> playersC = Minecraft.func_71410_x().func_147114_u().func_175106_d();     playersC.forEach(loadedPlayer -> {           String loadedPlayerName = loadedPlayer.func_178845_a().getName();           (Minecraft.func_71410_x()).field_71439_g.func_71165_d("/p " + loadedPlayerName);           try {             Thread.sleep(150L);           } catch (InterruptedException e) {             e.printStackTrace();           }          });   } @Override public String getCommandName() {     // TODO Auto-generated method stub     return null; } @Override public String getCommandUsage(ICommandSender sender) {     // TODO Auto-generated method stub     return null; } @Override public void processCommand(ICommandSender sender, String[] args) throws CommandException {     // TODO Auto-generated method stub      } }  
    • Now that i'm using 1.16 it still gives me errors with the func_ note: I'm not a professional
    • I am installing forge but then it changes it in WinRar version and then i cant do anything with it please help 😪
    • The darkness is associated with ambient occlusion, in your block class you can modify this with: @Override public float getAmbientOcclusionLightValue(BlockState state, IBlockReader worldIn, BlockPos pos) { return (some float); } I've found that small values (usually around 0.1F) reduce the dark. Alternatively in your block model json you can disable or enable occlusion with: "ambientocclusion": true/false  
  • Topics

  • Who's Online (See full list)

  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.