Posts: 836
Threads: 107
Joined: Sep 2010
Reputation:
0
Anyone else experience a bug with the update 10 of sscanf 2.6 where it doesn't recognize ID 4 as a connected player? This means I can't execute commands to ID 4, like /ban 4, /kick 4, /get 4, /goto 4, nothing works. The specifier I use is "r".
Posts: 5,314
Threads: 12
Joined: Aug 2010
Reputation:
0
The include is sscanf2, right ?
It's linux or windows ?
Posts: 836
Threads: 107
Joined: Sep 2010
Reputation:
0
Yea it's sscanf2 and it's a windows server.
Posts: 883
Threads: 131
Joined: Mar 2011
Reputation:
0
You can try "u" instead of "r"
Posts: 836
Threads: 107
Joined: Sep 2010
Reputation:
0
I tried "u" but I was getting some problems, so I tried "r". I sent a PM to ******, hopefully he'll give me instructions on what to do.
Posts: 836
Threads: 107
Joined: Sep 2010
Reputation:
0
Bump...Anyone else experiencing this?
Posts: 435
Threads: 24
Joined: Jun 2011
Reputation:
0
Yes , happened to me also... Dunno why
Posts: 836
Threads: 107
Joined: Sep 2010
Reputation:
0
All commands that need parameters from a user/id as I stated, I tried it with both the "u" and "r" specifiers and it doesn't work. The commands work for all other IDs, except ID 4.
