Jump to content

DataWatcher.addObject: init vs. constructor


coolAlias

Recommended Posts

I've noticed that data watcher objects are usually if not always added in init methods, such as EntityInit, in vanilla code. Is there a specific reason this is the case, or could it just as well be added in the entity constructor?

 

In my specific case, I add a watchable in a class that extends IExtendedEntityProperties. It seems to work fine in the constructor, but I could just as easily move it to the init method as well, if need be. Just curious if it makes a difference.

 

Thanks!

Link to comment
Share on other sites

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.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.