Skip to content
Discussion options

You must be logged in to vote

Packet 147 itself

In my packet library's naming: PlayerSetLoadoutSlot (could/should be renamed to PlayerSetLoadoutId or something)
It tells the server (or client in SSC with some caveats) to switch the active loadout slot in memory.

Handler implementation is generally client-authoritative:

C2S: It's a notification of client-side change, you can't "block it", you have to manually revert the change if you want
S2C: Requires SSC, client still gets to decide if it wants to make the change or not - in particular, being considered crowd-controlled (silence, petrify, etc.) can cause the client to ignore the server's loadout change.

Its structure is:

struct PlayerSetActiveLoadout {
    byte UserId;

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by manfromfms
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants