112 lines
3.9 KiB
Markdown
112 lines
3.9 KiB
Markdown
# Writing a Event Handler
|
|
|
|
Event handlers are one of the main functions of plugins. They allow a plugin to tap into the internal workings of the server and alter its behavior to perform some other action. For a simple example, we will implement a handler for the `player_join` event.
|
|
|
|
The Pumpkin plugin event system tries to copy the Bukkit/Spigot Event system, so that developers coming from there will have a easier time learning Pumpkin.
|
|
However, Rust has different conceptions and rules, so it's not all like in Bukkit/Spigot.
|
|
Rust doesn't have inheritance; instead it only has composition.
|
|
|
|
The event system uses traits to dynamically handle some events: `Event`, `Cancellable`, `PlayerEvent` and etc.
|
|
Cancellable can also be an Event, because it's a trait. (TODO: verify this)
|
|
|
|
## Implementing the Join Event
|
|
|
|
Individual event handlers are just structs which implement the `EventHandler<T>` trait (where `T` is a specific event implementation).
|
|
|
|
### What are blocking events?
|
|
|
|
The Pumpkin plugin event system differentiates between two types of events: blocking and non-blocking. Each have their benefits:
|
|
|
|
#### Blocking events
|
|
|
|
```diff
|
|
Pros:
|
|
+ Can modify the event (like editing the join message)
|
|
+ Can cancel the event
|
|
+ Have a priority system
|
|
Cons:
|
|
- Are executed in sequence
|
|
- Can slow down the server if not implemented well
|
|
```
|
|
|
|
#### Non-blocking events
|
|
|
|
```diff
|
|
Pros:
|
|
+ Are executed concurrently
|
|
+ Are executed after all blocking events finish
|
|
+ Can still do some modifications (anything that is behind a Mutex or RwLock)
|
|
Cons:
|
|
- Cannot cancel the event
|
|
- Have no priority system
|
|
- Allow for less control over the event
|
|
```
|
|
|
|
### Writing a handler
|
|
|
|
Since our main aim here is to change the welcome message that the player sees when they join a server, we will be choosing the blocking event type with a low priority.
|
|
|
|
Add this code above the `on_load` method:
|
|
:::code-group
|
|
|
|
```rs [lib.rs]
|
|
// [!code ++:7]
|
|
use pumpkin_api_macros::with_runtime;
|
|
use pumpkin::{
|
|
plugin::{player::player_join::PlayerJoinEvent, Context, EventHandler, EventPriority},
|
|
server::Server,
|
|
};
|
|
use pumpkin_util::text::{color::NamedColor, TextComponent};
|
|
|
|
struct MyJoinHandler; // [!code ++:12]
|
|
|
|
#[with_runtime(global)]
|
|
impl EventHandler<PlayerJoinEvent> for MyJoinHandler {
|
|
fn handle_blocking(&self, _server: &Arc<Server>, event: &mut PlayerJoinEvent) -> BoxFuture<'_, ()> {
|
|
Box::pin(async move {
|
|
event.join_message =
|
|
TextComponent::text(format!("Welcome, {}!", event.player.gameprofile.name))
|
|
.color_named(NamedColor::Green);
|
|
})
|
|
}
|
|
}
|
|
```
|
|
|
|
:::
|
|
|
|
**Explanation**:
|
|
|
|
- `struct MyJoinHandler;`: The struct for our event handler
|
|
- `#[with_runtime(global)]`: Pumpkin uses the tokio async runtime, which acts in weird ways across the plugin boundary. Even though it is not necessary in this specific example, it is a good practice to wrap all async `impl`s that interact with async code with this macro.
|
|
- `fn handle_blocking()`: Since we chose for this event to be blocking, it is necessary to implement the `handle_blocking()` method instead of the `handle()` method.
|
|
|
|
### Registering the handler
|
|
|
|
Now that we have written the event handler, we need to tell the plugin to use it. We can do that by adding a single line into the `on_load` method:
|
|
:::code-group
|
|
|
|
```rs [lib.rs]
|
|
use pumpkin::{
|
|
plugin::{player::player_join::PlayerJoinEvent, Context, EventHandler, EventPriority}, // [!code ++]
|
|
server::Server,
|
|
};
|
|
use pumpkin::{
|
|
plugin::{player::player_join::PlayerJoinEvent, Context, EventHandler}, // [!code --]
|
|
server::Server,
|
|
};
|
|
|
|
#[plugin_method]
|
|
async fn on_load(&mut self, server: Arc<Context>) -> Result<(), String> {
|
|
pumpkin::init_log!();
|
|
|
|
log::info!("Hello, Pumpkin!");
|
|
|
|
server.register_event(Arc::new(MyJoinHandler), EventPriority::Lowest, true).await; // [!code ++]
|
|
|
|
Ok(())
|
|
}
|
|
```
|
|
|
|
:::
|
|
Now if we build the plugin and join the server, we should see a green "Welcome" message with our username!
|