Manually building the Westeroscraft Custom Client - Historical

Applied By geeberry: Aug 31, 2017 at 1:50 PM

Manually building the Westeroscraft Custom Client
This procedure is intended to allow folks that, for whatever reason, would prefer to use the standard Minecraft launcher to run the Westeroscraft Custom Client. If you use this procedure, subscribe to this thread - I will attempt to keep the procedure current as we continue to update the client, but there may be some delay at times. Do understand that the WesterosCraft Launcher is the 'supported' mechanism for accessing our server - don't expect much support for the manual process, beyond what you see in this forum: its not a matter of wanting to be difficult, but supporting the manual process defeats the point of having produced the launcher, and will ultimately results in even more work for myself and the few others that can support these methods.

So, without further disclaimers, here is the process:

  1. Download the installer for MinecraftForge v1.11.2 #2393 from
  2. Make sure you've run vanilla v1.11.2 on your Mojang launcher at least once, so that the necessary files for v1.11.2 have been downloaded
  3. Run the MinecraftForge installer JAR file. Select "Install Client" and click OK. Restart the launcher after this is done.
  4. Create a new profile (if needed) for our client, named "WesterosCraft v1.11.2", set the 'Version' to 'release 1.11.2-forge1.11.2-'.
  5. Click the "Game Directory" checkbox, and change the directory to a directory of your choosing (this will keep the mods from our client from interfering with other mods you might have installed). Remember this directory - for the sake of this example, we'll refer to this directory as <client-dir> in the future (as all other steps will be adding files in and under this directory). You should create this directory, if needed.
  6. Click "Save".
  7. Click "News", select the profile from the list, and click "Play" to launch the client: this should download other needed files, and create needed directories. If things start properly, you should see "Powered by Forge" in the lower left corner of the main window. Close the client.
  8. Open the folder for the <client-dir>. Download each of the following files, and place them in the 'mods' subdirectory under the <client-dir>:
    1. OptiFine 1.11.2 HD U C3 -
    2. WesterosBlocks v3.0-beta-4 -
    3. JourneyMap -
    4. BetterFoliage v2.1.7 -
    5. JustEnoughItems mod (1.11.2- :
    6. WorldEditCUI Forge Edition 2 - - only needed by Editors or higher)
    7. Waila mod (1.7.1_1.11.2) - (optional)
    8. DynamicSurrounds mod (v3.4.6.0) -
  9. Download and install the WesterosCraft Resource Pack into the 'resourcepacks' directory under <client-dir>:
  10. Download the BetterFoliage config file from place it in the <client-dir>/config directory. (optional).
  11. Create a directory named 'dsurround' under the 'config' directory, and Downloads both and into this directory (optional)
  12. Start client again from launcher. Click 'Options'. Click 'Resource Packs'. Select 'WesterosCraft' resource pack.
  13. Click "Multiplayer". Click "Add Server". Enter "Westeroscraft" for name, and "" for the address. Click 'Done".
  14. Launch the server selection, and log in to the production server!!

When upgrading:
Always remove the older version of the given file - there should never be two versions of the same mod in the <client-dir>/mods directory, for example.
Repeat ALL steps, unless you know that the changed files don't affect other steps. If any of the files in step 1 change, repeat ALL of steps 2-7, updating the existing 'WesterosCraft v1.11.2' profile. Each step in 8-11 only needs to be repeated if the given files change, and each requires that the older file be removed.

And there you go! Good luck with these instructions, and be sure to look back here if (and when) you cannot log in to the server due to a change in a mod version or client version.

NOTICE: As of v1.11.2, we require Java 8 and we STRONGLY recommend running with at least 2GB of memory configured (which implies a requirement for a 64-bit Java). Confirm these by looking at the 'Java Executable' and 'JVM Options' settings on your profile in the launcher.