Jump to content

Recommended Posts

Posted

I'm currently trying to understand the inner workings of containers, but there are some weird things i noticed:
 

  • Is it possible that a container has more than one listener? As there is one container per Player spawned the listeners array doesn't fit to well in that picture. (Also there is a removeListener method, which is ClientOnly and only called from the GuiRepair and GuiContainerCreative)
  • Is the detectAndSendChanges method only logical server side or both? (I got only server side calls that far).
Posted
8 hours ago, Bregor said:

 

  • Is the detectAndSendChanges method only logical server side or both? (I got only server side calls that far).

It is intented to send changes to client, so it's effective on server only.

Posted
58 minutes ago, Alexiy said:

It is intented to send changes to client, so it's effective on server only.

Thanks - as i suspected then.

 

Then there is still the question if it is possible to have more than one listener on a container.

Posted
43 minutes ago, diesieben07 said:

You can add as many listeners as you want.

Is there a way to remove them on the server side? Because the removeListener method is ClientOnly.

Or is there a scenario where more than one would get added, if I don't add them myself?

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.