I see no reason why mods couldn't be supported in the same way resource packs are. Why can't there just be a mods folder where we drag the mods and then activate them in game?
I see no reason why mods couldn't be supported in the same way resource packs are. Why can't there just be a mods folder where we drag the mods and then activate them in game?
Because Mojang are busy optimising the game to make it run as best as it can, rather than focusing on modding support? Would you rather have official modding support with a game that stutters, or unofficial modding support which is still incredibly easy with a smooth game? I'd personally prefer the latter.
Either way, I don't know whether you haven't used mods since, what, 1.2.5? But ever since 1.2.5 most mods have been literally drag-and-drop-into-a-folder. Ever since 1.6 it's gotten even easier. Download the Forge installer from here for the version you're using, install it, download the mods you want to use and drop them in the mods folder. Hell, you don't even need to activate them in-game.
Even when the "Workbench" API is released, I seriously don't think mods will move from Forge to it (or whatever API is being used at the time to it) if it's what has been advertised. The API is being developed with server plugins in mind, rather than modding in general. What does this mean? Rather than having the mods we have now, we're going to have downscaled mods which can only work with the game within the bounds of what the API allows. The reason why modding is as large as it is now is because Forge doesn't give you a set of rules you have to follow (so long as you know how to do what you want to do), if you know your stuff you can do anything. The 1.8 model format broke a tonne of mods and completely removed support for dynamic renderers, however Forge has apparently got a workaround for it that modders can use. Still, if Forge dies and the "Workbench" API becomes the only API available, say goodbye to fancy animations and dynamic renders unless Mojang changes the premise of the API. They want the client to act as a "slave" side of the logic, the server does everything and the client only handles rendering, sound and input. I personally don't like how they're handling the API, and I know a heap of other people don't either. But, we'll have to wait and see.
Rollback Post to RevisionRollBack
Author of the Clarity, Serenity, Sapphire & Halcyon shader packs for Minecraft: Java Edition.
I see no reason why mods couldn't be supported in the same way resource packs are. Why can't there just be a mods folder where we drag the mods and then activate them in game?
Mods won't be supported until the Plugin API is released.
As for when that will happen, don't count on it happening within the next 20 years considering Mojang's track record with the plugin API.
Because Mojang are busy optimising the game to make it run as best as it can, rather than focusing on modding support? Would you rather have official modding support with a game that stutters, or unofficial modding support which is still incredibly easy with a smooth game? I'd personally prefer the latter.
Either way, I don't know whether you haven't used mods since, what, 1.2.5? But ever since 1.2.5 most mods have been literally drag-and-drop-into-a-folder. Ever since 1.6 it's gotten even easier. Download the Forge installer from here for the version you're using, install it, download the mods you want to use and drop them in the mods folder. Hell, you don't even need to activate them in-game.
Even when the "Workbench" API is released, I seriously don't think mods will move from Forge to it (or whatever API is being used at the time to it) if it's what has been advertised. The API is being developed with server plugins in mind, rather than modding in general. What does this mean? Rather than having the mods we have now, we're going to have downscaled mods which can only work with the game within the bounds of what the API allows. The reason why modding is as large as it is now is because Forge doesn't give you a set of rules you have to follow (so long as you know how to do what you want to do), if you know your stuff you can do anything. The 1.8 model format broke a tonne of mods and completely removed support for dynamic renderers, however Forge has apparently got a workaround for it that modders can use. Still, if Forge dies and the "Workbench" API becomes the only API available, say goodbye to fancy animations and dynamic renders unless Mojang changes the premise of the API. They want the client to act as a "slave" side of the logic, the server does everything and the client only handles rendering, sound and input. I personally don't like how they're handling the API, and I know a heap of other people don't either. But, we'll have to wait and see.
Author of the Clarity, Serenity, Sapphire & Halcyon shader packs for Minecraft: Java Edition.
My Github page.
The entire Minecraft shader development community now has its own Discord server! Feel free to join and chat with all the developers!