com.unity.services.samples.game-lobby

文件历史

nathaniel.buck@unity3d.com 42fe907a Almost actual progress: This now has the two clients connecting to Relay on join, with the host keeping the allocation alive, and they will send each other changes to their name, emote, and ready immediately. The code will get some cleanup and renaming, and then there are still plenty more features necessary, including UI work and changes to how Lobby data get used.		3 年前
..
Auth	Merge pull request #9 from Unity-Technologies/master-lobby_merge_resolution-beta_packages_included-public_release_staging	3 年前
Entities	Almost actual progress: This now has the two clients connecting to Relay on join, with the host keeping the allocation alive, and they will send each other changes to their name, emote, and ready immediately.	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	Almost actual progress: This now has the two clients connecting to Relay on join, with the host keeping the allocation alive, and they will send each other changes to their name, emote, and ready immediately.	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	Partial progress: Following a trio of Relay+UTP samples, I seem to have something that will bind a transport to Relay and keep the connection open (as evident from the fact that a client can join after what would be the 10s timeout on Relay and successfully get the JoinAllocation, when they wouldn't without keeping the connection open even when binding was correct). However, this current code is very slapdash and sloppy; I'm just committing now as a very rough draft.	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 年前