Note: This information is outdated. Use the documentation found here for version 2.5 and higher.


What is WSEvents

WSEvents is a seperate plugin for bukkit that is used in combination with Websend.
It allows developers and admins to select bukkit events that, when triggered, start a websend command.

How does it work?

Websend and WSEvents start up with Bukkit.
WSEvents reads the config file and chooses which eventlisteners are needed and enables those.
Then it waits until Bukkit triggers the event, and when that happens WSEvents will ask Websend to do a command.
The command contains the following data:
Data: "event", eventname as defined here.
Commandsource: "WEBSEND_EVENTS_" + event category (for example: "WEBSEND_EVENTS_INVENTORY")
Except if the command is from the "player" category, then it uses the playername.

How can I use it?

First, download the latest version of both Websend and WSEvents from the downloads page.
Put the jar in your plugins folder and start your server. WSEvents will generate the config files.
Take a look into your plugins/WSEvents folder. You will see a list of text files with the names of each category.
Each file contains a list of events you can enable. To enable an event, simply open the file with the right category, find the event and replace "false" with "true".
You will need to restart your server to apply these changes.


Should you encounter a problem with WSEvents, first try restarting the server.
If that doesn't work, try deleting the WSEvents config files and restart the server. WSEvents will regenerate them. Toggle the events again, restart the server and see if it works. If it doesn't, post a comment or a forum post with the full error log and your enabled events.