July 8, 20178 yr Author Ok, I think my theory is holding up. I removed the call setRandomAttributes and setAttributeModifiers and the output is only called once. I must be trying to process to much information for a single tick to handle it all. I guess I'll have to either set the information not inside of a TickEvent or try and optimize how I'm setting the information. Developer of Levels and Lost Eclipse
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.