71a4d91497
All checks were successful
studiorailgun/highlevel-netcode-gen/pipeline/head This commit looks good
14 lines
348 B
Markdown
14 lines
348 B
Markdown
|
|
|
|
Effectively we want two mechanisms for most trees
|
|
|
|
Client sends a signal to server requesting some mutation
|
|
|
|
Server sends update of state to client
|
|
|
|
|
|
|
|
|
|
|
|
Typical behavior tree should basically be a loop that constantly sends these updates to the client
|
|
The client triggers this loop in the first place by sending one of these signals to the server |