Search results

@mikeprimm the affected forge versions will not work. Only the pre-rewrite version and any versions including my PR will work on the 1.12 client. Not working as of the update. Since we host forge forge we could just build it with the fix though. The compatibility fix just allows our launch code...

Important Update - v1.4.1 Forge rewrote their modList implementation last April and we finally got the memo. This update adds support for some incompatible changes they've introduced. Please update to this version ASAP as our next update to the 1.12.2 test server will not work on older...

Compatibility fixes released in v1.4.1 of the launcher. https://github.com/WesterosCraftCode/ElectronLauncher/releases/tag/v1.4.1

Dynamic surroundings is the only issue I came across. They do declare an identifier, and it's different than the one we currently have declared. It's case sensitive as well.

I'm not too familiar with forge's loading system, however I've narrowed down the problematic commits. Forge devs should take a look soon. If not, perhaps you may have some more insight for them. https://github.com/MinecraftForge/MinecraftForge/issues/5315 Edit: I've identified the issue. Going...

I'll take a look at that, but they supposedly fixed an issue with it on Sept. 4 https://github.com/MinecraftForge/MinecraftForge/commit/8ace535995522bec0557d4217e0d98b3dc76cf1e Edit: Confirmed that the argument is not working on the latest forge. Going to see if I can see what the issue is. If...

We just released an update to the launcher to make using shaders even easier. https://github.com/WesterosCraftCode/ElectronLauncher/wiki/Mod-Management#shaderpacks

Have you ever tried to turn shaders on ingame, but the whole thing just freezes for 5 minutes? Have you ever wished for a simple way to turn shaders on before you start the game? If so, v1.4.0 of the WesterosCraft Launcher is perfect for you! You can now switch shaderpacks on the Mods tab of...

Fixed in v1.3.0 (https://github.com/WesterosCraftCode/ElectronLauncher/releases/tag/v1.3.0). It was due to an inconsistency in Mojang's native library formatting. That has now been accounted for.

Release v1.3.0 is now available. You can now add drop-in mods by dragging and dropping them onto the Add Mods button. This update also includes an **important** fix for macOS users and Minecraft 1.12.2. Please update at your earliest convenience. Release Notes...

Could you export the log file and send it to me via PM? I can most likely figure out what's going on from that.

It also may be a good idea to start phasing out support for the older launcher. We can push out an update including an alert instructing the user to install the new launcher and provide a download link/upgrade guide (just my news post should suffice). We should also pick a date where updates...

I will take a look. Edit: It's working fine for me. I tried a run with my existing configuration as well as wiping the files and running again. Both launched without issue. One thing though, there are a few small errors on the distribution: Most likely the distro was updated and a file...

Looks good. The only comment I have at this point is to clean up the How To Use section on the launcher page. The basic idea is to make it less of a wall of text. Perhaps condense the information on how to use the launcher into a paragraph and include a small graphic. Could also do a shorter...

I can take a look into it.

Any outstanding issues for 1.12.2? I'd be willing to take a stab at it.

Important Update - v1.1.0 As some users have likely noticed, the AutoUpdater has not been working properly on macOS. This is because the updater requires that all files on macOS be code signed. This is currently not possible to do for two main reasons. I don't own a mac to setup the code...

Just a reminder: more blocks added = more RAM required to join.

Does anyone wanna throw together a few #ForTheThrone pics for Twitter/Instagram? (Dont go on twitter unless you're caught up. https://twitter.com/search?q=%23ForTheThrone&src=tyah)

You can, but it's not a very clean way. You can go to .westeroscraft/config.json and edit the commonDirectory and instanceDirectory fields. I'll see about adding in a cleaner method. (https://github.com/WesterosCraftCode/ElectronLauncher/issues/17)