Welcome to Super-Shiritori!
Please remember:
- No vandalism – Do not add nonsense, false info, spam, or blank pages.
- Respect others – Be polite and assume good faith.
- Use reliable information – Make sure edits are accurate and IMPORTANT.
- Stay constructive – Help us grow the wiki with content, especially with the Word compendium.
⚠️ Repeated vandalism or rule-breaking may result in warnings or blocks. If you see vandalism, please revert it and notify an admin.
Created page with " == 🟢 Multiplayer Shiritori == '''Challenge friends, summon wild AIs, and build the longest chain of words you can—one letter at a time.''' === 🔓 Getting Started === To launch a game in any text channel: * A '''server Admin or Moderator''' (with the ''Manage Messages'' permission) must use: `/startshiritori [#channel]` * The bot will post the rules and automatically generate the '''starting word'''. * Only '''one active game''' is allowed per channel at a time...." |
No edit summary |
||
| (9 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= Multiplayer Shiritori = | |||
Multiplayer Shiritori is the bot's primary game mode, played in a shared text channel where players take turns extending a word chain. | |||
== | == Starting a Game == | ||
A server member with the Manage Messages permission, or the bot owner, can start a game with <code>/start_shiritori [#channel]</code>. The bot posts the rules and generates a random starting word automatically. Only one game may be active per channel at a time. | |||
To prevent abuse, a server is temporarily blocked from starting new games if <code>/start_shiritori</code> is used 5 times and <code>/end_shiritori</code> is used at least 4 times within a rolling 15-minute window. The resulting block lasts 2 hours. | |||
A multiplayer Shiritori game and a [[Protori]] game cannot both run in the same channel at once; starting one is rejected if the other is already active there, and this restriction also applies to a game's automatic restart, not just to the initial start command. | |||
If the bot restarts or goes offline while games are active, <code>/restore_games</code> brings them back. Restoration restores a channel's saved game state unconditionally rather than requiring the channel itself to be successfully re-resolved first — resolving the channel is only needed for the non-critical "welcome back" announcement and to restart [[#Timed Shiritori|Timed Shiritori]]'s countdown, so a temporary hiccup reaching Discord's API can no longer cost a game its progress the way it once could. | |||
''History:'' <code>/start_shiritori</code> and <code>/restore_games</code> could previously fail outright with a generic Discord "Unknown interaction" error if the command's own background work (acquiring a channel lock, or reading back saved game data) happened to take longer than Discord's 3-second initial-response window. Both commands now acknowledge the interaction immediately and send their actual response afterward, removing the crash. | |||
- | == Timed Shiritori == | ||
Timed Shiritori (referred to internally as Timer Mode) is an opt-in setting available when starting a game with <code>/start_shiritori</code>. With it enabled, the game also ends if nobody plays a word before a countdown expires, in addition to the normal ways a game can end. The countdown shrinks over the course of a game, cycling from 10 seconds down to 5 seconds across 3,000 turns. | |||
<code>/leaderboard</code> includes a toggle to view Timed-Shiritori-only statistics separately from a server's overall multiplayer leaderboard. | |||
''History:'' shortly after launch, Timed Shiritori had a restart-loop bug — an inactive channel's countdown was being started both at game creation and again after every automatic restart, so the countdown could expire before anyone had played a single word, ending and immediately restarting the same game roughly every 10 seconds. The countdown now only ever starts from an actual word being played (by a human, the AI, or Sniper), so an idle game no longer restarts itself in a loop. | |||
== | == Leveling and Experience == | ||
Every word played in multiplayer Shiritori grants experience points toward the player's level, viewable with <code>/level</code> or <code>!level</code> and ranked server-wide with <code>/levels_leaderboard</code>. On the bot's home server specifically, boosting that server grants a 1.8× experience multiplier; boosting a ''different'' server the bot is also present in grants a smaller 1.2× multiplier instead. | |||
''History:'' the function that grants experience used to save the updated data to disk synchronously, directly on the bot's single shared event loop, every single time any word was played in any Shiritori game across every server — the single most frequently hit blocking operation in the bot at the time it was found, since it's on the game's core, most-used path. That save now happens on a background thread instead, so granting experience for one word no longer stalls every other concurrent game while it writes to disk. | |||
== Rules == | |||
# The next word must begin with the final letter of the previous word. | |||
# Repeating a previously used word ends the game immediately. | |||
# Playing twice in a row is not allowed; another player must take a turn before the same player can play again. | |||
# Submitted words are checked against the bot's dictionary. <code>/check</code> can confirm whether a word is valid before it is played. | |||
According to the bot's own in-game rules message for this mode, allowed word types are English words, hyphenated compounds, acronyms, and common names. Unique proper nouns and words containing numbers or symbols other than the hyphen and apostrophe are not allowed. The dictionary also contains words related to political topics, sexual orientation, and internet subculture slang; players are responsible for the words they choose to play within their own server's rules. | |||
== Milestones and Special Messages == | |||
Every 100 turns, the bot posts "Congrats we at turn {number} 🎉", with the actual turn count filled in (for example, at turn 100, turn 200, and so on). | |||
Beyond that recurring announcement, seven specific individual turn numbers each carry their own one-off flavor message. These fall into two distinct categories: most of them react to ''whatever'' word is played on that turn, with a special variant only if the word happens to also match the milestone's theme; two of them (67 and 404) are silent unless the exact matching word is played, so most players never see them fire at all. | |||
=== | === Turn 42 === | ||
A reference to ''The Hitchhiker's Guide to the Galaxy''. Any word played on turn 42 triggers a message: playing "forty-two" or "four-two" gets "'''42.''' The Answer to Life, the Universe, and Everything," while any other word gets the plainer "Don't panic." | |||
=== Turn 67 === | |||
A reference to the "6 7" internet meme. Unlike the other milestones, this one is entirely silent unless the word played on turn 67 is specifically "six-seven" or "sixty-seven" — any other word at turn 67 produces no special message at all. When it does trigger, the bot fetches a random GIF from an external service (Klipy) matching "67 meme"; if that service isn't configured or the request fails for any reason, it falls back to a plain text reaction instead of a GIF. | |||
=== Turn 69 === | |||
Any word played on turn 69 triggers a message: "sixty-nine" specifically gets "I was thinking that too 😏," while any other word gets "Nice 😏." | |||
=== Turn 404 === | |||
A reference to the HTTP "404 Not Found" error code. Like turn 67, this one is silent unless the word played is specifically "four-o-four." When it triggers, it's a purely theatrical joke: the bot posts a fake system-crash message claiming an "unhandled exception" and an automatic restart, waits three seconds, then posts "'''jk.''' Carry on." Nothing about the actual game or word history is touched during those three seconds — the word was already committed normally before the joke plays out. | |||
=== Turn 420 === | |||
Any word played on turn 420 triggers a message: playing "weed," "four-twenty," "baked," "blazed," "lit," "high," or "stoned" gets "You got some 🌿?", while any other word gets "Live in the moment. 🌿" | |||
=== Turn 666 === | |||
Any word played on turn 666 triggers a message: playing "six-six-six" or "six-hundred-sixty-six" gets "You tried to summon it, but the ritual failed," styled with a pentagram symbol, while any other word gets the shorter "Something's watching." | |||
=== Turn 777 === | |||
A casino-jackpot reference. Any word played on turn 777 triggers a message: playing "seven-seven-seven," "seven-hundred-seventy-seven," "triple-seven," "jackpot," or "lucky" gets "'''JACKPOT!!!'''" styled with slot-machine emoji, while any other word gets "feeling lucky? 🍀" | |||
== AI Opponents == | |||
An AI opponent can be added with <code>/invite_ai</code>, or a specific personality can be summoned using a text command such as <code>!noob</code> or <code>!assassin</code>. An AI opponent is automatically removed after a period of inactivity. Personality behavior, summon success rates, and cooldowns are documented on [[AI Bots]]. | |||
== Community Role Rewards == | |||
On the bot's official support server, [https://discord.gg/WahVXSkA7H Shiritori Central], reaching certain turn milestones in a multiplayer game triggers an automatic role award. When the milestone is reached, the bot awards the role to every one of the last up to 50 unique players who contributed a word to that game (AI and Sniper turns do not count). | |||
{| class="wikitable" | |||
! Turn !! Role !! Message on success | |||
|- | |||
| 500 || 🔥5-Hundred Club🔥 || "Congrats {member}! You've been awarded a role for recent Shiritori activity 🎉" | |||
|- | |||
| 1000 || 💯1k Gang💯 || "Congrats {member}! You've been awarded a pretty rare role for the first Shiritori milestones 🎉" | |||
|} | |||
Any qualifying player who already holds the role is skipped with a message noting that recent activity was detected but the role was already held, rather than being granted it again. This mechanic is specific to Shiritori Central and does not occur on other servers running the bot. | |||
''History:'' the draw originally only considered players who were already visible in the server's cached member list at the moment the milestone was hit, silently excluding anyone playing from another server or simply not yet cached — with no record that they'd ever been in the running, and no way to recover the missed reward afterward. The draw was then changed to pick from the full candidate pool regardless of whether a player is currently resolvable, with an unresolvable pick logged durably and granted automatically the moment they're later seen as a member of the server, rather than being lost. | |||
It was still, at that point, a single random winner drawn from that pool despite up to 50 players qualifying each time — a mismatch caught from a direct report that only one person was ever receiving the reward. It now awards every qualifying player rather than picking just one, with the same per-player resolution and durable-queue handling described above applied individually to each of them, paced with a short delay between grants so a milestone with many qualifying players doesn't fire a burst of Discord API calls all at once. | |||
== Ending a Game == | |||
A game ends immediately if a repeated word is played, or if it is manually ended with <code>/end_shiritori</code>. Ending a game displays a summary of the match's statistics. Unless the game was ended by an admin, a new game starts automatically in the same channel after a 2-minute cooldown. | |||
''History:'' <code>/end_shiritori</code> shared the same "Unknown interaction" crash risk described above under [[#Starting a Game|Starting a Game]], since ending a game also does real background work (releasing the channel lock and compiling the closing statistics) before responding. It received the same immediate-acknowledgment fix. | |||
== Etiquette == | |||
There is no anti-cheat system, and consulting outside references is not blocked, though relying on one's own vocabulary is considered part of the spirit of the game. <code>!status</code> displays the current game's progress, including words played, average word length, and the next required letter. Players should use discretion with obscure or explicit words in line with their server's own rules. | |||
== See also == | |||
* [[Super-Shiritori]] | |||
* [[AI Bots]] | |||
* [[Solo Shiritori]] | |||
* [[Protori]] | |||
* [[Manual-Tori]] | |||
* [[Achievements]] | |||
[[Category:Information]] | |||
[[Category:Games(bot)]] | |||
Latest revision as of 01:57, 24 August 2026
Multiplayer Shiritori
Multiplayer Shiritori is the bot's primary game mode, played in a shared text channel where players take turns extending a word chain.
Starting a Game
A server member with the Manage Messages permission, or the bot owner, can start a game with /start_shiritori [#channel]. The bot posts the rules and generates a random starting word automatically. Only one game may be active per channel at a time.
To prevent abuse, a server is temporarily blocked from starting new games if /start_shiritori is used 5 times and /end_shiritori is used at least 4 times within a rolling 15-minute window. The resulting block lasts 2 hours.
A multiplayer Shiritori game and a Protori game cannot both run in the same channel at once; starting one is rejected if the other is already active there, and this restriction also applies to a game's automatic restart, not just to the initial start command.
If the bot restarts or goes offline while games are active, /restore_games brings them back. Restoration restores a channel's saved game state unconditionally rather than requiring the channel itself to be successfully re-resolved first — resolving the channel is only needed for the non-critical "welcome back" announcement and to restart Timed Shiritori's countdown, so a temporary hiccup reaching Discord's API can no longer cost a game its progress the way it once could.
History: /start_shiritori and /restore_games could previously fail outright with a generic Discord "Unknown interaction" error if the command's own background work (acquiring a channel lock, or reading back saved game data) happened to take longer than Discord's 3-second initial-response window. Both commands now acknowledge the interaction immediately and send their actual response afterward, removing the crash.
Timed Shiritori
Timed Shiritori (referred to internally as Timer Mode) is an opt-in setting available when starting a game with /start_shiritori. With it enabled, the game also ends if nobody plays a word before a countdown expires, in addition to the normal ways a game can end. The countdown shrinks over the course of a game, cycling from 10 seconds down to 5 seconds across 3,000 turns.
/leaderboard includes a toggle to view Timed-Shiritori-only statistics separately from a server's overall multiplayer leaderboard.
History: shortly after launch, Timed Shiritori had a restart-loop bug — an inactive channel's countdown was being started both at game creation and again after every automatic restart, so the countdown could expire before anyone had played a single word, ending and immediately restarting the same game roughly every 10 seconds. The countdown now only ever starts from an actual word being played (by a human, the AI, or Sniper), so an idle game no longer restarts itself in a loop.
Leveling and Experience
Every word played in multiplayer Shiritori grants experience points toward the player's level, viewable with /level or !level and ranked server-wide with /levels_leaderboard. On the bot's home server specifically, boosting that server grants a 1.8× experience multiplier; boosting a different server the bot is also present in grants a smaller 1.2× multiplier instead.
History: the function that grants experience used to save the updated data to disk synchronously, directly on the bot's single shared event loop, every single time any word was played in any Shiritori game across every server — the single most frequently hit blocking operation in the bot at the time it was found, since it's on the game's core, most-used path. That save now happens on a background thread instead, so granting experience for one word no longer stalls every other concurrent game while it writes to disk.
Rules
- The next word must begin with the final letter of the previous word.
- Repeating a previously used word ends the game immediately.
- Playing twice in a row is not allowed; another player must take a turn before the same player can play again.
- Submitted words are checked against the bot's dictionary.
/checkcan confirm whether a word is valid before it is played.
According to the bot's own in-game rules message for this mode, allowed word types are English words, hyphenated compounds, acronyms, and common names. Unique proper nouns and words containing numbers or symbols other than the hyphen and apostrophe are not allowed. The dictionary also contains words related to political topics, sexual orientation, and internet subculture slang; players are responsible for the words they choose to play within their own server's rules.
Milestones and Special Messages
Every 100 turns, the bot posts "Congrats we at turn {number} 🎉", with the actual turn count filled in (for example, at turn 100, turn 200, and so on).
Beyond that recurring announcement, seven specific individual turn numbers each carry their own one-off flavor message. These fall into two distinct categories: most of them react to whatever word is played on that turn, with a special variant only if the word happens to also match the milestone's theme; two of them (67 and 404) are silent unless the exact matching word is played, so most players never see them fire at all.
Turn 42
A reference to The Hitchhiker's Guide to the Galaxy. Any word played on turn 42 triggers a message: playing "forty-two" or "four-two" gets "42. The Answer to Life, the Universe, and Everything," while any other word gets the plainer "Don't panic."
Turn 67
A reference to the "6 7" internet meme. Unlike the other milestones, this one is entirely silent unless the word played on turn 67 is specifically "six-seven" or "sixty-seven" — any other word at turn 67 produces no special message at all. When it does trigger, the bot fetches a random GIF from an external service (Klipy) matching "67 meme"; if that service isn't configured or the request fails for any reason, it falls back to a plain text reaction instead of a GIF.
Turn 69
Any word played on turn 69 triggers a message: "sixty-nine" specifically gets "I was thinking that too 😏," while any other word gets "Nice 😏."
Turn 404
A reference to the HTTP "404 Not Found" error code. Like turn 67, this one is silent unless the word played is specifically "four-o-four." When it triggers, it's a purely theatrical joke: the bot posts a fake system-crash message claiming an "unhandled exception" and an automatic restart, waits three seconds, then posts "jk. Carry on." Nothing about the actual game or word history is touched during those three seconds — the word was already committed normally before the joke plays out.
Turn 420
Any word played on turn 420 triggers a message: playing "weed," "four-twenty," "baked," "blazed," "lit," "high," or "stoned" gets "You got some 🌿?", while any other word gets "Live in the moment. 🌿"
Turn 666
Any word played on turn 666 triggers a message: playing "six-six-six" or "six-hundred-sixty-six" gets "You tried to summon it, but the ritual failed," styled with a pentagram symbol, while any other word gets the shorter "Something's watching."
Turn 777
A casino-jackpot reference. Any word played on turn 777 triggers a message: playing "seven-seven-seven," "seven-hundred-seventy-seven," "triple-seven," "jackpot," or "lucky" gets "JACKPOT!!!" styled with slot-machine emoji, while any other word gets "feeling lucky? 🍀"
AI Opponents
An AI opponent can be added with /invite_ai, or a specific personality can be summoned using a text command such as !noob or !assassin. An AI opponent is automatically removed after a period of inactivity. Personality behavior, summon success rates, and cooldowns are documented on AI Bots.
Community Role Rewards
On the bot's official support server, Shiritori Central, reaching certain turn milestones in a multiplayer game triggers an automatic role award. When the milestone is reached, the bot awards the role to every one of the last up to 50 unique players who contributed a word to that game (AI and Sniper turns do not count).
| Turn | Role | Message on success |
|---|---|---|
| 500 | 🔥5-Hundred Club🔥 | "Congrats {member}! You've been awarded a role for recent Shiritori activity 🎉" |
| 1000 | 💯1k Gang💯 | "Congrats {member}! You've been awarded a pretty rare role for the first Shiritori milestones 🎉" |
Any qualifying player who already holds the role is skipped with a message noting that recent activity was detected but the role was already held, rather than being granted it again. This mechanic is specific to Shiritori Central and does not occur on other servers running the bot.
History: the draw originally only considered players who were already visible in the server's cached member list at the moment the milestone was hit, silently excluding anyone playing from another server or simply not yet cached — with no record that they'd ever been in the running, and no way to recover the missed reward afterward. The draw was then changed to pick from the full candidate pool regardless of whether a player is currently resolvable, with an unresolvable pick logged durably and granted automatically the moment they're later seen as a member of the server, rather than being lost.
It was still, at that point, a single random winner drawn from that pool despite up to 50 players qualifying each time — a mismatch caught from a direct report that only one person was ever receiving the reward. It now awards every qualifying player rather than picking just one, with the same per-player resolution and durable-queue handling described above applied individually to each of them, paced with a short delay between grants so a milestone with many qualifying players doesn't fire a burst of Discord API calls all at once.
Ending a Game
A game ends immediately if a repeated word is played, or if it is manually ended with /end_shiritori. Ending a game displays a summary of the match's statistics. Unless the game was ended by an admin, a new game starts automatically in the same channel after a 2-minute cooldown.
History: /end_shiritori shared the same "Unknown interaction" crash risk described above under Starting a Game, since ending a game also does real background work (releasing the channel lock and compiling the closing statistics) before responding. It received the same immediate-acknowledgment fix.
Etiquette
There is no anti-cheat system, and consulting outside references is not blocked, though relying on one's own vocabulary is considered part of the spirit of the game. !status displays the current game's progress, including words played, average word length, and the next required letter. Players should use discretion with obscure or explicit words in line with their server's own rules.