player_spawn event, does it fire more than once?

[BackRaw]

Hi,

in EventScripts (CSS), we had to check if the team index was above 1 on player_spawn because it fired even before player_activate fired (or something like that, can't exactly remember).

Code: Select all

import es

def player_spawn(ev):
    if int(ev["es_userteam"]) > 1:
        # only after this if, the player actually spawned "physically", so to speak

Do we still need this check?

Btw: why doesn't [syntax="python"] .... [/syntax] work any more? Or is it just on my machine? lol

[Ayuto]

Yep, but remember that es_userteam is a variable defined by EventScripts. This might be more effective:

Code: Select all

from events import Event

players = set()

@Event
def player_spawn(ev):
    userid = ev.get_int('userid')
    if userid not in players:
        players.add(userid)
        return
       
    # Your code here...

@Event
def player_disconnect(ev):
    players.discard(ev.get_int('userid'))

The syntax higlighter is broken and unfortunately La Muerte does not have the required permissions to fix that.

[sicman_adrian]

Can also check life state to see if there physically alive

[BackRaw]

Can also check life state to see if there physically alive

Good point, thanks!

[BackRaw]

Yep, but remember that es_userteam is a variable defined by EventScripts. This might be more effective:

Code: Select all

from events import Event

players = set()

@Event
def player_spawn(ev):
    userid = ev.get_int('userid')
    if userid not in players:
        players.add(userid)
        return
       
    # Your code here...

@Event
def player_disconnect(ev):
    players.discard(ev.get_int('userid'))

The syntax higlighter is broken and unfortunately La Muerte does not have the required permissions to fix that.

That does the half lol, I want to execute code when the player phisically spawns (the last time player_spawn fires for that player) you know? I guess the alive or team index check are the two best.
Thanks for the info on the syntax highlighter =)

[Ayuto]

It actually does that. The first time a player spawns he isn't in our set. So, we add him to the set and return. After that everything after "# Your code here..." will be executed.

[BackRaw]

Yes but what if player_spawn fires 3 times? the first time the index gets added to the set, the second time (maybe player_activate hasn't fired yet) the code gets executed which is what I don't want lol

[Ayuto]

I have never seen player_spawn firing 3 times.

[Omega_K2]

I have never seen player_spawn firing 3 times.

Might be a bug with the engine/game (or caused by other mods that force spawn people..)

[BackRaw]

lol, help me on this: how many times does player_spawn fire?? twice?

[XKillerBoy]

Depends on how many rounds, and if you respawn players.
But just do a check if player_activate has been run first.