GhostAuthoring.GhostGroup tooltip says that it’s useful for weapon pickup system, when weapon is another Ghost, but In all examples, weapon is just component on Player Ghost entity. Which best practice to create switchable weapon in netcode project?
a. Player is a ghost and each weapon is another ghost, linked by Ghost Group
b. Player is a ghost and weapon state is component on it, for example with synced enum of weapon type
Hey Asoprachev!
Unfortunately, this is not a question we can answer, as it depends upon your game design. If you have a use-case where weapons are “first class” ghosts, then you would likely have some kind of item management system built in Entities, allowing users to pickup and drop items, including weapon ghosts.
Other games load all weapons into the character controller’s hands, and simply enable the one the player is holding (usually for RAM and animation simplification reasons).