API Overview
Core entry points
Section titled “Core entry points”The SSEC public surface centers on:
SSECInitializer@SSCommand@SSCExecute@SSCArgument@SSCAlias@SSCPermission@SSEventSSCArgumentAdapter
Initialization contract
Section titled “Initialization contract”SuperSexyEventCommandLib loads every registered SSECInitializer, runs onInitializeSSEC(), collects scan packages, and then calls SSECScanner.initialize().
That split is important:
- initializers provide configuration
- scanners discover annotated classes
- registrars translate those classes into real command and event registrations
Main extension areas
Section titled “Main extension areas”Command registration
Section titled “Command registration”Author root commands and subcommands with @SSCommand, then mark executable methods with @SSCExecute. See Command System.
Permission and alias policy
Section titled “Permission and alias policy”Add redirect aliases with @SSCAlias and gate execution with @SSCPermission. See Permissions and Aliases.
Argument mapping
Section titled “Argument mapping”Use built-in type adapters or register your own SSCArgumentAdapter during initialization. See Argument Types.
Event registration
Section titled “Event registration”Register Fabric callback listeners by annotating methods with @SSEvent. See Event System.
Example
Section titled “Example”public class MyModSSEC implements SSECInitializer { @Override public void onInitializeSSEC() { // CommandRegistrar.registerAdapter(MyType.class, new MyTypeAdapter()); }
@Override public String[] getPackagesToScan() { return new String[] { "com.example.mymod.command", "com.example.mymod.event" }; }}