Exit | Home | Part 1 | Part 2 | Part 3 | Original Wiki

Part 1: Player Information

Section 1: Choosing a Version

1.1: Release Types

There are three main release types offered by Nomi-CEu:

If you want a stable and bug-free experience, opt for the latest stable release. Alpha/Beta releases are a little more cutting edge, whilst nightly releases can be very unstable, but ensures you get the latest features and bug fixes as soon as they are approved.

Latest Stable or Alpha/Beta Releases can be found on our GitHub Downloads and CurseForge Downloads. The top result is the newest release. You may have to scroll down to find the latest stable release.

The latest Nightly Release is found on our Nightly Page.

1.2: Which One is Newer?

Stable and Alpha/Beta Releases are labelled as follows:

Stable Releases

<major>.<minor>.<patch> Major versions are only changed when an extremely big release occurs. This is pretty much never changed. This is a number.

Minor versions are changed every big release. This is a number.

Patches are fixes between each big release. This is a number.

Alpha/Beta Releases

<incoming-release>-<status>-<pre-num> <emergency-fix>

The incoming release is the next stable release, that this alpha/beta puts out to test.

The status is either alpha or beta, dependent on how stable the release is.

The pre-num is a number that increases with each alpha/beta for a certain release. This is a number, starting from 1.

Sequence

Below is an example of an update progression. Arrows point towards a newer version. 1.6 -> 1.6.1-alpha-1 -> 1.6.1-beta-2 -> 1.6.1-beta-3 -> 1.6.1-beta-4 -> 1.6.1 -> 1.7-beta-1 -> 1.7-alpha-2 -> 1.7

Nightly Releases are always at a newer state, or the same state, as the latest Stable or Alpha/Beta Release.

Section 2: Client Installation and Updating

2.1: Installation Setup

Installing Prism Launcher

Start by installing Prism Launcher in their official site. It is the recommended launcher for Nomi-CEu. You can also use other launchers, such as MultiMC and ATLauncher.

Installing Java 8

Nomi-CEu also requires Java 8 to be installed. There are several options for this, listed below.

Make sure you install one for your operating system and architecture, and install a 64 bit one! If you are using Windows, that means you must install one labelled for x64, and the msi version.

You may install a JDK or a JRE version.

2.2: Stable or Alpha/Beta Installation

Below instructions are for Prism Launcher. For other launchers, you can install via your launcher's CurseForge integration, or import client zips downloaded from CurseForge or GitHub.

Ensure the selected Java Version is your installed Java 8!

Prism Installation

  1. Click 'Add Instance' in the top left
  2. Select 'CurseForge' in the sidebar
  3. Search 'Nomifactory CEu' in the search bar
  4. Select Nomi-CEu, and select your desired version in the bottom right
  5. Give your instance a descriptive name, desirably including the version number
  6. Click OK

To select Java Installation (Prism)

Instance -> Edit -> Settings -> Tick Java Installation -> Auto Detect -> Select Java Installation -> Click OK

2.3: Nightly Installation

If you want to install the nightly version of the pack for testing purposes, its link is available here. For all launchers, simply download the client zip and import into your launcher.

Prism Installation

  1. Download the latest client nightly zip
  2. Click 'Add Instance' in the top left
  3. Select 'Import' in the sidebar
  4. Click 'Browse' in the right, select the downloaded zip
  5. Click OK

2.4: Cleanroom Installation

Cleanroom offers multple benefits over a regular install, including faster game loading, increase in fps, and reduced memory usage. Note however, that this is in beta, and more issues will occur!

Note: if you are playing on a server, you can mix and match. For example, your client can run on Cleanroom, and your server can run normally, or vice versa.

Installing Java 21

To install Nomi-CEu with Cleanroom, you must first install Java 21. For this, Adoptium Temerin is Recommended, or use Azul Zulu for Arm Macs.

Installation Procedure (Prism)

Below is the installation instructions for Prism Launcher. The process is similar for other launchers; see the Cleanroom GitHub Page for more details.

[!IMPORTANT] If you are using Stable Nomi-CEu (1.7.5) -> Use CleanroomMC Version 0.3.2.

If you are playing on a nightly version after c83250b (Sat 14 Jun 11:50pm UTC) -> Use CleanroomMC Version 0.3.4+.

[!CAUTION] Using the wrong version will lead to your instance crashing!

  1. Install Nomi-CEu, Nightly or Stable/Alpha/Beta
  2. Download CleanroomMMC mmc instance zip
  3. In Prism, Import the Downloaded Zip. (See Nightly Installation for how to do this!)
  4. Edit the instance ➜ SettingsJava Installation ➜ set to your Java 21 path (/bin/javaw.exe).
  5. Set Java Arguments to -XX:+UseZGC -XX:+ZGenerational
  6. Copy the minecraft/ folder from Nomi-CEu to CleanroomMMC. Delete existing minecraft/ or .minecraft/ folders, if they exist.
  7. Disable or delete the mods mixinbooter & configanytime
  8. Add the latest version of Fugue
  9. Add the newest version of Scalar (v2.*, not v3.*)

If you see errors or log spams from CraftPresence, update your Fugue version to v0.17.3+.

2.5: Changing the Mode

There is a secondary mode to this game, called Expert Mode. See the Readme for more details.

Note: if you are playing on a server, your instance's mode must match that of the server!

If you would like to change to this mode, follow the below steps:

Windows:

  1. (CurseForge Downloads Only) Download the script here, and save it to the root directory of the pack (the same level as \config).
  2. Run the pack mode switcher in a terminal with ./pack-mode-switcher.bat

Mac/Linux:

  1. (CurseForge Downloads Only) Run curl -O https://raw.githubusercontent.com/Nomi-CEu/Nomi-CEu/main/pack-mode-switcher.sh to download the script, or download it here.
  2. Run chmod +x pack-mode-switcher.sh; sh pack-mode-switcher.sh in the pack root directory (the one containing /config).

Manual installation instructions are available here.

2.6: Customisation

Addon Mods

Nomi-CEu offers integration for some 'Addon Mods', which you can just add to your instance, and their recipes will be adjusted.

See the Readme for more details.

An addon mod not included in that list is the Essential Mod. Although it is not officially supported by Nomi-CEu, you should be able to simply add it into your instance, allowing for an easy way to play with a couple friends. If you add the Essential Mod, also delete or disable the CustomMainMenu mod, to fix issues with conflicting main menus.

Config Changes

You might want to set B:onDemandAnimatedTextures to false in config/loliasm.cfg. This will fix issues you may have with animated textures, but this could cause lag issues on AMD GPUs with outdated drivers.

Resource Packs

There are many resource packs available, which cover some mods that are in Nomi-CEu, or cover custom textures in Nomi-CEu itself. Recommended resource packs include: Faithful Resource Packs

Clarity Resource Packs

Other GregTech Resource Packs

World Customisations

Popular world customisations include:

2.7: Updating

To update to a newer version, make a new instance of Nomi-CEu of the version you are updating.

Do NOT use the Update button in your launcher as it is built naively and will break your pack!

You might also want to copy your existing saved data:

FileDescription
minecraft/saves directorySingle Player Worlds
minecraft/resourcepacks directoryResource Packs
minecraft/options.txtMinecraft settings, like keybinds, selected resource packs, video options, etc.
minecraft/journeymap directoryJourneyMap Waypoints and Map Data
minecraft/visualores directoryVisualOres Data
minecraft/hei_bookmarks.iniHEI Bookmarks

To automate this process, feel free to use one of the migration scripts provided by this project: NomiUpdater. Whilst this is an official script, it is not well polished, and any issues should go to the migrator project's issues page.

2.8: Tips and Tricks

This section includes some brief tips and tricks designed to make your Nomi-CEu experience as fun as possible!

Section 3: Server Installation and Updating

3.1: Installation

Note: If you wish to play on your server outside of your network, you will need to setup port-forwarding. That is out of the scope of this file, and you should be aware of the risks that are created when you do this.

To install a Nomi-CEu server, follow the below steps:

  1. Ensure Java 8 is installed. See Installing Java 8 for more details!
  2. Download the latest server zip file from your Chosen Version
  3. Extract it

If you are using a server hoster, follow instructions from them.

3.2: Cleanroom Installation

Cleanroom offers multiple benefits over a regular install, including faster game loading, increase in fps, and reduced memory usage. Note however, that this is in beta, and more issues will occur!

Note: if you are playing on a server, you can mix and match. For example, your client can run on Cleanroom, and your server can run normally, or vice versa.

Installing Java 21

To install Nomi-CEu with Cleanroom, you must first install Java 21. For this, Adoptium Temerin is Recommended, or use Azul Zulu for Arm Macs.

Installation Procedure

[!IMPORTANT] If you are using Stable Nomi-CEu (1.7.5) -> Use CleanroomMC Version 0.3.2.

If you are playing on a nightly version after c83250b (Sat 14 Jun 11:50pm UTC) -> Use CleanroomMC Version 0.3.4+.

[!CAUTION] Using the wrong version will lead to your instance crashing!

  1. Install Nomi-CEu, Nightly or Stable/Alpha/Beta
  2. Download CleanroomMMC installer jar
  3. Run the installer jar (If you are on mac, you may have to approve it)
  4. Select your extracted server zip folder
  5. Ignore the warning about files being already present, press OK
  6. Wait for installation to finish
  7. Disable or delete the mods mixinbooter & configanytime
  8. Add the latest version of Fugue
  9. Add the newest version of Scalar (v2.*, not v3.*)
  10. Edit your launchscript (launch.bat or launch.sh):
    • Change the FORGEJAR variable to be the name of the Cleanroom Jar (e.g., for Cleanroom 0.2.3 Alpha, cleanroom-0.2.3-alpha.jar)

3.3: Using SpongeForge

Although Nomi-CEu does not officially support SpongeForge, you should be able to get your server at least running with SpongeForge, with these steps and some debugging:

  1. Download the latest SpongeForge for 1.12
  2. Set B:threadPriorityFix to false in config/loliasm.cfg
  3. Set B:"Entity Tracker" to false in config/Universal Tweaks - Bugfixes.cfg
  4. If this still doesn't work, try removing Alfheim and/or Vintage Fix

However, SpongeForge has a lot of issues with mods, including, at least at the time of writing, issues with obfuscation in Groovy Scripts.

3.4: Changing the Mode

There is a secondary mode to this game, called Expert Mode. See the Readme for more details.

If you would like to change to this mode, follow the below steps:

  1. Download the Pack Mode Switcher Script (CurseForge Download ONLY)
  2. Run the Script
    • Windows: ./pack-mode-switcher.bat (Terminal)
    • Mac/Linux: chmod +x pack-mode-switcher.sh; sh pack-mode-switcher.sh (Terminal)
  3. Follow On Screen Prompts to Change to Desired Mode

3.5: Launching The Server

  1. Run the launch.bat script (Windows) or the launch.sh script (Mac/Linux) to launch the server. These two scripts are called the launchscripts. (You may have to run chmod +x launch.sh on Mac/Linux first)
  2. The first time you do this, the server will crash. To fix this, open the eula.txt file, and change the value from false to true.

Note: If you receive an error saying you have the wrong java version installed, make sure your terminal is currently using Java 8 (or Java 21 for Cleanroom Installation) as the default, or customise the launchscript to use the java executable directly. SDKMAN! is recommended for the first option, which runs on Mac, Linux, and Windows through WSL, and allows you to change your default java easily, on the fly.

3.6: Server Options

3.7: Updating a Server

To update a server, please create a new server folder, or instance. Copy over saved data:

Section 4: Server Admin Information

4.1: Island Cakes

There are Island Cakes available, which sends each team to a different void island. To set this up:

How do they Work?

Island Cakes and Personal Island Cakes do not get eaten. If you wish to make them be eaten, and be slowly consumed similar to Overworld, Void, Nether and End Cakes, change line 332, in /config/DimensionalEdibles.cfg, from B:consumesFuel=false to B:consumesFuel=true. To refill them, Pulsating Dust is used.

Island Cakes send each FTB Team to a unique island. A player simply right-clicks the cake and will be sent to their team's island. If no such island exists, an island will first be created.

In contrast, Personal Island Cakes sends each individual to a seperate island. This is useful for individuals who want some personal space, apart from their team.

Customization

By default, Islands will be 60 Regions apart, placed in a spiral. Regions are an area of 32 by 32 chunks. You can change the spacing by changing the number value in line 343, in /config/DimensionalEdibles.cfg, to any value between 2 and 100. Note that this value is in Regions.

In line 338, you can change the dimension the Islands are spawned in. You may have to play around. To get a list of all dimensions, do /forge dimensions to get a list of all dimensions and their IDs. You can also change the y level the islands are spawned at, in line 354.