Recently there has been a bit of interest surrounding the need for integration with world protection plugins to ensure that waystones in the system cannot be misused (see PR #14). On top of this we should consider the ideas presented in Issues #19 and #20 as ideas beyond the scope of this project, but otherwise worth offering support for.
The purpose of this issue is to discuss what we should look for in an API. At this point it is clear we will need a standard one to expose access to some information about waystones within the system. It's also clear that an API will need to exist to offer first-class support to plugins like WorldGuard, and second-class support to other plugins.
What we need to consider is what both of these components will need and how we should implement them. Any ideas are welcome.
Recently there has been a bit of interest surrounding the need for integration with world protection plugins to ensure that waystones in the system cannot be misused (see PR #14). On top of this we should consider the ideas presented in Issues #19 and #20 as ideas beyond the scope of this project, but otherwise worth offering support for.
The purpose of this issue is to discuss what we should look for in an API. At this point it is clear we will need a standard one to expose access to some information about waystones within the system. It's also clear that an API will need to exist to offer first-class support to plugins like WorldGuard, and second-class support to other plugins.
What we need to consider is what both of these components will need and how we should implement them. Any ideas are welcome.