What works over a bridge
Every Hijinks game and team feature runs through the same commands on every chat, so a bridged chat gets them all. A few work differently because a bridge has no forms, no App Home and no member directory. This table says where, checked against the code, not the marketing.
What the reference bridge handles is marked in the last column; a bridge you write yourself needs the same pieces.
| Feature | Over a bridge | How it reaches your chat | What the bridge needs |
|---|---|---|---|
Live trivia (/hijinks start, true or false, rebus, charades) | Yes | One message per game, created and then redrawn: start card, each question with answer buttons, answer count, reveal, final board. Rebus and charades answers are typed. | Create and edit messages; buttons; replies only one member sees (the verdict after a press). Typed answers for rebus and charades. |
| Gotcha rounds | Yes | /hijinks gotcha; decoys are planted with /hijinks bait <text>, and the round arrives as two more redraws of the game's message. | Same as live trivia. Whether others see the bait command depends on how your chat shows slash commands (Mattermost does not). |
| Daily question | Yes | A one-question scheduled game: /hijinks schedule daily <hour>. | Same as live trivia. |
| Scheduled games | Yes | Created with /hijinks schedule daily or schedule weekly; listed with pause and delete buttons. Hijinks posts them at the time set, with no member action. | Nothing extra: a scheduled post is an ordinary message.create. |
| Async quiz | Yes | /hijinks async 48h posts an announcement with a Start button; each player gets the questions one by one in a direct message with answer buttons. Results post to the channel at the deadline. | Direct messages (dm.create) and button presses in them. |
| Word games (anagram, wordle, hangman; Team plan) | Yes | Started by command; the board is redrawn after each guess. Guesses are typed in the channel, or sent as a command (/hijinks answer, guess or letter). | For bare typed guesses, every message in the game channel is forwarded (see What a bridge sends us). Without that, guesses go through the commands only. |
| Pictionary | Yes | A drawing-room link; drawing and guessing happen in the browser, and the podium posts back to the channel. | Show a link button (the reference bridge prints it as a Markdown link). |
| Know Your Team | Partly | Turned on with /hijinks kyt on or in the dashboard. The daily reveal and the guess buttons work as everywhere. | Answering differs: Slack opens a form and Telegram asks in a private chat, but a bridged chat shows each question's key and members type /hijinks kyt answer <key> <text>. Typed in the channel, an answer is visible to others; typed in a direct message with the bot, it is not. |
| Celebrations (birthdays, work anniversaries) | Partly | Turned on with /hijinks celebrations on or in the dashboard; posts on the day. | Dates can only be set by each member typing /hijinks celebrations birthday MM-DD or anniversary YYYY-MM-DD. No form, no import, and an admin cannot enter dates for others. Members who never set one are not celebrated. |
| Coffee pairing | Yes | /hijinks coffee on; introductions go out as direct messages, with an opt-out switch. | Direct messages. Only members Hijinks has seen (below) are paired. |
| Icebreakers / small talk | Yes | /hijinks smalltalk on; a question with vote buttons, tally redrawn in place. | Buttons and message edits. |
| Weekly digest | Yes | Posted to each channel that played that week. | Nothing extra. |
| Leaderboard, categories, language, mute, preferences | Yes | Commands and button panels. The preferences panel is a reply only the member sees, redrawn when they flip a switch. | Editing a reply only one member sees, or the panel will not redraw. |
Who Hijinks knows about
A bridge sends no member directory and no "joined the channel" events. Hijinks learns a member the first time they run a command, answer a game question, answer Know Your Team or set a celebration date. Coffee pairing, Know Your Team's guess options and the digest's names draw on those members only. A typed message that is not an answer does not add anyone.
Who can stop games and change settings
Stopping a game, creating or removing schedules, and changing the language or a channel's settings take an admin. On Slack and Discord the chat says who manages it; a bridge cannot. The person who connected the workspace is its owner in the dashboard, but has no chat identity yet. To let chat members control games, make them admins on the dashboard's Members page once they appear there (after their first command). Playing, answering and reading standings are open to everyone.
Your chat cannot be reached from the internet?
The bridge can poll for events instead of receiving them, so Hijinks never needs an inbound address. Every feature above works the same in either mode.