使用 JavaScript能使本网站更好的工作。
首页
探索
关于Plastic
登录
unity-tech-cn
/
com.unity.services.samples.game-lobby
关注
31
点赞
0
派生
7
代码
合并请求
版本发布
11
提交
62
分支
1
Plastic标签
目录树:
5fa60706
/main
/dev
/esteban-learn-lobby-relay
/bartj-remove-connectioninfo
/rename_to_gamelobby
/sonarqube_run
/feat-parrelsync
/35-bug-in-joining-private-lobby
/lobby-1.1.0-pre.3-update
/main/staging
/main/symbol_game_art-URP_Test
/main/symbol_game_art
/main/staging/code_context
/main/staging/host_icon
/main/staging/429_cooldown_implementation
/main/staging/closed_beta_package_update
/main/staging/more_minor_fixes
/main/staging/rate_limit_data
/main/staging/sub-version-update
/main/staging/Open_beta_Update
/main/staging/error_UI_UX
/main/staging/resetting_event_queue_fix
/main/staging/error_codes_to_exceptions
/main/staging/vivox_UI
/main/staging/vivox_package_integration
/main/staging/Networking_for_GameObjects
/main/staging/lobby_quick_join
/main/staging/relay_disconnect_ping_bug
/main/staging/vivox_polish
/main/staging/Polished_UI_assets
/main/staging/lobby_quick_join_put_it_back
/main/staging/relay_dtls
/main/staging/UI_Marketing_Assets
/main/staging/UI_bugs
/main/staging/bugs_various
/main/staging/host_handshake
/main/staging/core_service_package_updates
/main/staging/small_ui_bugs
/main/staging/vivox_bug_voice_outside_lobby
/main/staging/missing_fonts
/main/staging/ugs_package_updates
/main/staging/ngo_minigame_structure
/main/staging/minigame_staging
/main/staging/messenger_fix
/main/staging/ngo_minigame_cleanup
/main/staging/asyncrequest_log_fix
/main/staging/december_UI_bugs
/main/staging/ready_when_player_leaves
/main/staging/ngo_more_cleanup
/main/staging/ngo_gameplay_tweaks
/main/staging/qol_gameplay
/main/staging/moved_folder
/main/staging/observer_comments_and_clarification
/main/staging/glyph_game_NGO_fixes
/main/staging/wire_implementation
/main/staging/wire_lobbydata_replacement
/main/staging/2021_Upgrade
/main/staging/Open_beta_Update/open_beta_relay
/main/staging/2021_Upgrade/custmer_test
/main/staging/2021_Upgrade/Async_Refactor
/main/staging/2021_Upgrade/Async_Refactor/Relay_On_UTP
/main/staging/2021_Upgrade/Async_Refactor/GA_Package-Upgrade
release
分支列表
标签列表
${ item.name }
创建分支
${ searchTerm }
从 '5fa60706'
${ noResults }
8 次代码提交 (5fa60706-4e2d-4366-8b3a-f1b54b61a4de)
作者
SHA1
备注
提交日期
Jacob Stove Lorentzen
a394c6e4
Latest Dev and Readme without Vivox
3 年前
UnityJacob
4dc33191
merging in the working plastic branch.
3 年前
UnityJacob
e4cf51c3
Cleaned up Out of date scripts.
3 年前
Thomas Coldwell
c5af4590
Get everything compiling again
3 年前
UnityJacob
5a5209dc
Pulled in latest Renames from Plastic Branch
3 年前
nathaniel.buck@unity3d.com
abd52623
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 年前
nathaniel.buck@unity3d.com
678fd232
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 年前
nathaniel.buck@unity3d.com
42535b51
Tidying a bit, especially the tests. Removing uninformative tests and adding a little context. Removing a couple test-only methods.
3 年前