Announcement

Collapse
No announcement yet.

Query protocol with 1.3 Patch

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • replied
    Yep, I not understand algorithm of new query and all bytes in the query strings. Upgrade script who know how...

    Leave a comment:


  • replied
    Originally posted by omihaz View Post

    P.S. This script some times output not valid results.
    ^^ It is the ping-value which sometimes returns a cube in front

    Leave a comment:


  • replied
    Originally posted by WooRus View Post
    omfg how my ip entered in your script ?

    its you Ddos me all time with test this script ?
    =D Yep, test script on the 1.3 server version with players.

    P.S. This script some times output not valid results.
    P.S2: Ддоса не было, и тестил не долго, и спасибо! хех...

    Leave a comment:


  • replied
    Originally posted by omihaz View Post
    Hi!

    My Fixed version cruz's script.
    Add players
    Status: beta, I programming for self only

    Download here:
    http://www.unreal-club.com/monitorin...rverquery.phps
    omfg how my ip entered in your script ?

    its you Ddos me all time with test this script ?

    Leave a comment:


  • replied
    Originally posted by WooRus View Post
    sadly .... developers not post here ?
    Amazingly, they don't post in the Server Admin section that I can tell. I've had a few threads in here but never any Epic response. I would think they would be in here before anywhere else. Diehard UTers paying money to run servers and keep their game alive...

    Leave a comment:


  • replied
    Coooool !

    Leave a comment:


  • replied
    Fixed version cruz's script

    Hi!

    My Fixed version cruz's script.
    Add players
    Status: beta, I programming for self only

    Download here:
    http://www.unreal-club.com/monitorin...rverquery.phps

    Leave a comment:


  • replied
    Yes, i tested it earlier.
    But the main problem is, that mostly 'sockets' is disabled by the provider.
    But the received data are more clean:
    [] -> []
    [score_] -> []
    [team_] -> []
    [pid_] -> []
    [team_t] -> []
    [Team] -> [Team]
    [0] -> []
    I will try to compose functions of cruz's script and apophis's.
    I hope the main reason is not the 'socket' or 'fsockopen'.

    Thanks....

    Leave a comment:


  • replied
    Have you tried the PHP query class written by Apophis?

    http://www.unrealadmin.org/forums/sh...456#post135456

    Leave a comment:


  • replied
    Originally posted by dirrty[starbuck] View Post

    So it would appear that the php code needs some tweaking (in the way it manipulates the raw return values)...

    ...recently working on it.

    But today i want to join my server:
    UT3-Serverlist says 10/10 Players.
    So I joined the server as a spectator (1 is allowed) and did a F1 for the scoreboard,
    Scoreboard shows me 9 players.
    I tried to join the game, but it fails.
    So I wait until the next player disconnects and i retried joining the match, succesfull.
    In the Query-script 1 player is missed (as i wrote).
    But 'ingame' I have the same issue too.
    I think this is not a problem only in the query-script. ..?

    Leave a comment:


  • replied
    ....OMFG.....That needs more skill.....
    Yes I am using cruz's script.
    I try to find out the problem until there is no other php-class

    greetz

    Leave a comment:


  • replied
    Originally posted by kotraeppchen View Post
    Everytime I do a query one player is not listet.
    In this example numplayers says 15 (Same error with other values).
    Anyone else got this query-error?
    I assume you're using a php query based on Cruz's UT3 Server Query Functions v1.3? I ran a some tests a couple nights ago using this same php code and came up with the same results as you (and various other oddities in ping, score etc)...

    I have a query class written in C# (used for my UT3 Server Query Vista Gadget)... I ran some tests and the raw values returned by it are accurate (no missing players,scores,pings etc).

    So it would appear that the php code needs some tweaking (in the way it manipulates the raw return values)...

    Leave a comment:


  • replied
    Everytime I do a query one player is not listet.
    In this example numplayers says 15 (Same error with other values).
    Anyone else got this query-error?

    [numplayers] => 15

    [NinjaMenou] => woorus
    [xxxPhOeNiXxxx] => monocerotis
    [rfgu] => motka_rast
    [Klim_4ugunkin] => pippo_x93
    [Jade/////250590] => The_Dong_MAN
    [zlgota] => KYPROS12345
    [Exius] => minowa
    [22] => 25
    [31] => 27
    [24] => 112
    [28] => 36
    [23] => 27
    [37] => 7
    [6] => 3
    [176] => 28
    [32] => 26
    [44] => 84
    [228] => 72
    [20] => 23
    [19] => 16
    [13] => 8
    [1083] => 1082
    [1072] => 1071
    [1061] => 1060
    [1058] => 1018
    [1077] => 1087
    [1088] => 1089
    [1090] => 1091

    Leave a comment:


  • replied
    Copy-pasted here too
    --------
    Yep, there is an array of player info equal in length to the "numplayers" value of the server, with 6 values reported for every player:
    player - Player name
    team
    score
    deaths
    ping
    playerid

    In the query protocol, those keys are named like so:
    Key_Number

    With 'Key' representing one of the 6 keys listed above, and 'Number' representing a value between 0 and 'numplayers', for example: team_0, player_5, score_8 etc.


    So, to get the values for the first player, you just append _0 to each of the six key values above, and search for those.

    Leave a comment:


  • replied
    Originally posted by {DvT}JonahHex View Post
    I asked about getting player info from the UT3 Server Query Protocol in the UnrealAdmin forums last February. Not possible at that time. I just resurected that thread and that question over there. I'll report the answer here when I get a reply.

    Essentially never. This is a users forum, not a tech support forum .
    ffs ...... where find it ffs =(
    gametracer already do it =(

    Leave a comment:

Working...
X