Closed
Issue #23 · created by Will Sheffield · ·

Liteloader doesn't load

I have forge 1.11-13.19.1.2189 already installed and ran the LiteLoader installer for windows, ver. 1.11, telling it to extend from that version of forge. Yet when I select the new profile from the launcher (LiteLoader 1.11 with Forge 1.11), Forge says that only the same 4 mods are installed that were installed by it before loading liteloader and liteloader doesn't show in the mod list. I have one 1.11 mod (VoxelMap) that I downloaded and put in my 1.11 mod folder but it isn't being loaded because liteloader is not being installed. Any suggestion?

2 participants
liteloader/LiteLoader#23
  • You need to post the actual log, it's impossible to diagnose this kind of error from a description alone.

  • Will Sheffield @wsheffield9004 · by Mumfrey

    It's not an error. Minecraft loads just fine, just no liteloader is installed, only Forge. Unless you want to see the the part of the log file where liteloader is loaded during startup. You can see where it loads up and then calls Forge to be loaded. I don't see any errors. Here it is...

    [23:13:26] [main/INFO]: Loading tweak class name com.mumfrey.liteloader.launch.LiteLoaderTweaker
    [23:13:26] [main/INFO]: Using primary tweak class name com.mumfrey.liteloader.launch.LiteLoaderTweaker
    [23:13:26] [main/INFO]: Loading tweak class name net.minecraftforge.fml.common.launcher.FMLTweaker
    [23:13:26] [main/INFO]: Calling tweak class com.mumfrey.liteloader.launch.LiteLoaderTweaker
    [23:13:26] [main/INFO]: Bootstrapping LiteLoader 1.11
    [23:13:28] [main/INFO]: Registering API provider class
    com.mumfrey.liteloader.client.api.LiteLoaderCoreAPIClient
    [23:13:28] [main/INFO]: Spawning API provider class 'com.mumfrey.liteloader.client.api.LiteLoaderCoreAPIClient' ...
    [23:13:28] [main/INFO]: API provider class 'com.mumfrey.liteloader.client.api.LiteLoaderCoreAPIClient' provides API 'liteloader'
    [23:13:28] [main/INFO]: Initialising API 'liteloader' ...
    [23:13:28] [main/INFO]: SpongePowered MIXIN Subsystem Version=0.6.6 Source=file:/C:/Users/Bill/AppData/Roaming/.minecraft/libraries/com/mumfrey/liteloader/1.11-SNAPSHOT/liteloader-1.11-SNAPSHOT.jar Env=CLIENT
    [23:13:28] [main/INFO]: LiteLoader begin PREINIT...
    [23:13:28] [main/INFO]: Initialising Loader properties...
    [23:13:28] [main/INFO]: Setting up logger...
    [23:13:28] [main/INFO]: LiteLoader 1.11 starting up...
    [23:13:28] [main/INFO]: Active Pack: 1.11-SNAPSHOT-rE11CAFE-b8-8
    [23:13:28] [main/INFO]: Java reports OS="windows 7"
    [23:13:28] [main/INFO]: Adding supported mod class prefix 'LiteMod'
    [23:13:28] [main/INFO]: Enumerating class path...
    [23:13:28] [main/INFO]: Class path separator=";"
    [23:13:28] [main/INFO]: Class path entries=(
       classpathEntry=C:\Users\Bill\AppData\Roaming\.minecraft\libraries\com\mumfrey\liteloader\1.11-SNAPSHOT\liteloader-1.11-SNAPSHOT.jar
       classpathEntry=C:\Users\Bill\AppData\Roaming\.minecraft\libraries\net\minecraft\launchwrapper\1.12\launchwrapper-1.12.jar
       classpathEntry=C:\Users\Bill\AppData\Roaming\.minecraft\libraries\org\ow2\asm\asm-all\5.0.3\asm-all-5.0.3.jar
       classpathEntry=C:\Users\Bill\AppData\Roaming\.minecraft\libraries\net\minecraftforge\forge\1.11-13.19.1.2189\forge-1.11-13.19.1.2189.jar
       classpathEntry=C:\Users\Bill\AppData\Roaming\.minecraft\libraries\net\minecraft\launchwrapper\1.12\launchwrapper-1.12.jar
  • Just noticed something new. Tried loading one of my earlier liteloader/forge profiles, LiteLoader 1.8 with Forge 11.14.3.1250 now stops during loading just when Forge starts it's the first of its 7 laoding steps. Screen just goes black and does nothing.

  • Open the liteloader panel, press F3, then click upload log. Then paste the URL to your uploaded log here.

  • You've lost me, 'open liteloader PANEL' ?!? I have no idea what this is. If you mean the installation screen, no F3 ability there. Please explain. I tried F3 in the launcher 'log' and 'output' windows, nothing there either.

  • Well you said the mod wasn't showing up so I assumed that you already knew how liteloader worked since you must have been checking the mods list to know it wasn't showing up? The liteloader panel is a little tab in the top right of the main menu and all options menus. If liteloader is installed then you will see this little tab, hovering over it will expand the tab and you will see a tooltip with number of mods installed and liteloader version. Click the tab to open the panel.

  • Wow... what a little knowledge can do. Ok. Thanks! liteloader is loading but it is not loading the mod I have for it. I tried it with the mod in the \mod folder and in the \mod\1.11 folder, liteloader says it didn't install anything. Forge picked up the 2 mods I have in the \mod\1.11 folder. The mod is mod_voxelMap_1.6.21_for_1.11.0.zip. Says it needs liteloader to install it. Here's the log file... http://Logs.Liteloader.com/view/75NDvLg Thanks again!

  • The mod is mod_voxelMap_1.6.21_for_1.11.0.zip

    But why is it .zip? The correct extension for litemods is .litemod

    My guess is that you're using Internet Explorer. IE has a useful "feature" where it "corrects" the file extension when downloading things and "helpfully" renames the file to .zip. Change the file extension to .litemod and you should experience greater success.

  • Changed the extension (litemod), looked at liteloader log and it loaded. The zip contained some json files and a asset and com folder so it looked legit as a zip file. I just thought liteloader handled zip files instead of jar's or whatever. GGGrrrrrrrrr.... Windows!!! Thanks for your patience in this! Next time, should I expect liteloaded mod files to always(!) end in litemod? or can they be another extension?

  • It is a legit zip file. All a .jar file is is a .zip file with a different extension. Likewise, .litemod is a .jar (aka a zip) with a different extension. The extension is just used to differentiate the different purpose of the file. I strongly recommend using a different browser though, this kind of stuff is really just the tip of the iceberg with stupid stuff that IE/Edge does. Closing this issue as invalid/resolved.