netrek-dev folks,

Question 1: On continuum.us.netrek.org <http://continuum.us.netrek.org/>, if my client doesn’t send any commands for 20-30 seconds, I get ghostbusted.  It seems like the server wants some sort of activity keepalive.  Any ideas?  There is a SP_PING and a CP_PING_RESPONSE, but I don’t see a CP_PING.  What should I send periodically?

Question 2:

I’m having trouble with the “picking team” logic in my netrek client.

The server sends an SP_MASK packet:
struct mask_spacket { /* SP_MASK py-struct "!bbxx" #19 */
    char type;
    char mask;
    char pad1;
    char pad2;
};
Here’s what the currently online servers send:
continuum.us.netrek.org <http://continuum.us.netrek.org/> sends mask = 15 (fed + rom + kli + ori)
netrek.beesenterprises.com <http://netrek.beesenterprises.com/> sends mask = 3  (fed + rom)
pickled.netrek.org <http://pickled.netrek.org/> sends mask = 2 (rom)

Then the client sends a CP_OUTFIT packet:
struct outfit_cpacket { /* CP_OUTFIT py-struct "!bbbx" #9 */
    char type;
    char team;
    char ship;
    char pad1;
};
It looks like the “Team” has to be an integer between 0 and 3 inclusive:
netrek-server-vanilla/ntserv/getentry.c:
            if (teamPick < 0 || teamPick > 3) {
                new_warning(UNDEF,"Get real!");
                sendPickokPacket(0);
                teamPick= -1;
                continue;
            }

On beesenterprises.com <http://beesenterprises.com/>, when I send team = 0 I end up rom.  Anything else I am rejected.
On pickled.netrek.org <http://pickled.netrek.org/> when I send team = 0 I end up rom. Anything else I am rejected. 
On continuum.us.netrek.org <http://continuum.us.netrek.org/>, when I send team = 0, I end up rom.  Anything else I am rejected.

Is there a way to select teams?  What does the team = 0 or 1 or 2 or 3 mean in the CP_OUTFIT packet?

I have a pulldown menu with the “preferred team”, but it doesn’t work the way a player would expect.

Darrell






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.us.netrek.org/pipermail/netrek-dev/attachments/20190328/8dd753b8/attachment.html>