
minecraft\logs.Ĭurse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch: Mojang Launcher: When using the Mojang launcher debug.log is found in. log is added the log will appear with the. Windows hides file extensions by default so the installer may appear without the. This log will be called either installer.log or named the same as the installer but with.

Post your installer log, found in the same place you ran the installer Please post logs using one of the following sites (Thank you Lumber Wizard for the list):ĭo NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.
#JOURNEY MAP 1.12.2 SERVER MOD#
I think it's the Forge Mod Loader default mod that is not working.

jar file, moving it to the client mod folder, and renaming it back to "Securit圜raft-Mod-1.12.1"(It works with 1.12.2) Now I can join the server with no error and use the mod with the configurations that I have already. : Rejecting connection CLIENT: " I tried duplicating the mod's.
#JOURNEY MAP 1.12.2 SERVER MODS#
: Client attempting to join with 5 mods : : Attempting connection with missing mods at CLIENT It says this on the console " : Client protocol version 2 I runned it with my client that doesn't have the mod added. I added the mod "Securit圜raft" made for Forge 1.12.2, 1.12.1, and 1.12 to the server mods folder. I runned the server with no mods, it worked. I have installed the Forge 1.12.2 server and client.
