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
In a large complex game, the remotes used can generally be grouped into categories. Zap should support a namespace under the event struct, and when a namespace is specified, you should be able to access it through remotes.namespace.remote_name.
Alternatives
Do not organise the events
Use mutiple zap config files
Implementation Details
This should be implimented under the event struct with an optional namespace field.
The text was updated successfully, but these errors were encountered:
An alternative syntax for this rather an an event namespace field could be this:
namespace n = {
type t = u8
event e = {
from: Server,
type: Reliable,
call: SingleAsync,
data: t
}
}
-- this also allows us to use types from namespaces
type t_from_n = n.t
Describe your feature
In a large complex game, the remotes used can generally be grouped into categories. Zap should support a namespace under the event struct, and when a namespace is specified, you should be able to access it through
remotes.namespace.remote_name
.Alternatives
Implementation Details
This should be implimented under the event struct with an optional namespace field.
The text was updated successfully, but these errors were encountered: