Add server-side Forge protocol support

[deathcap]

Right now node-minecraft-protocol-forge only supports acting as a Forge client (connecting to Forge servers), but having the ability to act as a Forge server (allowing incoming Forge client connections) might be interesting.

See also: https://github.com/PrismarineJS/node-minecraft-protocol/issues/114 Forge Support

[ghost]

:+1: flying-squid forge support :smile:

[deathcap]

@mhsjlw That's what I was thinking too, but curious if you had a specific use case in mind? Forge clients can connect to vanilla servers already, but by adding Forge server support to flying-squid, we could allow Forge client mods to interact with flying-squid "Forge mods" (reimplemented in JavaScript for the nmp/flying-squid API). Or maybe have the server "register" all blocks/items/etc from the RegistryData packet...

[ghost]

I was thinking of implementing a JavaScript forge kind of API, but that may not make it attractive for Java mod developers. Registering the items is an interesting idea.

[nornagon]

I would love to use this for proxying Forge connections on the server side.

[deathcap]

:+1: to both ideas. Some notes/references possibly of interest:

https://github.com/voxel/ideas/issues/35 http://j2s.sourceforge.net/ http://stackoverflow.com/questions/8417809/java-to-javascript-using-gwt-compiler

https://github.com/WaterfallMC/Waterfall/tree/1fb55349f9c5822775623c4816646efab8c2d1a1/proxy/src/main/java/net/md_5/bungee/forge https://github.com/PrismarineJS/node-minecraft-protocol/blob/master/examples/proxy/proxy.js

[ghost]

Once I've completed my current projects this will be something that I'd like to work on, if you're open to help.

[deathcap]

@mhsjlw For sure, could use all the help I could get =)