6 Commits

Author	SHA1	Message	Date
LOOHP	6d14314bd9	reupload	2021-04-06 21:14:05 +08:00
LOOHP	05cfdb73a9	clear	2021-04-06 21:12:32 +08:00
LOOHP	6c90a82f7c	Follow naming conventions	2021-04-06 12:50:26 +08:00
James Puleo	3f60ffd1ef	Track the players selected slot index with PacketPlayInHeldItemChange, ... and allow changing of a players selected slot with PacketPlayOutHeldItemChange. Also introduces an event that can be used to change or cancel a player's selected slot change. I tried to follow the style and mannerisms of existing code, but what's up with the Unsafe class? The class is okay, but why are the methods named as such? Having all the methods named 'a' will be sure to cause conflict once two methods take the same parameters.	2021-02-22 01:54:26 -05:00
LOOHP	8d2b7ea0cb	0.4.0 SNAPSHOT	2021-02-19 23:33:21 +08:00
LOOHP	c77c700fac	Reorganize sources to maven project standard	2020-12-29 01:50:43 +08:00