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.

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

Player disconnected feedback #224

Closed
jzy-chitong56 opened this issue Jan 13, 2024 · 7 comments
Closed

Player disconnected feedback #224

jzy-chitong56 opened this issue Jan 13, 2024 · 7 comments
Labels
bug Something isn't working

Comments

@jzy-chitong56
Copy link
Contributor

jzy-chitong56 commented Jan 13, 2024

some feedback said human player disconnected , they use China Game platform , A few friends fight against AI together
The same issue will not occur in the previous AMAI version

this platform use 1.27a or 1.36.0 crack , and all1.27a embedded with platform APIs
Mainly used to obtain platform member level, ladder points, and item information purchased in the platform mall , and encapsulated trigger events/conditions/actions

Feedback suggests that there may be issues with inconsistent timelines and errors between players

The feedback also states that players experience disconnection when they using ZOOM adjustment function, whether it is built-in in BJ or built-in on the platform

I think either cache was used to handle the chat queue
Either some of my code affected the main branch

I suggest you consult HIVE to see if anyone has encountered this issue on Battle.net or other non Chinese platforms

@jzy-chitong56
Copy link
Contributor Author

It may be caused by consistent triggering conditions of map commands

-Zoom

SMUnlimited added a commit that referenced this issue Jan 14, 2024
Avoid using intensive camera functions within local triggers.
@SMUnlimited
Copy link
Owner

Give this commit 38687e2 a try to see if that fixes it.

@jzy-chitong56
Copy link
Contributor Author

Your master branch also crash

  • war3 1.29.2.2931
  • (24)Emersion v3.0 Standard Melee.w3x
  • 11 vs 12 + observer

Considering that the code did not occur before running

I suspect it was caused by DETECT_DOUBLE_EXP

image

@SMUnlimited
Copy link
Owner

v1.29 is not a safe version to be on as has known issues with AMAI. It will also explain no chat messages as well. Downgrade or upgrade to avoid those issues.

@jzy-chitong56
Copy link
Contributor Author

It is true that the problem cannot be found by checking the code, and it is difficult to find it. However, by disabling some job functions, the game can run until the end without crashing. Therefore, I have been trying to locate which line of code has the problem in the past few months, and I always believe that it is not a problem with the game, but an error in the code itself

I have run games on 1.36 before and game disappear directly, so I think changing versions cannot avoid it

Another issue is that at 1.36, while the game may run continuously in the foreground without causing any lag, I have tested that I usually switch to the desktop to check the code (only one display), and when I switch back to the game, the game will become 0FPS

@jzy-chitong56
Copy link
Contributor Author

chinese

Regular chat cannot display Chinese characters, only letters and numbers can be displayed
But the Strategy.txt is not affected
image

@jzy-chitong56
Copy link
Contributor Author

zoom Numerical recording should use arrays, with each player recording independently

@SMUnlimited SMUnlimited added the bug Something isn't working label Jan 27, 2024
SMUnlimited added a commit that referenced this issue Mar 2, 2024
Various spots were variables were being saved for only a single player which is a desync culprit.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants