Adds asynchronous implementations of the Action and DistancedAction
classes, allowing plugins to make use of suspendable functions in Kotlin
instead of creating mini state machines to keep track of state.
The asynchronicity works by creating coroutine backed Channels for each
asynchronous action and having them listen on "pulse" events from the
action scheduler. The action can then suspend execution until a pulse is
received or until some expensive operation has completed (i.e.,
pathfinding).
If an asynchronous action is still busy when a pulse arrives then the
number of missed pulses will be accumulated and sent to the action at
the next possible time.
The training dummy plugin has been updated to use asycnrhonous actions
as an example.
Refactors the test helpers to use receiver functions so multiple players
can exist in the world per test case. The AddFriendsTest is an example
of where this is needed.
Additionally, Hamcrest has been replaced with AssertJ for fluent
assertions.
Adds separate build tasks for each plugin by auto-discovering plugin meta
files in the build script. Each plugin will automatically have its
main sources and tests compiled, and then it's output added to the game
modules classpath.
This enables support for incremental compilation of scripts, as well as
unit testing using Gradle's test framework.
Adds gradle tasks to build all plugin scripts under data/plugins with
the KotlinPluginCompiler implementation previously used for runtime code
generation. In addition to .plugin.kts files, scripts can also declare
API code in .kt files which will also be included on the classpath and
made available to other plugins.
Creates a new sourceset for server plugins to support IDE integration
with plugin code. Additionally moves plugins to game/data/plugins and
contains some gradle related fixes (remove java plugin from root project
and fix exec task dependency).
Ports the Maven build POMs to Gradle build scripts, which are a bit
friendlier to use. Instead of using the exec:java Maven goal to run the
server now, the gradle run task should be used.
Gary Tierney