translators
8,403
edits
Changes
Jump to navigation
Jump to search
Line 340:
Line 340: − + − − Line 742:
Line 740: − {{SMAPI upcoming|3.6|content= Line 775:
Line 772: − }}
Modding:Modder Guide/APIs/Events (view source)
Revision as of 18:50, 20 June 2020
, 18:50, 20 June 2020update for SMAPI 3.6 release
|group = Multiplayer
|group = Multiplayer
|name = PeerConnected
|name = PeerConnected
|desc = {{SMAPI upcoming|3.6}}
|desc = Raised after a connection from another player is approved by the game. The event is raised for any player (whether host or farmhand), including when the connecting player doesn't have SMAPI installed. This happens after <tt>PeerContextReceived</tt>.
Raised after a connection from another player is approved by the game. The event is raised for any player (whether host or farmhand), including when the connecting player doesn't have SMAPI installed. This happens after <tt>PeerContextReceived</tt>.
The player is connected to the game at this point, so methods like <tt>Game1.server.kick</tt> will work.
The player is connected to the game at this point, so methods like <tt>Game1.server.kick</tt> will work.
===Custom priority===
===Custom priority===
SMAPI calls event handlers in the same order they're registered by default, so the first event handler registered is the first to receive the event each time. This isn't always predictable, since it depends on mod load order and when each mod registers their handlers. This order is also an implementation detail, so it's not guaranteed.
SMAPI calls event handlers in the same order they're registered by default, so the first event handler registered is the first to receive the event each time. This isn't always predictable, since it depends on mod load order and when each mod registers their handlers. This order is also an implementation detail, so it's not guaranteed.
}
}
</source>
</source>