-
Notifications
You must be signed in to change notification settings - Fork 5
Packet API #18
Comments
This is a great idea. (I wanted to do this for Dimensions.) |
Its a core feature if forge mods are supported to enable plugins to interact with mods via packets. |
I say we keep the packet API as a unsafe API in a special package and as a separate maven dependency if we're going to do it at all. Sort of like |
just put it into a .internal.* package |
yes, and no reflection utilities or anything, just |
Oppose, for portability's sake. Fountain can provide a few things to help, but in general I feel this is best handled outside Fountain. |
We need to have it on foutain other wise people will be digging around with asm and reflection which is not good. |
Putting in the API is a bad idea. We could have it in the the implementation, so if people want to build off a specific version they get that version's Packets. |
Unless we're going to wrap all packets in a version-safe manner, plugins will have to access packet fields with reflection. |
Sponge has this already implemented. (Custom Payload Packet), SpongePowered/SpongeAPI@e9f96b7 |
Nope. That Sponge PR refers to plugin messaging.
|
That are packets. Packets = Messages. |
I have worked with this specific Sponge API. This is the standard Plugin Message packet in Minecraft. Fountain will support listening and sending messages with this specific packet.
|
Oh, good. |
No description provided.
The text was updated successfully, but these errors were encountered: