Skip to content
MyoWiki SSEC · 26.1

Installation

Runtime expectations

Section titled “Runtime expectations”

The local sseclib build metadata for this line declares:

  • artifact name ssec
  • group me.myogoo
  • version 26.1
  • loader target Fabric
  • Java target 25

That means the intended published coordinate for this line is me.myogoo:ssec:26.1.

Add the dependency

Section titled “Add the dependency”

In a Loom-based mod, wire the library into your preferred dependency scope.

dependencies {
    modImplementation "me.myogoo:ssec:26.1"
}

Use the repository source that matches how you publish or consume the artifact in your workspace.

Register ssec entrypoints

Section titled “Register ssec entrypoints”

Dependency setup alone is not enough. SSEC only discovers your handlers through a custom ssec Fabric entrypoint.

{
  "entrypoints": {
    "ssec": [
      "com.example.mymod.command.MyCommandInitializer",
      "com.example.mymod.event.MyEventInitializer"
    ]
  }
}

Implement SSECInitializer

Section titled “Implement SSECInitializer”

Each entrypoint implements SSECInitializer and returns the packages that should be scanned.

public class MyCommandInitializer implements SSECInitializer {
    @Override
    public void onInitializeSSEC() {
        // Register custom argument adapters or perform extra setup here.
    }


    @Override
    public String[] getPackagesToScan() {
        return new String[] { "com.example.mymod.command" };
    }
}

onInitializeSSEC() runs before the scan. Use it for adapter registration and any setup that annotated handlers depend on.

Common failure modes

Section titled “Common failure modes”
  • No ssec entrypoint: nothing is scanned.
  • Wrong package list: annotated classes are never discovered.
  • Missing custom adapter: a command parameter type cannot be mapped.
  • Wrong Java baseline: the library targets Java 25 for this line.
Section titled “Recommended next pages”