unity-tech-cn
/
com.unity.services.samples.game-lobby
31
0
派生 7
代码 合并请求 版本发布
您最多选择25个主题 主题必须以中文或者字母或数字开头，可以包含连字符 (-)，并且长度不得超过35个字符
8 提交
62 分支
1 Plastic标签
目录树: d1773d39
分支列表 标签列表
${ item.name }
创建分支 ${ searchTerm }
从 'd1773d39'
${ noResults }
com.unity.services.samples..../Assets/Scripts
nathaniel.buck@unity3d.com d1773d39 Consolidating and renaming for readability. This still represents the baseline Relay + UTP behavior, without removing existing Lobby behavior yet or handling edge cases. 3 年前
..
Auth Merge pull request #9 from Unity-Technologies/master-lobby_merge_resolution-beta_packages_included-public_release_staging 3 年前
Entities Consolidating and renaming for readability. This still represents the baseline Relay + UTP behavior, without removing existing Lobby behavior yet or handling edge cases. 3 年前
Infrastructure Merge pull request #9 from Unity-Technologies/master-lobby_merge_resolution-beta_packages_included-public_release_staging 3 年前
Lobby Still partial progress. I have a little handoff going where the client identifies itself to the server and the server responds with an ID to use in further communication. However, I don't think that will actually work since all clients would also need those IDs? I can just send the user ID, which takes up more bandwidth but not dramatically so. Also, this pinpoints the heartbeat for keeping the Relay allocation up. I'm trying to pull out all the job system things, since that both seems like an extra layer of complexity that devs would have to learn and it also isn't, like, *actually* used correctly in the sample? 3 年前
Relay Consolidating and renaming for readability. This still represents the baseline Relay + UTP behavior, without removing existing Lobby behavior yet or handling edge cases. 3 年前
Tests Merge pull request #9 from Unity-Technologies/master-lobby_merge_resolution-beta_packages_included-public_release_staging 3 年前
UI Still partial progress. I have a little handoff going where the client identifies itself to the server and the server responds with an ID to use in further communication. However, I don't think that will actually work since all clients would also need those IDs? I can just send the user ID, which takes up more bandwidth but not dramatically so. Also, this pinpoints the heartbeat for keeping the Relay allocation up. I'm trying to pull out all the job system things, since that both seems like an extra layer of complexity that devs would have to learn and it also isn't, like, *actually* used correctly in the sample? 3 年前
Auth.meta Latest Dev and Readme without Vivox 3 年前
Entities.meta Latest Dev and Readme without Vivox 3 年前
Infrastructure.meta Latest Dev and Readme without Vivox 3 年前
Lobby.meta Latest Dev and Readme without Vivox 3 年前
LobbyRelaySample.asmdef Consolidating and renaming for readability. This still represents the baseline Relay + UTP behavior, without removing existing Lobby behavior yet or handling edge cases. 3 年前
LobbyRelaySample.asmdef.meta Latest Dev and Readme without Vivox 3 年前
Relay.meta Latest Dev and Readme without Vivox 3 年前
Tests.meta Latest Dev and Readme without Vivox 3 年前
UI.meta Latest Dev and Readme without Vivox 3 年前