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
Is your feature request related to a problem? Please describe.
There are numbers of situations when some entity should be handled by several resources but replication to the client-side is redundant. The simplest example is a spawnpoint. In my practice was not any case in which spawnpoints had used on a client-side. But maintaining spawnpoints as elements is a very convenient so it'll be desirable to add an opportunity to decide replicate an element or don't.
Describe the solution you'd like
I propose to add a new argument to createElement function that tells the game about a local nature of an element.
For example, createElement( string elementType, [ string elementID = nil, bool isLocal = false ] )
Describe alternatives you've considered
At the moment there are two kind of approaches to handle this. The first one is to create elements as is, do all the work to replicate element for a client. And second one is to syncronize a table between resources, that in most cases is painful and unreliable.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
There are numbers of situations when some entity should be handled by several resources but replication to the client-side is redundant. The simplest example is a spawnpoint. In my practice was not any case in which spawnpoints had used on a client-side. But maintaining spawnpoints as elements is a very convenient so it'll be desirable to add an opportunity to decide replicate an element or don't.
Describe the solution you'd like
I propose to add a new argument to createElement function that tells the game about a local nature of an element.
For example,
createElement( string elementType, [ string elementID = nil, bool isLocal = false ] )
Describe alternatives you've considered
At the moment there are two kind of approaches to handle this. The first one is to create elements as is, do all the work to replicate element for a client. And second one is to syncronize a table between resources, that in most cases is painful and unreliable.
The text was updated successfully, but these errors were encountered: