Client.delete() crashes my demo

#1 Client is usually the ClientConnection object. You probably shouldn't be deleting it. It doesn't matter if your game is single player or not since Torque has no distinction between the two.

#2 Well I need some way to disconnect somebody off my server.

#3 My bad.
Well ya. You would do something like:

%client.delete("You were kicked from the server");

That should work.

#4 Yeah thats exactly what crashes me.

#5 Are you trying to delete yourself as a test?

If so, that's why you crash.

If not, could you specify what server you are running and how you are testing it?

#6 I don't think it should crash if you delete the player on a listen server...

#7 I think it would if your the one running the server.. no server then game would either drop or crash..
if he is running the server and then removes the main server client then no server.. right?
or maybe I am wrong..

#8 Ben, the tree structure is different for a listen vs. a dedicated. Although I have not personally tested it, just looking at it tells me that if you delete the MAIN client on a listen server you crash, simple as that. There is no provision for separating the player from his server on a listen. In fact, a listen server is one of the worst ways to test most code simply because it reacts tottaly different than a dedicated.

How many times have you seen "Works perfectly untill we try it on the LAN or NET, then it doesn't work at all"?


It's because the modes of operation are so different. Tell you what, I'll go run the test on the latest head and see what happens.

#9 Confirmed. Delete the main client in a single player or multiplayer listen server and you crash the client. Ironicly enough, you do not crash the server and it continues to function just fine. The hosting client see's all activity stop and his lag icon comes up. But instead of dropping to the lobby after the timeout which would normally happen to the client, the hosting client stays locked into his game screen indefinately(or untill he exits the game which also kills the server).

So as best I can tell,

%client.delete("message");

is working just fine but as I stated before, you cannot test it correctly on a listen server. You can create a dedicated server and log into it from the same computer using a client and test it correctly because it separates the client from the server(same machine doesn't matter)

#10 I believe you are right Gonzo. I remember doing some debugging where I was accidently deleting myself and I crashed. I think you need to disconnect before you delete.

#11 If you disconnect the client of a listen server the server quits and everyone gets dropped with the message "The server dropped the connection".

#12 Maybe i'm misunderstanding. If you are running a server that is not dedicated then when you disconnect the server quits. That is what it should do. No? Maybe I don't understand what you are trying to do or what you want to happen on %client.delete

#13 Michael

The thread has evolved into more info than was needed.

Entropy originally had crashing problems when using the client.delete() function. I determined that he was most likely using a listen server which could not be used to gain an accurate test result. The conclusion was the function was workin fine, his test method was flawed.

The rest of this has just been basicaly an info discovery and clarification thread. And yes, you would want your listen server to quit when the host client disconnects. And it does. But using what we have learned, it is possible to alter your scripts slightly and be able to quit out of a listen server. One good use for such a trivial feature would be the ability to quickly start a server for a buddy and after he logs in give him admin or other powers and then exit out while leaving the server running. In fact, I think I'm going to mod in the option to do it both ways now that I think about it.

#14 Cool that clears things up.

#15 I am running a dedicated server. It crashes when I try to %client.delete any connection coming in.

#16 Where is it crashing?

#17 Like I said, it is crashing when i call client.delete. Is there something I must do before I can use client.delete? Does the client have to be in the game already, or is simply being connected to the server enough?

#18 I meant, what line of C++ code...

#19 Well still no luck on this. I have put it off for a long time to see if anybody could tell me what's going on but nobody has. I absolutely *must* figure it out now.

I have to be able to disconnect a gameconnection in Gameconnection::Onconnect with script.

Like I said, %client.delete crashes the server. If I use a command to the client to disconnect, then the client crashes. I can close a gameconnection in GameConnection::onConnectRequest by sending an empty return, but it doesn't work in Gameconnection::Onconnect (which is what I need).

Please for the love of god somebody help.

#20 Here's the gdb info:

Program received signal SIGSEGV, Segmentation fault.
0x00609aba in NetInterface::handleConnectRequest(NetAddress const*, BitStream*)
(this=0x7c3c50, address=0x22f934, stream=0x22f850)
at sim/netInterface.cc:305
305 conn->setEstablished();