Jump to content

Home

RCON STATUS is freezing


Lord Sokar

Recommended Posts

Mine is pretty consistant, it shows only 3 or 4 and that's it. Never has it given me a good list.

 

It sucks to tell someone you're going to kick them only to not be able to.

 

If you have any luck figuring this out, please come back here and let me know how you fixed it. This really is a problem.

 

Anyone else got a suggestion?

Link to comment
Share on other sites

^ Right now, the console isn't an option for me.

 

Here is what I get with 'rcon status' right now:

 

map: ffa_bespin

num score ping name lastmsg address qport rate

--- ----- ---- --------------- ------- --------------------- ----- -----

0 3 181 Player1 0 62.31.213.114:28070 12926 4000

1 34 51 Player2 0 68.49.27.61:28070 59588 25000

2 22 80 Player3 50 68.45.127.73:28070 64037 4000

3 0 93 Player4 0 65.35.126.239:28070

 

As you can see, although there are 12 players on the server, the status abruptley ends after 3 1/2.

Link to comment
Share on other sites

Well, I'm just letting you know that they fixed that problem in v1.03. If you want to stick with v1.02--then you're stuck with the problem. Now, if I remember correctly, the server console status command was broken in v1.02c (windows). So, if you downgrade to 1.02b (windows) you can at least get around that. However, the rcon status command didn't get fixed until 1.03. Sorry to be the bearer of bad news. :(

Link to comment
Share on other sites

The problem still exists in 1.03 and is caused (as I said) by the ANSI color coding in some people's names. You will get only so many lines of the STATUS command and then it will stop.

 

If you kick the person in the last line you see, I bet the problem goes away... ;)

Link to comment
Share on other sites

It was always my understanding that the original problem was due to a buffer limitation that goes back to Q3. If you figure out a particular combination of color codes that causes the problem, I could enable my admin bot to auto-kick those people. ;)

Link to comment
Share on other sites

This problem does not happen some of the time, or stop only when it haves a problem with certain names.

 

It stops everytime, and in the same place EVERYTIME. Without fail.

 

I understand the whole 1.03 thing, but at the same time, I have no desire to start a server for a game that I do not enjoy. I'm doing this because I love 1.02 and want to keep playing it. If we're lucky, there won't be any more patches and 1.02 will live a long, long time. Nonetheless, I'm putting my money where my mouth is and keeping this thing going the way it was meant to be.

 

But I have taken into consideration an earlier version (was there an A and a B version of 1.02?). Also, if you know anywhere that I can download these versions, I would be greatful.

Link to comment
Share on other sites

Linux or winblows? I saved copies of the linux versions for my own personal archive. You never know when you might need to "downgrade". ;)

 

Oh, just to let you know, Aerys. The rcon status command works perferctly every time on my 1.03a server. So, it there's some combination of ansi colors that's the cause, I'm the luckiest admin around because nobody on my server ever uses them. :D

Link to comment
Share on other sites

MatrixCPA,

 

Both versions, actually. I have a duel on Win32 and two on Linux. My email is courtney@housequake.net if you want to email. If not, I have an FTP server that I believe is set up for write permissions (I'll have to check), you can email me for the address. I appreciate your help.

 

Oh and just to let you know, I set up a new server last night with 1.02c and got the same thing, ONLY WORSE! Yeah, it bites.

 

Thanks for your help.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...