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

[BUG] ARRCON shows previous response for current command #15

Open
rykugur opened this issue Apr 11, 2023 · 3 comments
Open

[BUG] ARRCON shows previous response for current command #15

rykugur opened this issue Apr 11, 2023 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@rykugur
Copy link

rykugur commented Apr 11, 2023

# System Information

  • OS: endeavourOS
  • Version: Linux 6.2.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 30 Mar 2023 14:51:14 +0000 x86_64 GNU/Linux
  • Shell (Windows-Only):

Using ARRCON 3.3.5 (latest release).

# Bug Description

Upon successful authentication (either manually or using a saved session, when I type a command, I get [no response]. The second command I type, regardless of what it is (even if it's an invalid command), displays the results of the first command I typed. The third command will display the results of the second. And so on. Here's an example:

Authentication Successful.
Use <Ctrl + C> or type "exit" to quit.
RCON@...> players
[no response]
RCON@...> who
Players connected (0): 
RCON@...> players
Unknown command who
RCON@...> players
Players connected (0): 
RCON@...> ^C

The server I'm connecting to is a Project Zomboid server, running in docker. Other rcon clients I have tried do not have this problem.

# Reproduction Steps

Connect to a Project Zomboid server (you can relatively easy set one up using one of the docker containers available; I'm using https://github.com/PepeCitron/projectzomboid-server)
Try a command
Try an invalid command
Try a command

@rykugur rykugur added the bug Something isn't working label Apr 11, 2023
@preppie22
Copy link

Bumping this because I'm having the exact same problem.

@radj307
Copy link
Owner

radj307 commented Feb 29, 2024

This happens because of a limitation in ARRCON v3's design. The client isn't waiting long enough for the server's response before assuming it just didn't respond at all.

You can fix this by increasing the value of the iSelectTimeout setting past its default of 500 (milliseconds) in ~/.config/ARRCON/ARRCON.ini. Increase it by 500 and try again, repeating as necessary until the issue goes away.

The main goal of ARRCON v4 is to improve networking robustness, which includes this bug. I switched to using Boost ASIO for networking instead of raw sockets, which will remove the need for manually setting delays.

@radj307
Copy link
Owner

radj307 commented Mar 3, 2024

Please try v4.0.0-pr1 and let me know if the problem is resolved.

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

3 participants