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.

Sign up for GitHub

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

adr245: better define for transform updates #261

Merged
merged 2 commits into from
Jan 22, 2024
Merged

adr245: better define for transform updates #261

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3c82207
adr245: better define for transform updates
leanmendoza Dec 22, 2023
778ed0b
Update content/ADR-245-player-components.md
leanmendoza Jan 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/ADR-245-player-components.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ The proposal consists of the following key points:
- Reserving Entities: Entities numbered 32 to 256 will be reserved for storing player data components. This reservation ensures that sufficient entities are available to accommodate player data. When a player disconnects from the room, the entity MUST be deleted, and a new generation for the entity number will be used. This ensures a session of up to 14.680.064 unique players.
- Player Data Components: A new set of player data components will be introduced, containing essential information about the player, such as position(Transform), wearables, identity, base avatar properties, and emote commands.
- Scene Inclusion: Every scene in SDK7 MUST receive player data components. This inclusion ensures that each scene has access to real-time player data, which is vital for smooth interactions and gameplay experiences.
- Transform Updates: Only active and global scenes will receive real-time transform updates to optimize data updates and reduce overhead. If the Transform is not set in a Scene, it is out of the scene.
- Transform Updates: active parcel scenes (the one where each player is) and global scenes MUST receive real-time players `Transform` updates. Non-active parcel scenes MAY have no `Transform` of the player outside of them. Exception: the primary player `Transform` MUST be present in all scenes.

# Player Data Components

Expand Down
Loading