-
-
Notifications
You must be signed in to change notification settings - Fork 932
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
Document how to use minecraft-protocol-forge with mineflayer #56
Comments
According to mcforge.net, mc forge is a classic server. Not supported. |
Dunno if its too late, but I have a feeling that Kyso was talking about Minecraft Forge, which I'm sure you've heard of. I think he's talking about the forge modloader packets. As quoted by "To some extent, you won't have to implement the mods directly, but at least send the packet that Forge wants to let it work? shrug" AKA. |
I would accept a pull request that did this, but I'm not going to add the functionality myself |
I've completely forgotten about this issue. But yes, @bearbear12345 hit it on the nail. |
@rom1504 can you reopen this issue? Still would be a cool feature =) Requires lower-level protocol support first PrismarineJS/node-minecraft-protocol#114 |
Good idea, MCCTeam/Minecraft-Console-Client#100 (a console client with Forge (1.8 and 1.7.10) support) used this same technique |
Yeah reopening. Nothing can be done here until PrismarineJS/node-minecraft-protocol#114 is done though. |
Now that nmp has a minecraft-forge plugin, something can be done here. |
let's close this |
To some extent, you won't have to implement the mods directly, but at least send the packet that Forge wants to let it work? shrug
The text was updated successfully, but these errors were encountered: