You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you want your component to tick alongside its provider, you can add the ServerTickingComponent or ClientTickingComponent (or both) to your component interface (here, IntComponent). If you'd rather add the ticking interface to a single component subclass, you can use one of the specific methods provided in the individual modules.
And the example shows adding ticking interface to component subclass. So, I tried implementing ServerTickingComponent in my component subclass:
But it never ticked. But docs says you can add ServerTickingComponent to your component interface, so after seeking for help I found this out and did this:
(serverTick still in PlayerManaComponent class)
And it worked. For some reason ticking doesn't work in component subclasses. Either it is wrong docs, or something wrong with the code.
The text was updated successfully, but these errors were encountered:
If you want your component to tick alongside its provider, you can add the ServerTickingComponent or ClientTickingComponent (or both) to your component interface (here, IntComponent). If you'd rather add the ticking interface to a single component subclass, you can use one of the specific methods provided in the individual modules.
What this was supposed to mean is that if you put the ticking on a subtype, you must use registry.beginRegistration().impl(PlayerManaComponent.class)...
The README says:
And the example shows adding ticking interface to component subclass. So, I tried implementing ServerTickingComponent in my component subclass:
But it never ticked. But docs says you can add ServerTickingComponent to your component interface, so after seeking for help I found this out and did this:
(serverTick still in PlayerManaComponent class)
And it worked. For some reason ticking doesn't work in component subclasses. Either it is wrong docs, or something wrong with the code.
The text was updated successfully, but these errors were encountered: