# Suppressing presence events sent to client

**URL:** <https://forum.heroiclabs.com/t/suppressing-presence-events-sent-to-client/3598>\
**Category:** Game Design\
**Created:** [March 9, 2023, 12:56pm UTC](https://forum.heroiclabs.com/t/suppressing-presence-events-sent-to-client/3598 "2023-03-09T12:56:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![totebo](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/totebo/32/528_2.png) [@totebo](https://forum.heroiclabs.com/u/totebo)\
**Post date:** [March 9, 2023, 12:56pm UTC](https://forum.heroiclabs.com/t/suppressing-presence-events-sent-to-client/3598/1 "2023-03-09T12:56:18Z")

</div>

My game uses the lua runtime and lua client code.

The join/leave messages are handled by custom code picked up by the client with `socket.on_match_data()`. This means events sent to the client that are picked up with `socket.on_match_presence_event()` are superfluous.

Is there a way to suppress the `socket.on_match_presence_event()` events being sent to the client, to save on server bandwidth and CPU?

Alternatively, is there a way to tag on information to the match presence events, so I can use those instead of sending custom events for join/leave?

The additional data I need to send when players join are position, tint colour, display name and other properties describing the players.

---

<div class="post-metadata">

**Author:** ![lugehorsam](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/lugehorsam/32/314_2.png) [@lugehorsam](https://forum.heroiclabs.com/u/lugehorsam)\
**Post date:** [March 9, 2023, 3:46pm UTC](https://forum.heroiclabs.com/t/suppressing-presence-events-sent-to-client/3598/2 "2023-03-09T15:46:58Z")

</div>

Hey Totebo, the match presence events comprise such a trivial amount of data that it won’t matter to your server performance.

We don’t provide a way to tag presence events with metadata but you should have each player send a `MatchData` payload after they join with their properties. That way you can potentially reuse any opcodes there for future changes to position, etc.

---

<div class="post-metadata">

**Author:** ![totebo](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/totebo/32/528_2.png) [@totebo](https://forum.heroiclabs.com/u/totebo)\
**Post date:** [March 9, 2023, 6:07pm UTC](https://forum.heroiclabs.com/t/suppressing-presence-events-sent-to-client/3598/3 "2023-03-09T18:07:18Z")

</div>

I thought that might have been the case. Thanks!