[noci] Wrap "EventHelper#registerEvent" in `

This commit is contained in:
JeremyStar™ 2024-10-03 21:34:44 +02:00
parent d6e56f8dd9
commit a4830b5ce8
Signed by: JeremyStarTM
GPG key ID: E366BAEF67E4704D

View file

@ -34,7 +34,7 @@ It can do the following things:
## Known issues ## Known issues
### Reflection is broken ### Reflection is broken
Due to how the mod and plugin loaders load JAR files, scanning the classpath for annotations does not work. Due to how the mod and plugin loaders load JAR files, scanning the classpath for annotations does not work.
This means that events have to be registered manually. You can do that by calling [EventHelper#registerEvent](https://jd.engine.staropensource.de/v1-alpha5/base/de/staropensource/sosengine/base/implementable/helper/EventHelper.html#registerEvent(java.lang.Class,de.staropensource.sosengine.base.implementable.EventListenerCode,de.staropensource.sosengine.base.type.EventPriority)). This means that events have to be registered manually. You can do that by calling [`EventHelper#registerEvent`](https://jd.engine.staropensource.de/v1-alpha5/base/de/staropensource/sosengine/base/implementable/helper/EventHelper.html#registerEvent(java.lang.Class,de.staropensource.sosengine.base.implementable.EventListenerCode,de.staropensource.sosengine.base.type.EventPriority)).
If you want to use a specific subsystem, either find or make a plugin/mod porting that subsystem to Minecraft (best option), or shade and include the subsystem in your final JAR and hope nothing breaks. Only do that if you have no other choice or the subsystem is specific to your plugin or modification. If you want to use a specific subsystem, either find or make a plugin/mod porting that subsystem to Minecraft (best option), or shade and include the subsystem in your final JAR and hope nothing breaks. Only do that if you have no other choice or the subsystem is specific to your plugin or modification.
## Contributing ## Contributing