[Bug] The Gamesession allocation verification error causes the player to appear blank or to drop out of service

[Adelaide114514]

在#2324 中提到服务端因无法处理而导致白屏掉线 通过对比旧版本grasscutter核心我发现新版本中删除了一条判断 In # 2324, it was mentioned that the server could not process the request and led to a white screen and a disconnect By comparing the old version of grasscutter core, I found that a judgement was deleted in the new version 通过会话的状态来确定是否需要进行解密操作 在我的理解当中新版grasscutter如果删除该判断无论是什么状态都会解密 这会不会导致解密不正确，因为他可能会通过会话状态而变化？或者是Gamesession的变化等等导致不一致而使得玩家掉线或者是断开连接，我通过尝试添加该条判断，得到了以下结果 Determine whether decryption operation is required based on the state of the session In my understanding, if the new version of Grasscutter is deleted, the judgment will be decrypted regardless of its status Will this lead to incorrect decryption, as it may change through session state? Alternatively, changes in Gamesession or other factors may cause inconsistencies and cause players to drop or disconnect. By attempting to add this judgment, I have obtained the following results 这使得一个玩家都无法进入，之前还能进入八个左右的玩家才开始掉线白屏，现在是一个都无法进入，这是否关于第一次分配Gamesession时就不一致所导致的？ This makes it impossible for any player to enter. Previously, players who could only enter around eight players started to lose their connection and have a blank screen. Now, none of them can enter. Is this caused by the inconsistency in the first Gamesession allocation?

[KingRainbow44]

database.

[Ayin-a]

数据库。

I encountered the same problem as #2324. When the number of players reaches 8 or more, other players experience disconnection and white screen issues upon rejoining.

My friend made some modifications to the GC to test it.

Test details: First, let the game have 8 or more players online, then refuse login for players who haven't entered the game yet (similar to version verification). During the test, there were 14 players online, and more than 20 players were refused login. Although the number of players online exceeded 8, there were no disconnection and white screen issues. Once we allowed the previously refused 20+ players to log in again, the disconnection and white screen problems occurred again. This is the detailed description of the problem provided by my friend.

[KingRainbow44]

can you try stress testing this branch of Grasscutter? i tried to include some optimizations for data saving, as well as packet handling but i dont have the resources to test it against more than 2 players

[Adelaide114514]

你能尝试对Grasscutter的这个分支进行压力测试吗？我试图包括一些用于数据保存和数据包处理的优化，但我没有资源在超过 2 个玩家上进行测试

好的，我对此分支未作任何更改进行了测试 测试结果少了乱踢人的问题[即人数超过约五人以上就会随机踢人 原因是此账号重复登陆 但是我可以确定以及肯定 并没有重复登录 此问题最新的Grasscutter分支 1.7.X版本仍然存在]此问题得到了修复

第二个问题:对比于1.7.XGrasscutter分支他的问题表现于10-18人左右时出现白屏无进度条 但是此分支表现是固定12人且无法更多 不像最新的版本是一个大概人数 同时白屏[如果是注册新号则会卡在过场动画的取名确定地方 确定无法使用 服务端也无任何反馈] 如果需要日志我可以提供更多 Okay, I have tested this branch without making any changes The test results have reduced the issue of random kicking [i.e., if the number of people exceeds about five, random kicking will occur due to repeated login of this account, but I can confirm and confirm that this issue still exists in the latest Grasscutter branch 1.7. X version]. This issue has been fixed But the number of people was still controlled at twelve, compared to the 1.7 XGrasscutter branch. His problem was manifested in a white screen with no progress bar when there were around 10-18 people However, this branch has a fixed number of 12 people and cannot have more. Unlike the latest version, which has an approximate number of people and a white screen at the same time, if registering a new number, it will get stuck in the naming confirmation area of the cutscene animation and cannot be used on the server without any feedback If you need a log, I can provide more

[Adelaide114514]

你能尝试对Grasscutter的这个分支进行压力测试吗？我试图包括一些用于数据保存和数据包处理的优化，但我没有资源在超过 2 个玩家上进行测试

好的，我对此分支未作任何更改进行了测试 测试结果少了乱踢人的问题[即人数超过约五人以上就会随机踢人 原因是此账号重复登陆 但是我可以确定以及肯定 并没有重复登录 此问题最新的 Grasscutter分支 1.7.X版本仍然存在]此问题得到了修复

第二个问题：对比于1.7.XGrasscutter分支他的问题表现于10-18人左右时出现白屏无进度条 但是此分支表现是固定12人且无法更多 不像最新的版本是一个大概人数 同时白屏[如果是注册新号则会卡在过场动画的取名确定地方 确定无法使用 服务端也无任何反馈] 如果需要日志我可以提供更多 好的，我已经测试了这个分支而不进行任何更改 测试结果减少了随机踢的问题[即，如果人数超过五人左右，由于重复登录此帐户，将发生随机踢腿，但我可以确认并确认此问题仍然存在割草树枝 1.7.X 版本]。此问题已修复 但与 1.7 XGrasscutter 分支相比，人数仍控制在 10 人。他的问题表现为没有进度条的白屏，当时大约有 18-12 人，但是，这个分支的固定人数为 <> 人，不能更多。与最新版本同时拥有近似人数和白屏不同，如果注册新号码，它将卡在过场动画的命名确认区域中，并且在没有任何反馈的情况下无法在服务器上使用 如果您需要日志，我可以提供更多

问题:新号无法确认名字后退出再次进入直接白屏 问题2:上述理解错的点在于新号似乎注册到一定程度就无法注册了，服务端从12人在线变成了9人可仍然注册不了 旧号可以使用[新号默认名字都是旅行者 但实际取名并不如此] 问题3:从问题二中得到只能注册大约十多个账号进行游玩 更多的账号就如同上图全是默认旅行者白屏无法进入[这十多个账号只要退出之后再次进入同时也是白屏无法进入]