Event Handlers and Multiplayer Clarification Needed

[Sarah]

Might be an odd question but how do event handlers and multiplayer work in respect to UI processing?

Say Player 1 activates UI mode. This sets an event handler to be a UI processor and require the mouse. Player 1 should be frozen with a mouse cursor on the screen and able to interact with whatever Ui is getting drawn.

My question is, what happens to the other players? They don't freeze as well do they?

[Player701]

GZDoom does not have actor replication. If you set IsUiProcessor to true for one player, it won't be automatically changed for other players as well. To enable UI input for a certain player only, you can compare the number of the player that activated the event with consoleplayer:

Code: Select all

class MyEventHandler : EventHandler
{
    override void NetworkProcess(ConsoleEvent e)
    {
        if (e.Name == "my_ui" && e.Player == consoleplayer)
        {
            // This code only executes for whoever's triggered the event.
            IsUiProcessor = true;
        }
    }
}

For other players IsUiProcessor will remain false, so they won't freeze.

[Sarah]

Ah ha, ok thank you! This question cropped up as I'm in the process of overhauling my net command system to isolate commands based on player number. So thanks again, I don't have a good way to test multiplayer so I have to ask the dumb/odd questions.

[Player701]

I don't have a good way to test multiplayer so I have to ask the dumb/odd questions.

You can always run a local multiplayer session by starting more than one instance of GZDoom, one with -host and the other(s) with -join localhost.