asofold 9a4b3f6f91 [BLEEDING][BREAKING] Store PlayerData by UUID, use a PlayerTickListener. ... Instead of maps for each individual purpose, and the rather expensive TickListener adding and removing, player specific task will be done via one PlayerTickListener that can be registered with the TickTask. Thus PlayerData has the access methods requestUpdateInventory and requestPlayerSetBack, and so on, later more. For the DataManager.playerData map it'll be UUID first now. Consequently some calls have been altered to prefer passing Player or UUID for PlayerData getting.		2017-04-08 15:47:06 +02:00
..
src	[BLEEDING][BREAKING] Store PlayerData by UUID, use a PlayerTickListener.	2017-04-08 15:47:06 +02:00
pom.xml	Add a dedicated compatibility module for 1.10.x (1.10 R1).	2016-12-27 23:36:03 +01:00