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

Exception reported: Client X is not in game Error #7

Closed
RoonMoonlight opened this issue May 4, 2019 · 4 comments
Closed

Exception reported: Client X is not in game Error #7

RoonMoonlight opened this issue May 4, 2019 · 4 comments

Comments

@RoonMoonlight
Copy link

@RoonMoonlight RoonMoonlight commented May 4, 2019

Hi,

I keep getting this error about Exception reported: Client X is not in game(Note: X is the number, and the number is random).
Please note that I'm using the Bots Features on the server.

Can you fix this issue or do you have any solutions about this?

@RoonMoonlight
Copy link
Author

@RoonMoonlight RoonMoonlight commented May 4, 2019

L 05/04/2019 - 21:47:28: [SM] Exception reported: Client 7 is not in game
L 05/04/2019 - 21:47:28: [SM] Blaming: smac_speedhack.smx
L 05/04/2019 - 21:47:28: [SM] Call stack trace:
L 05/04/2019 - 21:47:28: [SM] [0] IsPlayerAlive
L 05/04/2019 - 21:47:28: [SM] [1] Line 123, Y:\SourcemodProjects_SMDevENV\addons\sourcemod\scripting\smac_speedhack.sp::OnPlayerRunCmd

@Silenci0
Copy link
Owner

@Silenci0 Silenci0 commented May 4, 2019

I think I see what the problem is and I will fix it soon. Also, what game is this for?

@RoonMoonlight
Copy link
Author

@RoonMoonlight RoonMoonlight commented May 5, 2019

@Silenci0 Team Fortress 2.

@Silenci0
Copy link
Owner

@Silenci0 Silenci0 commented May 7, 2019

I did not run into this issue myself, personally, on my TF2 test server, but I think I found the issue and hopefully resolved it. The error you are seeing is due to whatever client 7 is no longer being connected and/or in game during the time that the check is run. Client 7 could easily be a player or a bot, but in either case, it took an action directly before disconnecting so the check would then fail at this step.

While I have, hopefully, resolved this issue in the latest 0.8.6.4 update, I cannot guarantee that an edge case won't occur depending on the timing of the action vs. the disconnect. Unless this issue completely breaks the plugin, I think it can safely be ignored. Thanks for the report, closing issue.

@Silenci0 Silenci0 closed this May 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants