Assuming you're using some kind of state management in your game, you could set a state variable:

//serious pseudo-code :)

//in the network code

if( msg == "kick")

    state = GameState.ShowKickMsg

//in the game code
switch (state)

GameState.ShowKickMsg - show kick messagebox

GameState.Kick - exit the game

//in the messagebox code

state = GameState.Kick

multimolti:

Yeah, this is what my program.cs looks like, but it doesn't work!! The game exits without calling the MessageBox.Show() method!

If your code isn't working you're going to have to post it so we can see what you're doing.

edit: Tried a sample and the MessageBox doesn't show if you put it in the program.cs or if you override the OnExiting when you exit the game using the keyboard or gamepad. :(

multimolti:

The gm variable is my GameManager, and because it's static, the changes during the Game1() should be applied, shouldn't they?

Just a side note -- I think the larger problem is you are using ASCII words for your client-server packets. A packet sniffer and a clever Winsock/System.Net.Sockets developer could start kicking everyone in the game. Best to use an encryption/decryption method for your packets. Cheers!

Caetris:

Just a side note -- I think the larger problem is you are using ASCII words for your client-server packets. A packet sniffer and a clever Winsock/System.Net.Sockets developer could start kicking everyone in the game. Best to use an encryption/decryption method for your packets. Cheers!

What??

He's only parsing messages from the server (i guess), nobody can send "kick" directly to a player.
And in this case encryption will only be security by obscurity, if somebody can sniff the packets being sent when you kick a player then they can just send the encrypted string they got from the packetsniffer right away.

There is no problem in using plain text for messages.

What can become a problem however is if someone recompiles the game and outcomments the line where you call game.Exit(), then you will have an unkickable player. But this can easily be solved by just ignoring messages from that client on the serverside.

Nick Gravelyn:

That's strange. Here are the exact steps I just took a moment ago to get this all working.

1) Create a new Windows project.
2) Add a reference to System.Windows.Forms.
3) Add line System.Windows.Forms.MessageBox.Show("You have been kicked"); to the end of your Main method. Run game and exit; message box shows up.
4) Added public static bool Kicked = false; to Program declaration. Added if (Kicked) to show the message box. Run game and exit; message box doesn't show up (it shouldn't).
5) Go into Game1.cs. Add line Program.Kicked = true; in Game1's constructor. Run game and exit; message box shows up again.

How are you exiting?

emachine:

Do you have 2 different classes with a playerKicked member, and are you setting one to true, but then checking the other (which I assume is staying false)?

// program.cs
    static class Program
    {
        public static bool playerKicked = false;
        ...

            if (playerKicked)
            {
                MessageBox.Show("You got kicked from the server!", "Kicked");
            }
    }

// game1.cs
                       switch(receivedata) ...
                            case "kick":
                                Program.playerKicked = true;
                                ...
                                this.Exit();
                                break;

Machaira:

How are you exiting?