-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spigot server support #37
Comments
Hey thanks - glad that you like the mod. |
It wasn't gonna be a fork (the API is to different, a fork wouldn't work). It was gonna be a server-side rewrite that implements the protocol. |
any update? |
Nope |
同求,BBOR Mod有CraftBukkit插件,可以参考它的代码去写一个(Purpur用户没有这玩意是真的难受) |
Thanks for the tip. I'll have a look at this |
if I have time, I will do it like bbor |
https://github.com/LeavesMC/Leaves/blob/master/patches/server/0060-Syncmatica-Protocol.patch |
它的意义何在呢,现有的协议已经实现了你所说的全部功能,我认为你需要仔细阅读源码以后再来提问。 |
服务器从来没有进行解包,服务器只存储客户端发来的数据。 |
我没看懂你的意思 并且我认为issue不是一个聊天的好地方 |
我想表达的是MixinClientPlayNetworkHandler.Class中 @Inject(method = "onCustomPayload", at = @At("HEAD"), cancellable = true)
private void handlePacket(final CustomPayloadS2CPacket packet, final CallbackInfo ci) {
if (!MinecraftClient.getInstance().isOnThread()) {
return; //only execute packet on main thread
}
ActorClientPlayNetworkHandler.getInstance().packetEvent((ClientPlayNetworkHandler) (Object) this, packet, ci);
} 这个方法它并没有接收到,来自spigot的PluginChannel的数据包,导致无法通讯,而我使用Fabric Api,它可以接收到来自spigot的插件通道的数据包 |
视乎是通道需要注册的原因吧,具体我也不清楚 |
很高兴你找到了方法但是有两个问题 |
https://github.com/bunnyi116/fabric-syncmatica The plugin has been implemented, because the original author did not register the plugin channel, so it cannot communicate with the plugin channel, which is the branch I modified. Note: I don't know if there is an error!! Currently the test is up and running. |
It would be great if this mod had the ability to install it on the Spigot server (or a derivative, such as Paper). I may work on this myself, although I think it would probably be better as a separate repository.
The text was updated successfully, but these errors were encountered: