First attempt to detect if a moving event would fire. This might not be
100% accurate, as a) we can'T really know and b) lastTo is not minitored
in the most reliable way (e.g. teleport on highest priority, resetting
logic favors set-backs).
* Use a HashMap for data, as we intend to use the primary thread.
* Move redundant move checking into a method.
* Ignore on-ground, if it is sent too often.
* Log if redundant move checking has to be disabled.
* Add methods to NoCheatPlusAPI to add/set/get version tags.
* Display all tags in the ncp reload command.
* Alter test framework to set a dummy API.
* Add tags for blocks, net checks, FastConsume.
Obviously these have been forgotten, but are not marked with
@GlobalConfig. Using after-failure checking, because the raw config
getting and accessing might be slightly heavy-ish.
Does not seem to be strictly necessary, because the data is comparably
light-weight and the data loss on some time slices would usually be
small.
Should be cleaner, as this is a seldom event (login, logout).
