ViaMCP
ViaMCP copied to clipboard
ViaVersionMCP
Add ViaMCP for MCP Reborn
1.18.1 is even more random imo, 1.18.2 can be done if people want it but I generally don't recommend MCP for modern versions (and also not versions below 1.20.4)
it's crazy that ViaMCP still does not have support for MCP Reborn
It's crazy that people still use MCP instead of Fabric. It's also crazy that there are people who call Yarn "ass" (it's not) meanwhile Searge having 5000 useful functions not mapped, and Yarn has most of them remapped. I can't wait for MCP & Searge to die.
- You can't stack mods with MCP without hacks like Reflection, and even then, it's really annoying to have to tell everyone "depend on my mod in your mod manifest file, Mixins will do their thing, and you can fix conflicts & compatibility issues if present", but then realize that some idiot is still using MCP instead of mod loaders
- Issues that are caused by your modifications to Minecraft's code, if you don't know where to look. Imagine you want to spoof the yaw & pitch being sent to the server, you create an event, and in the entity code where the packet is sent, you modify the code to use yours. Oops! You forgot to modify this other thing, and now it's all falling down. Oops! You changed other entities that aren't your player's yaw, now everyone is looking backwards from your view.
- Licensing issues (although no one cares and neither does Mojang). Now you want to distribute your client. You distributed it, oops! Looks like you broke Mojang's EULA! It says "Do not distribute" in the corner, that means it's probably in their EULA, and you just distributed Minecraft with some modifications, I could confuse the 500 other Minecraft classes you didn't change enough and say that's a copyright violation. Whereas with mods, you aren't distributing Minecraft, you're distributing pretty much a patch / diff for your modifications to Minecraft, these are called Mixins, and Fabric or your mod loader will change Minecraft's bytecode around so you can make your modifications without breaking their EULA and getting told no as soon as you get any attention enough to get someone at Mojang to look at your client and see it's basically their source.
it's crazy that ViaMCP still does not have support for MCP Reborn
It's crazy that people still use MCP instead of Fabric. It's also crazy that there are people who call Yarn "ass" (it's not) meanwhile Searge having 5000 useful functions not mapped, and Yarn has most of them remapped. I can't wait for MCP & Searge to die.
- You can't stack mods with MCP without hacks like Reflection, and even then, it's really annoying to have to tell everyone "depend on my mod in your mod manifest file, Mixins will do their thing, and you can fix conflicts & compatibility issues if present", but then realize that some idiot is still using MCP instead of mod loaders
- Issues that are caused by your modifications to Minecraft's code, if you don't know where to look. Imagine you want to spoof the yaw & pitch being sent to the server, you create an event, and in the entity code where the packet is sent, you modify the code to use yours. Oops! You forgot to modify this other thing, and now it's all falling down. Oops! You changed other entities that aren't your player's yaw, now everyone is looking backwards from your view.
- Licensing issues. Now you want to distribute your client. You distributed it, oops! Looks like you broke Mojang's EULA! It says "Do not distribute" in the corner, that means it's probably in their EULA, and you just distributed Minecraft with some modifications, I could confuse the 500 other Minecraft classes you didn't change enough and say that's a copyright violation. Whereas with mods, you aren't distributing Minecraft, you're distributing pretty much a patch / diff for your modifications to Minecraft, these are called Mixins, and Fabric or your mod loader will change Minecraft's bytecode around so you can make your modifications without breaking their EULA and getting told no as soon as you get any attention enough to get someone at Mojang to look at your client and see it's basically their source.
holy yap
1.18.1 is even more random imo, 1.18.2 can be done if people want it but I generally don't recommend MCP for modern versions (and also not versions below 1.20.4)
He's writing a cheat. 1.18.2 is the version the movement threshold was reduced from 0.03 -> 0.0002. He wants the higher threshold so more leniency has to be given for his cheats making it easier to bypass.
it's crazy that ViaMCP still does not have support for MCP Reborn
It's crazy that people still use MCP instead of Fabric. It's also crazy that there are people who call Yarn "ass" (it's not) meanwhile Searge having 5000 useful functions not mapped, and Yarn has most of them remapped. I can't wait for MCP & Searge to die.
- You can't stack mods with MCP without hacks like Reflection, and even then, it's really annoying to have to tell everyone "depend on my mod in your mod manifest file, Mixins will do their thing, and you can fix conflicts & compatibility issues if present", but then realize that some idiot is still using MCP instead of mod loaders
- Issues that are caused by your modifications to Minecraft's code, if you don't know where to look. Imagine you want to spoof the yaw & pitch being sent to the server, you create an event, and in the entity code where the packet is sent, you modify the code to use yours. Oops! You forgot to modify this other thing, and now it's all falling down. Oops! You changed other entities that aren't your player's yaw, now everyone is looking backwards from your view.
- Licensing issues. Now you want to distribute your client. You distributed it, oops! Looks like you broke Mojang's EULA! It says "Do not distribute" in the corner, that means it's probably in their EULA, and you just distributed Minecraft with some modifications, I could confuse the 500 other Minecraft classes you didn't change enough and say that's a copyright violation. Whereas with mods, you aren't distributing Minecraft, you're distributing pretty much a patch / diff for your modifications to Minecraft, these are called Mixins, and Fabric or your mod loader will change Minecraft's bytecode around so you can make your modifications without breaking their EULA and getting told no as soon as you get any attention enough to get someone at Mojang to look at your client and see it's basically their source.
I appreciate you're willing to explain all of this to these people but the only reaction you're gonna get from anybody here is that ur yapping and disrespect. These people are all hack client developers they really don't care about the EULA or licensing or much with legality at all.
it's crazy that ViaMCP still does not have support for MCP Reborn
It's crazy that people still use MCP instead of Fabric. It's also crazy that there are people who call Yarn "ass" (it's not) meanwhile Searge having 5000 useful functions not mapped, and Yarn has most of them remapped. I can't wait for MCP & Searge to die.
- You can't stack mods with MCP without hacks like Reflection, and even then, it's really annoying to have to tell everyone "depend on my mod in your mod manifest file, Mixins will do their thing, and you can fix conflicts & compatibility issues if present", but then realize that some idiot is still using MCP instead of mod loaders
- Issues that are caused by your modifications to Minecraft's code, if you don't know where to look. Imagine you want to spoof the yaw & pitch being sent to the server, you create an event, and in the entity code where the packet is sent, you modify the code to use yours. Oops! You forgot to modify this other thing, and now it's all falling down. Oops! You changed other entities that aren't your player's yaw, now everyone is looking backwards from your view.
- Licensing issues. Now you want to distribute your client. You distributed it, oops! Looks like you broke Mojang's EULA! It says "Do not distribute" in the corner, that means it's probably in their EULA, and you just distributed Minecraft with some modifications, I could confuse the 500 other Minecraft classes you didn't change enough and say that's a copyright violation. Whereas with mods, you aren't distributing Minecraft, you're distributing pretty much a patch / diff for your modifications to Minecraft, these are called Mixins, and Fabric or your mod loader will change Minecraft's bytecode around so you can make your modifications without breaking their EULA and getting told no as soon as you get any attention enough to get someone at Mojang to look at your client and see it's basically their source.
I appreciate you're willing to explain all of this to these people but the only reaction you're gonna get from anybody here is that ur yapping and disrespect. These people are all hack client developers they really don't care about the EULA or licensing or much with legality at all.
I'm pretty sure mojang don't care unless you're making money or claiming you wrote the Minecraft source code
I appreciate you're willing to explain all of this to these people but the only reaction you're gonna get from anybody here is that ur yapping and disrespect. These people are all hack client developers they really don't care about the EULA or licensing or much with legality at all.
it still is a issue, I was just pointing things out