-
Notifications
You must be signed in to change notification settings - Fork 369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Block Action -> ? #1319
Comments
Maybe go for simplicity... Sync Event? |
There are also world events for worlds, which are basically the same thing but not dependent on a "Sync event" is a bit ugly IMO but descriptive, so it could work. |
|
I personally think action describes perfectly all of these. The word action just means "something that is done" (pushing, playing, ringing, opening, emitting a beam, etc.) |
But this is more specific than simply something that is done, it's something that need to be done on the client. Look over this list again, and see if you can spot that pattern. |
The problem with I therefore propose |
What yarn currently calls "block actions" are used by:
"Block actions" are triggered by the server, and processed by both the server and clients within range of the block (the "block action" is sent to these clients). Basically, it is used for events that also need to be processed on the client.
The yarn name is confusing and does not capture its actual purpose. It looks like a method you would want to call to simulate a right-click action or something. What should we call it instead?
The text was updated successfully, but these errors were encountered: