Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client: Entity Back Reference on NetworkedEntityId #2

Open
MeFisto94 opened this issue Dec 20, 2023 · 0 comments
Open

Client: Entity Back Reference on NetworkedEntityId #2

MeFisto94 opened this issue Dec 20, 2023 · 0 comments

Comments

@MeFisto94
Copy link
Member

Basically, the created entity should have a component (and the related PS), so for instance when entering a car that has already been spawned by another player, we can tell the server that we wanted to enter exactly that car (by looking up if the entity we mount has a network id), otherwise we need to ad-hoc spawn a car and enter that.

yeah imo component is the cleanest solution
technically you can register persistent state without having an actual component
look at what I do in DynamicEntitySystem, you'll just need composite PersistentID with entity id and unique component name

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant