> [!NOTE]
> This is a joke variant of Stianloader's Starloader-Launcher.
> If you really are contemplating using it - then ask yourself what's wrong with you.
> This variant is mainly intended to use for comparision reasons only.
> There will be missing features, and dragons - maybe. So beware, you've been warned.

# Starloader

## Starloader vs Starloader-API

The starloader project on its own doesn't do much other than providing a way
to loader secondary jars (extensions) as well as providing mixins and a bytecode
manipulation framework. As such most extensions should make use of Starloader-API
to avoid conflicts.

## IRC Chat

We do have an IRC channel for anyone that is interested in modding the game in
general, although the main purpose of the channel will be to discuss Starloader.
Feel free to take a look at it at #galimulator-modding @ irc.esper.net

## Building

The project can be built via maven and a JDK 9 or higher (JDK 17 is recommended).
This can be easily done via `mvn install` on most systems.
The built jar is located in the target folder. (Note: you probably
don't want the jar prefixed with "original-")

## Running

On MacOS it has to be run manually via a Java 1.8 JRE (17 recommended) with a command such
as `java -cp starloader-launcher-XYZ-all.jar de.geolykt.starloader.launcher.CLILauncher`

Place the built `starloader-launcher-XYZ-all.jar` in the galimulator folder.
Then edit the `config.json` file in the galimulator folder to be

```json
{
  "classPath": [
    "jar/galimulator-desktop.jar",
    "starloader-launcher-XYZ-all.jar"
  ],
  "mainClass": "de.geolykt.starloader.launcher.CLILauncher",
  "vmArgs": [
    "-Dsun.java2d.dpiaware=true"
  ]
}
```
Make sure to modify the `mainClass` entry to be equal to the one shown above,
The `starloader-launcher-XYZ-all.jar` entry in the `classPath` entry should
correspond to the name of the starloader-launcher file you copied into the
galimulator folder.

Mods need to be added in a "mods" folder located in the galimulator directory.

For JPMS, the `de.geolykt.starloader.launcher` and `core` (from classtransform)
modules must be defined as root modules. You probably also want to include
`org.fusesource.jansi` as a root module, though SLL will somewhat gracefully
recover if that module is missing.

## Licensing and redistributing

All code is licensed under the Apache 2.0 license, allowing you to redistribute
the source.

Additionally a few portions of our code (i. e. large parts of the selfmodification and extension system)
was largely written by Minestom contributors, who have contributed their code under
the Apache 2.0 license