Various mods with boards that are not so busy. Ones that get busy may get promoted to their own multi-board section, or dead ones will be removed.
No posts here yet
615 topics in this forum
Please describe your problem in more detail. What version of Forge are you downloading? Did you download the installer from the downloads site? What happens when you double-click the file? Do you have Java installed? Is there an installer.log in the same directory as the installer? If so, please upload the log file to here or a paste site (Pastebin).
The warnings about unknown attributes can be ignored; Minecraft 1.16 changed how entity attributes are identified, bringing them more in line with resource locations (1.15.2: "forge.swimSpeed" is in 1.16: "forge:swim_speed"). This occurs when loading a Forge world from pre1.16, since Forge doesn't have datafixers to automatically fix those attributes, as far as I know. (Forge doesn't have datafixers for those because DataFixerUpper is very theory-heavy, and requires time investment to translate between versions, which is hard for a volunteer- and community-driven project, as opposed to Mojang, a company with salaried employees) The errors about serialization of arguments can also be ignored. One of Forge's goals is interoperability with vanilla: Forge clients can connect to vanilla servers, and vanilla clients can connect to Forge servers. The errors occur because Forge doesn't serialize the arguments to be sent to clients; if the clients were vanilla, then sending those command arguments to the client can confuse it and may cause issues and crashes. (If you're thinking, "Why not only check if it's a Forge client?", because that would require changing the Brigadier library, which would be another can of worms.) TL;DR: First batch of errors because you updated an old world, second batch of errors is because Forge likes to support connecting to vanilla clients/server.
Who's Online (See full list)