For the complete documentation index, see llms.txt. This page is also available as Markdown.

&roomcap

Set a server-side cap on how many guests can be admitted to a claimed room.

Director Option! (&director)

Aliases

  • &rcap

Options

Example: &roomcap=20

Value
Description

Integer greater than 0

Maximum admitted guests for the claimed room

Details

&roomcap sets a handshake-server admission cap for a claimed room.

https://vdo.ninja/?director=MyRoom&roomcap=10

On the official vdo.ninja service:

  • Default cap is 80 when not set.

  • Maximum accepted value is 80; higher values are clamped.

  • New join attempts are blocked when the room is full.

  • Pending approval requests count toward the cap so the room is not overfilled while the director is deciding.

  • Transfers into the destination room also respect the destination room's cap.

  • Matching &roomkey values can bypass a lower custom cap, but cannot bypass the server hard cap.

Live director behavior

Room caps are attached to the live director claiming the room. If the director is not present, that director's live cap is not present either.

If a director claims or reclaims the room, pending guests are re-evaluated using the director's current cap and approval settings.

Combining with approval

&roomcap can be combined with &requireapproval:

This makes guests wait for approval and also prevents the room from admitting more than the cap allows.

Not the same as source connection limits

&roomcap limits admission to a claimed room. It is not the same as &maxconnections, which limits peer connections to a single source/push stream.

&requireapproval&roomkey

Last updated

Was this helpful?