Some Issues with TickEvent

[hanbings]

Some Issues with TickEvent

[hanbings]

Please check out the new commit. 6301953
I've changed AtomicLong to static because Alkaid will detect duplicate loads and I believe this change will work. Thanks!

[iceBear67]

Just close this issue with your confidence.

[iceBear67]

There're still some issues with your new commit.

TickEvent, which should be immutable, varies its tick when a newer one is fired, breaking its immutability. (And it should be immutable.)

Once TickEvent is immutable(or not), an AtomicLong is no longer necessary. Also, events are fired on the Main Thread where you can confidently avoid thread-safe issues, you don't have to use such a wrapper.

Additionally, You'd better use methods like getAndIncrease that guarantee thread-safe(which encourages VM to compile CAS assembly instructions) instead of tick + 1.

[hanbings]

New commit: 8368a3f
In this commit (and the first two of this) we separated the Event from the Tick / Second counter so that the tick / second inside the Event is no longer mutable.
The problem has been fixed, thanks again!