You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 2, 2020. It is now read-only.
It would be great to have a "boilerplate" for plugins with a separate API.
The plugin should contain a simple service interface and an implementation. This way we can also show how to register and use custom services.
Structure:
Project: notification
Subproject: notification-api
Interface: NotificationService
Subproject: notification-sponge
Class: NotificationPlugin
Class: SimpleNotificationService
The plugin displays a notification to players when they login.
They can mark the notification as read with /notification clear.
Admins can set the notification with /notification set <msg> or delete it with /notification delete.
The command uses the SimpleDispatcher class for subcommands.
Other plugins can get the NotificationService from the service manager and modify the notification. Plugins can also set an expiration date for the notification.
For simplicity, the notification is not persistent when the server restarts.
Right now I don't have the time to work on this, that's why I created this issue as a reminder. If you want to work on this, go ahead...
The text was updated successfully, but these errors were encountered:
This isn't done yet, but if anyone comes here, for now you can find an example of a project with a separate API using services and similar with Nucleus.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be great to have a "boilerplate" for plugins with a separate API.
The plugin should contain a simple service interface and an implementation. This way we can also show how to register and use custom services.
Structure:
The plugin displays a notification to players when they login.
They can mark the notification as read with
/notification clear
.Admins can set the notification with
/notification set <msg>
or delete it with/notification delete
.The command uses the
SimpleDispatcher
class for subcommands.Other plugins can get the
NotificationService
from the service manager and modify the notification. Plugins can also set an expiration date for the notification.For simplicity, the notification is not persistent when the server restarts.
Right now I don't have the time to work on this, that's why I created this issue as a reminder. If you want to work on this, go ahead...
The text was updated successfully, but these errors were encountered: