Add configurability to enforcing the players location.
Fix for stained glass panes.

Adding a flag for ~ thin fence.
Random formatting change.
Make message for consoleonly feature configurable. [TICKET DBO 711]
Set version to 3.10.9-RC for release.
Set version to 3.10.10-SNAPSHOT for next development iteration.
Just a typo.
First rough version of a LocationTrace implementation.

Just the raw implementation + initial test cases. To keep memory use
constant, a ring-buffer with some maximal size will be used. The
iterators are meant for faster implementation, rather than fastest
iteration. Later some trigonometric functions could be added to
LocationTrace, depending on if that may gain a lot of performance.

Next we will add the logics for adding entries and resetting the trace
to NCP (moving, teleporting, joining), on Logout the trace must not stay
in MovingData but should be garbage collected. That should be a
milestone dev build, though it does nothing for the user, it might help
finding crash bugs :p.

Soon to follow will be changing some fight checks to be able to use the
moving trace, then alter them to actually use it. Fight and interact
checks could also do moving consistency checking (tp exploit).

Who reads this?
Set fall distance to 0, if the player could fly or is in creative mode.
[BLEEDING] Maintain location traces (not making use of those, yet).

No change for the function of the plugin, except if there are new bugs.
Actual changes:
* Keep track of squared distance to the previous element in a trace.
* Balance mergeDist: prevent merging the latest entry, if the squared
	distance from the latest to the second latest element is greater
	than mergeDist. Never merge if there are only two entries in total.
* Add convenience methods for resetting and updating the trace.
* Maintain the moving traces actively. With intended use being
	player-player interaction, we will not reset with every teleport.
Ensure no fall distance remains for leaving players who could fly.
Use the preset TAG for some commands.
Add more tests for LocationTrace.
Prepare fight checks for using a moving trace.

* Get+update players moving traces, create fake ones for other entities.
* Reorder checks + add some comments (not in use yet).
Fight checks: Use data and config from arguments. Prepare new methods.
Add test for first element for a maxAge iterator.
[RAW] First version for direction + reach using a moving trace.

This does not change the used methods much, thus it will rather allow
much more cheating, however it allows some basic testing for false
positives. The reach implementation has been slightly optimized to run
faster. The current implementation is not final and only uses trace
elements that were added in the current tick, the latest is always
included.

Next steps will probably be:
* Stricter methods for an individual TraceEntry (demand near-exact hit).
* Don't allow random latency shifting. Maintain a window-thing.
* Probably get rid of the classic method for attacking other entities.
Ignore players in vehicles with the fall damage events.
[BLIND] Dedicated compat module for 1.7.2. Set CompatCBDev to MC 1.7.5.
Add guard for not having checked at all.