Library

Anti-AFK

Detect idle players by movement and by chat, with a 12 s tolerance.

Anti-AFK flags as AFK a player who stayed 12 seconds without moving and without chatting. Either signal resets the clock.

ts
room.enableAntiAfk();                                  // default: 12 s

room.on('player-afk',  (id) => room.kickPlayer(id));   // once, when they become AFK
room.on('player-back', (id) => room.chat(`player ${id} is back`));

room.isAfk(playerId);                                  // one-off check
room.disableAntiAfk();

Options

ts
room.enableAntiAfk({
  thresholdMs: 12_000,     // idle time until AFK
  checkIntervalMs: 1_000,  // check frequency
});

The default time is also available as the AFK_THRESHOLD_MS constant.

Who is watched

Only players on a team during a match. Spectators and the bot itself are ignored. The clock starts when the match starts (or when the player joins a team during the match) and is discarded when the match ends.

Where the signals come from

SignalSourceEvent
ChatSocket.IOchat-message
MovementSocket.IO (packet 7) and WebRTC (input frames)raw-packet / peer-input

Movement arrives in two ways: through Socket.IO, in packet 7 ([7, id, {i, f, c}], with the key mask and the frame), which is the most reliable, and through the WebRTC input frames. The library uses both. A held key counts as activity: someone keeping a direction pressed is not flagged AFK just for not generating new events.

peer-input delivers { playerId, peerID, data }, with the frame already tied to the right player. You can use it directly for activity statistics.

Important limitations

  • Needs the real mode. The peer-input event only exists when the room uses the real transport (with peerID), as in createRoom() and joinRoom(). In tests with a fake transport, emit peer-input manually.
  • Signal reliability. If, for some reason, no movement frame arrives during a whole match, the signal is not reliable. The 24/7 room ignores automatic AFK in that case, so it never punishes everyone over a network failure. Do the same if you apply penalties.

Complete example

ts
import type { BonkRoom } from 'bonktools';

export function setupAntiAfk(room: BonkRoom): void {
  room.enableAntiAfk();

  const name = (id: number) => room.state.players.get(id)?.userName ?? `#${id}`;

  room.on('player-afk', (id) => {
    room.chat(`${name(id)} is AFK!`);
    room.kickPlayer(id); // remove this line if you only want to warn
  });

  room.on('player-back', (id) => room.chat(`${name(id)} is back.`));
}