Install modules.

Way 1 — download the full package (nothing to install)

The release page has a single file, CT-Client-4.3.0-full.zip, that already contains the launcher, all thirteen modules, launcher scripts, and a read-me. This is the one-click route.

1. 1

   Download and unzip

   Unzip the file anywhere — Desktop, Documents, a games folder. You get a folder with CT-Main-4.3.0.jar, a modules folder, and four script files.

2. 2

   Start the launcher

   macOS: double-click Start CT-Main.command. If macOS blocks it the first time, right-click it, choose Open, then Open again.
   Windows: double-click Start CT-Main.bat.
   Linux: run java -jar CT-Main-4.3.0.jar in the folder.

3. 3

   Use it

   The window opens with every view — Launch, Versions, Settings, Accounts, Console, Mods, About. Nothing else to install.

Way 2 — drag module jars onto the installer

Use this to add or update modules later. Download the ct-module-*.jar files you want from the module catalog, then drop them on the right file for your system.

What the report tells you

Installing dropped modules into /Users/you/CT-Client-4.3.0/modules
  installed ct-module-about-4.3.0.jar — About (about 4.3.0) (28785 bytes)
Required by the modules above: theme
  fetching  ct-module-theme-4.3.0.jar from https://ct.shit.pub
  installed ct-module-theme-4.3.0.jar — CT Dark Interface (theme 4.3.0) (60369 bytes)
Installed 2 module(s).

• installed — the jar was copied into the modules folder.
• current — that exact build is already installed.
• replaced — an older build of the same module was removed first, so an upgrade never leaves two copies.
• fetching — a module another module requires was downloaded from the official site automatically. This is why dropping one jar can install two: About requires Theme.
• skipped — the file is not a CT module, or a folder held none.
• not found — the path does not exist.

If a module is already open in a running launcher, the dropped copy installs the modules, prints the report, and stops: close that window and start CT-Main again to use them.

Way 3 — install from inside the launcher

Open the Modules view in CT-Main and press Install module jar…. Pick one or more jars in the file chooser; they are installed into the modules folder that is shown at the top of the view. Because CT-Main reads modules when it starts, the launcher then offers to restart itself so the new modules load — press Restart CT-Main now, or Later and restart it yourself.

The same view lists every module that loaded, with its version and description, and every jar that was skipped with the reason. The Open modules folder button opens the folder in your file manager if you would rather copy jars there by hand.

Way 4 — command line

java -jar CT-Main-4.3.0.jar ct-module-theme-4.3.0.jar ct-module-launcher-4.3.0.jar
java -jar CT-Main-4.3.0.jar --install-modules ~/Downloads/ct-module-*.jar
java -jar CT-Main-4.3.0.jar --install-modules --no-fetch ct-module-theme-4.3.0.jar
java -jar CT-Main-4.3.0.jar --modules-dir /games/ct/modules ct-module-*.jar

• Plain jar arguments install and then start the launcher.
• --install-modules installs and exits without opening a window — this is what the Install modules scripts use.
• --no-fetch stops the automatic download of missing required modules.
• --modules-dir <path> installs somewhere else and makes CT-Main read that folder.

A single module jar is also a program of its own: java -jar ct-module-theme-4.3.0.jar installs just that module and prints where it went, with --print, --remove, and --launch as companions.

Where modules go, and which one you need

CT-Main reads one folder. It is shown at the top of the Modules view and printed at every start:

• --modules-dir <path> when you pass one;
• otherwise a modules folder next to CT-Main-4.3.0.jar (this is what the full download uses);
• otherwise ~/.ct-client/modules.

Modules declare what they require, and a module only loads when everything it requires is loaded first. The full set needs nothing extra, but if you install by hand:

Anything missing is named in the report rather than failing silently.

If a feature does not appear