Package-level declarations
Types
Convenience-annotation to mark a specific class as a listener. Should be used in combination of VitalListener. Internally delegates functionality to Component.
Convenience-condition to mark a class to only be loaded as a bean, when running as a BungeeCord plugin. If not running as a BungeeCord plugin, the annotated bean will not be instantiated by Spring.
Convenience-condition to mark a class to only be loaded as a bean, when running as a Spigot plugin. If not running as a Spigot plugin, the annotated bean will not be instantiated by Spring.
Convenience-condition to mark a class to only be loaded as a bean, when the vital-cloudnet4-bridge module is used. If not running with the vital-cloudnet4-bridge module, the annotated bean will not be instantiated by Spring.
Convenience-condition to mark a class to only be loaded as a bean, when the vital-cloudnet4-driver module is used. If not running with the vital-cloudnet4-driver module, the annotated bean will not be instantiated by Spring.
Convenience-condition to mark a class to only be loaded as a bean, when the vital-commands module is used. If not running with the vital-commands module, the annotated bean will not be instantiated by Spring.
Convenience-condition to mark a class to only be loaded as a bean, when the vital-configs module is used. If not running with the vital-configs module, the annotated bean will not be instantiated by Spring.
Convenience-condition to mark a class to only be loaded as a bean, when the vital-holograms module is used. If not running with the vital-holograms module, the annotated bean will not be instantiated by Spring.
Convenience-condition to mark a class to only be loaded as a bean, when the vital-inventories modules is used. If not running with the vital-inventories module, the annotated bean will not be instantiated by Spring.
Convenience-condition to mark a class to only be loaded as a bean, when the vital-items module is used. If not running with the vital-items module, the annotated bean will not be instantiated by Spring.
Convenience-condition to mark a class to only be loaded as a bean, when the vital-localization module is used. If not running with the vital-localization module, the annotated bean will not be instantiated by Spring.
Convenience-condition to mark a class to only be loaded as a bean, when the vital-minigames module is used. If not running with the vital-minigames module, the annotated bean will not be instantiated by Spring.
Convenience-condition to mark a class to only be loaded as a bean, when the vital-players module is used. If not running with the vital-players module, the annotated bean will not be instantiated by Spring.
Convenience-condition to mark a class to only be loaded as a bean, when the vital-scoreboards module is used. If not running with the vital-scoreboards module, the annotated bean will not be instantiated by Spring.
Convenience-condition to mark a class to only be loaded as a bean, when the vital-statistics module is used. If not running with the vital-statistics module, the annotated bean will not be instantiated by Spring.
Convenience-condition to mark a class to only be loaded as a bean, when the vital-tasks module is used. If not running with the vital-tasks module, the annotated bean will not be instantiated by Spring.
Convenience-condition to mark a class to only be loaded as a bean, when the vital-utils module is used. If not running with the vital-utils module, the annotated bean will not be instantiated by Spring.
Internal interface; setups up bStats for Spigot and BungeeCord. By default, Vital enables bStats and sends its own metrics to it. To also include metrics for your own plugin, you must configure vital.core.bstats.plugin-id to your plugin id you got from bStats.
Defines an entity managed by a VitalRepository instance. The entity may be identified by the given generic type.
Should be used for classes that support an info annotation to provide metadata. To allow for multiple info annotations along the hierarchy path, this interface exposes a map of all registered info annotations.
Defines a listener within the Vital-Framework.
Internal exception; thrown during VitalListener lifecycles.
A module includes additional features within the Vital ecosystem. Every module is essentially a Configuration and should define every module bean. Additionally, a module can also display what features are added, etc.
Internal exception; thrown during VitalModule lifecycles.
This class defines internal functionality required to initialize and shutdown a Vital plugin and should rarely be used by developers manually. Plugin bootstrapping is automatically done via the vital-gradle-plugin and initialization is done by vital-loader.
Internal exception; thrown when an error occurrs during VitalPlugin lifecycles.
A volatile in-memory repository to store temporary data in a Spring-like repository implementation. It can store implementations of VitalEntity and the means to get, save and delete them.
Internal spring resource loader responsible for locating resources in the spring context. Will strip any protocol from requested resources to enable correct resource loading.
Internal handler; responsible for gracefully shutting down Vital when server shutdown is requested.
Main spring configuration for the implementing plugin. Exposes the plugin as a bean to fix classpath scanning errors when ide scans for beans.