"PlayerStart" and "playerEnd" event on the client
See original GitHub issueIt would be nice to have an event in the client called playerStart
and playerEnd
, and to be executed every time a guild player starts or ended.
I say this idea in order to better manage the control of players from one place.
Example:
const client = new Shoukaku(options);
client.on("playerStart", (guildId, player) => console.log(guildId, player));
client.on("playerEnd", (guildId, player) => console.log(guildId, player));
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Player Start | Unreal Engine 4.27 Documentation
The ability to spawn a player into the world at any location is a very useful feature for any game. Unreal Engine 4...
Read more >SpawnSharedAsset - Core Documentation
Connect up the broadcast events that the server will broadcast to the client to handle updating the UI for when to jump and...
Read more >Adding Player Start - Learning Unreal Engine Game ... - O'Reilly
For every game, you need to set where the player will spawn. Go to Modes | Basic | Player Start. Click, hold, and...
Read more >VideoCapX ActiveX control reference - Fath Software
Events: ConnectionRequest. This is invoked on a server when client connects. At server side, use these steps: 1. connect the camera. 2. start...
Read more >Understanding Standard eCounsel Reports
Matters/Player/Start Date Matters/Player/End Date. Contact. The main contact for the client for the matter. The player assigned a role of ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I can consider this, but definitely will not ship in current 1.6.x, if considered, expect this to be on 2.x.x, and most likely is not a Shoukaku issue, because as far as I know, me, and other users that use this lib don’t encounter this particular issue
Check latest next-branch commits, new events on Shoukaku Class have been added, named
playerReady
andplayerDestroy