UNET Commands calling advice. Calling Commands from CHILD object
Hello, developers!
I've faced a problem within my creature's system in UNET. I'm having a main Creature class (NetoworkBehaviour) and bunch of other classes wich describe creature's behaviour (Patrolling, Attacking etc); this classes (decorators) are attached to crature's child gameObject "Behaviour".. So this describing classes (decorators) should send commands and rpc's to other clients in all, derive from NetowrkBehaviour.
So, i've found out that only root gameObject ("Creature") should contain NetoworkIdentity so only this root object can send Commands and call rpc's but child object's want to do this too..!
I don't want to attach a lot of components (Patrolling, Attack, Yell etc) to one root gameObject and at this time a dont wanna break my creature's system architecture. So how to organize all this stuff? Or should i eventually attach all components to root obj?
Answer by Riccardo82 · Oct 07, 2017 at 10:06 PM
Hi, i have the same problem. Any solution?
@epicVoodoo have you made progress?
Your answer
Follow this Question
Related Questions
Unet multiplayer Client Host confusion 0 Answers
Multiplayer Survival Status Handling 1 Answer
Photon RPC 2 Answers
ClientRPC not called from command on client instance during Start() 0 Answers
Simple ClientRpc Whats wrong with it? 0 Answers