Super Shiritori Wiki - User contributions [en]

MediaWiki:Cosmos.css

2026-09-05T08:20:50Z

The CodeGhost: Fix two real SocialProfile layout bugs: undefined .visualClear utility class (squished Personal information/Real name), and eye-container privacy pill overlapping field labels

/* ==========================================================================
SocialProfile dark-theme fixes
--------------------------------------------------------------------------
SocialProfile's bundled CSS (UserProfile.css, ProfileTabs.css,
SpecialUpdateProfile.css) was written for a white-background wiki: it sets
dark-gray text with NO background of its own (relying on the page being
white) and hardcodes a green/orange brand palette from Wikia's old look.
On this wiki's dark #401901 page background that produces near-invisible
text and off-brand green tabs/buttons. This overrides just those rules --
layout/spacing from the original files is untouched.
========================================================================== */

/* --- Profile tabs (View profile / Edit profile bar) --- */
.profile-tab {
background-color: rgba(241, 144, 0, 0.12);
border: 1px solid #F19000;
}

.profile-tab-on {
background-color: #F19000;
border: 1px solid #F19000;
}

.profile-tab a {
color: #F19000 !important;
}

.profile-tab a:hover {
color: #ffffff !important;
}

.profile-tab-on a,
.profile-tab-on a:visited {
color: #2a0f00 !important;
}

/* --- Save/update button on Special:UpdateProfile --- */
.profile-update-button {
background-color: #F19000;
border: 1px solid #F19000;
color: #2a0f00;
font-weight: 700;
}

/* --- Section headings that relied on a white page background --- */
#user-page-left h2,
#user-page-right h2,
.profile-update-title {
color: #F19000;
border-bottom-color: rgba(255, 255, 255, 0.2);
}

/* --- Body text that relied on a white page background --- */
.item-small,
.item,
.vote-text,
.profile-update-unit-left,
.profile-update-unit-small,
.profile-update-row,
.profile-board-message-type,
table.avatar-success-page td.title-cell,
.user-board-message-time,
.profile-info-container b,
.profile-info-container div {
color: #D5D4D4;
}

/* --- Cards that set their own pale/white background (looked like leftover
white boxes on the dark page) -- keep them as cards, just re-themed --- */
.no-info-container,
.no-pictures-container,
.user-board-message-from {
background-color: rgba(255, 255, 255, 0.06);
color: #D5D4D4;
}

/* --- Dividers that were near-invisible pale-gray-on-dark-brown --- */
#user-page-left h2,
#user-page-right h2,
.user-section-heading,
#profile-top,
.user-board-message,
.activity-item,
.casual-game-container p,
.article-item {
border-color: rgba(255, 255, 255, 0.15);
}

/* --- "Add points"-style badge on the toggle button: brand orange stays,
just make sure the text stays legible --- */
#profile-toggle-button {
background-color: #F19000;
}

#profile-toggle-button a {
color: #2a0f00 !important;
}

/* ==========================================================================
Mobile / tablet fixes
--------------------------------------------------------------------------
Reported by a wiki editor via Discord: on a tablet, the notifications
(bell/envelope) flyout "takes up nearly half my screen". Root cause: Echo's
popup has no max-height or scroll of its own -- it just grows one row per
notification forever. Capping it and giving the list its own scrollbar
fixes that regardless of how many notifications pile up.
========================================================================== */
/* !important is required here: OOUI's JS computes its own clipping and sets
max-height as an INLINE style on this element, which otherwise beats any
plain rule in an external stylesheet regardless of selector specificity. */
.mw-echo-ui-notificationBadgeButtonPopupWidget-popup .oo-ui-popupWidget-body {
max-height: 60vh !important;
overflow-y: auto !important;
}

@media screen and (max-width: 900px) {
.mw-echo-ui-notificationBadgeButtonPopupWidget-popup .oo-ui-popupWidget-body {
max-height: 45vh !important;
}

.mw-echo-ui-notificationBadgeButtonPopupWidget-popup .oo-ui-popupWidget-popup {
max-width: 92vw;
}
}

/* ==========================================================================
Top-nav mega-menu + page-actions "..." menu (legacy Wikia "WDS" markup)
--------------------------------------------------------------------------
Cosmos ports this component straight from old Wikia CSS with its own
light-theme colors baked in -- it was never re-themed, so every dropdown
off the top nav renders as a plain white box with black text. This is most
visible on mobile, where the hamburger button just toggles this same
element to display:block (reported by a wiki editor: the menu "takes up
nearly half my screen" and looks broken), but it's equally wrong on
desktop. Colors match what the rest of the site already uses.
========================================================================== */
/* Selectors are doubled-up (.foo.foo) purely to raise specificity -- Cosmos's
own CSS fights back here with both a 2-class selector (.cosmos-header
.wds-dropdown__content) on desktop AND a 2-class !important rule forcing
background-color: transparent on mobile, so a plain single-class rule
(even with !important) loses to both. */
.wds-dropdown__content.wds-dropdown__content,
.wds-dropdown-level-2__content.wds-dropdown-level-2__content {
background-color: #2a0f00 !important;
border: 1px solid rgba(255, 255, 255, 0.15) !important;
box-shadow: 0 4px 12px rgba(0, 0, 0, 0.4);
}

.wds-dropdown__content li,
.wds-dropdown-level-2__content li {
color: #D5D4D4;
border-color: rgba(255, 255, 255, 0.1);
}

.wds-dropdown__content a,
.wds-dropdown-level-2__content a,
.wds-dropdown-level-2__toggle {
color: #F27AEE !important;
}

.wds-dropdown__content a:hover,
.wds-dropdown-level-2__content a:hover,
.wds-dropdown-level-2__toggle:hover {
color: #F19000 !important;
}

.wds-dropdown-level-2__toggle .wds-dropdown-chevron {
fill: #F27AEE;
}

.wds-dropdown-level-2__toggle:hover .wds-dropdown-chevron {
fill: #F19000;
}

/* On mobile the hamburger button toggles the whole .wds-tabs bar to
display:block; without an explicit background it would otherwise rely on
.wds-dropdown__content alone for color, so give the outer bar a matching
dark backing and keep it from ever exceeding the viewport height. */
@media screen and (max-width: 1023px) {
.wds-tabs {
background-color: #1a0a00;
max-height: 80vh;
overflow-y: auto;
}
}

/* ==========================================================================
Site notice (the dismissible "Welcome to Super-Shiritori!" rules banner)
--------------------------------------------------------------------------
Cosmos reuses its BUTTON theme colors for this box (@button-background-color
/ @button-font-color) -- on this wiki that resolves to solid brand-orange
with bold white text, which is exactly what the "EDIT SOURCE" button looks
like, so a rules notice ends up camouflaged as UI chrome instead of reading
as a notice, and white-on-orange is borderline low-contrast besides.
Restyled as a proper notice card: dark body, orange accent border --
consistent with every other box on the site.
========================================================================== */
#cosmos-content-siteNotice {
background-color: #2a0f00;
border: 1px solid rgba(255, 255, 255, 0.15);
border-left: 4px solid #F19000;
color: #D5D4D4;
}

#cosmos-content-siteNotice * {
color: #D5D4D4;
}

#cosmos-content-siteNotice b,
#cosmos-content-siteNotice strong {
color: #F19000;
}

#cosmos-siteNotice-closeButton svg,
#cosmos-siteNotice-closeButton path {
fill: #D5D4D4;
}

#cosmos-siteNotice-closeButton:hover svg,
#cosmos-siteNotice-closeButton:hover path {
fill: #F19000;
}

/* ==========================================================================
Social profile layout fixes
--------------------------------------------------------------------------
Two separate real bugs on the user-profile / edit-profile pages.
========================================================================== */

/* 1. ".visualClear" is used throughout SocialProfile's markup to clear floats
(e.g. after a floated section heading, before the section's actual
content) -- but it's a bare Fandom/Wikia platform utility class that was
never actually DEFINED anywhere: not in SocialProfile's own CSS, not in
MediaWiki core, not in Cosmos. With no "clear" rule attached, the class
does nothing, so floated headings (like "Personal information") never get
cleared and the next line's content (the "Real name" label/value) rises up
and squishes into the same line as the heading instead of sitting below
it. This one rule fixes every place that pattern shows up. */
.visualClear {
clear: both;
}

/* 2. The privacy "Public"/"Friends"/"Hidden" toggle pill on Special:UpdateProfile
is pulled up with fragile hardcoded negative offsets (top: -25px, tuned
per-field) meant to tuck it next to Fandom's original field-label spacing.
Cosmos's typography doesn't match those old measurements, so the pill
lands on top of the label text instead (e.g. "Email" + the pill overlap
into an unreadable "Emailublic"). Letting it sit in normal document flow
below the field, instead of being pulled back up over it, can't overlap
regardless of exact spacing. */
div.eye-container[fieldkey] {
position: static !important;
top: auto !important;
margin: 4px 0 10px 0;
}

MediaWiki:Cosmos.css

2026-09-05T08:07:17Z

The CodeGhost: Restyle the site notice banner: dark card with orange accent border instead of solid brand-orange (was borderline low-contrast and camouflaged as a button)

MediaWiki:Common.js

2026-09-05T05:25:47Z

The CodeGhost: Fix: use event delegation for gallery tab clicks -- direct listeners were being silently dropped, likely by MultimediaViewer touching the parser output after load

/* Behavior for Template:Infobox_application. Lives in Common.js (not
* Cosmos.js) so it keeps working regardless of which skin a reader/editor
* has selected. */
( function () {

// Clickable tab bar for multi-image infoboxes (image1/caption1,
// image2/caption2, ...). Delegated on document instead of bound directly
// to each tab: something else on the page (MultimediaViewer's own image
// handling is the prime suspect) touches the parser output shortly after
// load and silently drops direct listeners, so binding to a stable
// ancestor that's never replaced is what actually keeps working.
function handleGalleryClick( e ) {
var tab = e.target.closest( '.infobox-application__gallery-tab' );
if ( !tab ) {
return;
}
var gallery = tab.closest( '.infobox-application__gallery' );
if ( !gallery ) {
return;
}
var index = tab.getAttribute( 'data-ia-tab' );
gallery.querySelectorAll( '.infobox-application__gallery-tab' ).forEach( function ( t ) {
t.classList.toggle( 'is-active', t === tab );
} );
gallery.querySelectorAll( '.infobox-application__gallery-slide' ).forEach( function ( slide ) {
// A plain "hidden" attribute gets stripped by MediaWiki's
// sanitizer, so a CSS class carries visibility instead.
slide.classList.toggle( 'is-inactive', slide.getAttribute( 'data-ia-slide' ) !== index );
} );
}

// On narrow screens the infobox drops its desktop float (see
// Template:Infobox_application/styles.css) and becomes a full-width
// block -- but it's still first in the wikitext/DOM, so without this it
// would render ABOVE the lead paragraph instead of below it, the way
// Wikipedia's mobile view places infoboxes. This moves it to just after
// the first non-empty paragraph of the article (mirrors MobileFrontend's
// own behavior, which Cosmos doesn't have).
function relocateInfoboxOnMobile() {
if ( window.innerWidth > 550 ) {
return;
}
document.querySelectorAll( '.mw-parser-output > .infobox-application' ).forEach( function ( box ) {
if ( box.dataset.iaRelocated ) {
return;
}
var sib = box.nextElementSibling;
while ( sib && ( sib.tagName !== 'P' || !sib.textContent.trim() ) ) {
sib = sib.nextElementSibling;
}
if ( sib ) {
sib.insertAdjacentElement( 'afterend', box );
box.dataset.iaRelocated = '1';
}
} );
}

// Registered immediately (doesn't need the DOM to be ready) and on a
// node that's never replaced, so this survives regardless of what else
// on the page rebuilds the content area after load.
document.addEventListener( 'click', handleGalleryClick );

function init() {
relocateInfoboxOnMobile();
}
if ( document.readyState === 'loading' ) {
document.addEventListener( 'DOMContentLoaded', init );
} else {
init();
}
// Belt-and-suspenders: re-run once everything (including images) has
// finished loading, in case something reflowed the lead section after
// DOMContentLoaded. The dataset guard above makes this a no-op otherwise.
window.addEventListener( 'load', relocateInfoboxOnMobile );
}() );

MediaWiki:Common.js

2026-09-05T05:21:33Z

The CodeGhost: Fix: toggle is-inactive class instead of .hidden property to match the sanitizer-safe markup

/* Behavior for Template:Infobox_application. Lives in Common.js (not
* Cosmos.js) so it keeps working regardless of which skin a reader/editor
* has selected. */
( function () {

// Clickable tab bar for multi-image infoboxes (image1/caption1,
// image2/caption2, ...). Without this, only the first <div data-ia-slide>
// is visible -- everything still renders, it just can't be switched.
function initInfoboxGalleries() {
document.querySelectorAll( '.infobox-application__gallery' ).forEach( function ( gallery ) {
var tabs = gallery.querySelectorAll( '.infobox-application__gallery-tab' );
var slides = gallery.querySelectorAll( '.infobox-application__gallery-slide' );
tabs.forEach( function ( tab ) {
tab.addEventListener( 'click', function () {
var index = tab.getAttribute( 'data-ia-tab' );
tabs.forEach( function ( t ) {
t.classList.toggle( 'is-active', t === tab );
} );
slides.forEach( function ( slide ) {
// A plain "hidden" attribute gets stripped by MediaWiki's
// sanitizer, so a CSS class carries visibility instead.
slide.classList.toggle( 'is-inactive', slide.getAttribute( 'data-ia-slide' ) !== index );
} );
} );
} );
} );
}

// On narrow screens the infobox drops its desktop float (see
// Template:Infobox_application/styles.css) and becomes a full-width
// block -- but it's still first in the wikitext/DOM, so without this it
// would render ABOVE the lead paragraph instead of below it, the way
// Wikipedia's mobile view places infoboxes. This moves it to just after
// the first non-empty paragraph of the article (mirrors MobileFrontend's
// own behavior, which Cosmos doesn't have).
function relocateInfoboxOnMobile() {
if ( window.innerWidth > 550 ) {
return;
}
document.querySelectorAll( '.mw-parser-output > .infobox-application' ).forEach( function ( box ) {
var sib = box.nextElementSibling;
while ( sib && ( sib.tagName !== 'P' || !sib.textContent.trim() ) ) {
sib = sib.nextElementSibling;
}
if ( sib ) {
sib.insertAdjacentElement( 'afterend', box );
}
} );
}

function init() {
initInfoboxGalleries();
relocateInfoboxOnMobile();
}

if ( document.readyState === 'loading' ) {
document.addEventListener( 'DOMContentLoaded', init );
} else {
init();
}
}() );

Template:Infobox application

2026-09-05T05:21:32Z

The CodeGhost: Fix: use a CSS class instead of the hidden attribute, which MediaWiki sanitizer strips from raw HTML

<includeonly><templatestyles src="Infobox application/styles.css"/><div class="infobox-application"{{#if:{{{color|}}}{{{bg|}}}| style="{{#if:{{{color|}}}|--ia-accent: {{{color}}};}}{{#if:{{{bg|}}}| --ia-bg: {{{bg}}};}}"}}>
<div class="infobox-application__title">{{{name|{{PAGENAME}}}}}</div>{{#if:{{{image2|}}}|
<div class="infobox-application__gallery">
<div class="infobox-application__gallery-tabs">
<div class="infobox-application__gallery-tab is-active" data-ia-tab="0">{{{caption1|Image 1}}}</div>{{#if:{{{image2|}}}|<div class="infobox-application__gallery-tab" data-ia-tab="1">{{{caption2|Image 2}}}</div>}}{{#if:{{{image3|}}}|<div class="infobox-application__gallery-tab" data-ia-tab="2">{{{caption3|Image 3}}}</div>}}{{#if:{{{image4|}}}|<div class="infobox-application__gallery-tab" data-ia-tab="3">{{{caption4|Image 4}}}</div>}}{{#if:{{{image5|}}}|<div class="infobox-application__gallery-tab" data-ia-tab="4">{{{caption5|Image 5}}}</div>}}{{#if:{{{image6|}}}|<div class="infobox-application__gallery-tab" data-ia-tab="5">{{{caption6|Image 6}}}</div>}}
</div>
<div class="infobox-application__gallery-slide" data-ia-slide="0">{{{image1|}}}{{#if:{{{caption1|}}}|<div class="infobox-application__gallery-caption">{{{caption1}}}</div>}}</div>{{#if:{{{image2|}}}|<div class="infobox-application__gallery-slide is-inactive" data-ia-slide="1">{{{image2}}}{{#if:{{{caption2|}}}|<div class="infobox-application__gallery-caption">{{{caption2}}}</div>}}</div>}}{{#if:{{{image3|}}}|<div class="infobox-application__gallery-slide is-inactive" data-ia-slide="2">{{{image3}}}{{#if:{{{caption3|}}}|<div class="infobox-application__gallery-caption">{{{caption3}}}</div>}}</div>}}{{#if:{{{image4|}}}|<div class="infobox-application__gallery-slide is-inactive" data-ia-slide="3">{{{image4}}}{{#if:{{{caption4|}}}|<div class="infobox-application__gallery-caption">{{{caption4}}}</div>}}</div>}}{{#if:{{{image5|}}}|<div class="infobox-application__gallery-slide is-inactive" data-ia-slide="4">{{{image5}}}{{#if:{{{caption5|}}}|<div class="infobox-application__gallery-caption">{{{caption5}}}</div>}}</div>}}{{#if:{{{image6|}}}|<div class="infobox-application__gallery-slide is-inactive" data-ia-slide="5">{{{image6}}}{{#if:{{{caption6|}}}|<div class="infobox-application__gallery-caption">{{{caption6}}}</div>}}</div>}}
</div>
|{{#if:{{{image|}}}|
<div class="infobox-application__image">{{{image}}}</div>}}{{#if:{{{caption|}}}|
<div class="infobox-application__caption">{{{caption}}}</div>}}}}{{#if:{{{type|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Type</div><div class="infobox-application__value">{{{type}}}</div></div>}}{{#if:{{{function|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Function</div><div class="infobox-application__value">{{{function}}}</div></div>}}{{#if:{{{aliases|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Aliases</div><div class="infobox-application__value">{{{aliases}}}</div></div>}}{{#if:{{{platform|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Platform</div><div class="infobox-application__value">{{{platform}}}</div></div>}}{{#if:{{{developer|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Developer</div><div class="infobox-application__value">{{{developer}}}</div></div>}}{{#if:{{{language|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Language</div><div class="infobox-application__value">{{{language}}}</div></div>}}{{#if:{{{status|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Status</div><div class="infobox-application__value">{{{status}}}</div></div>}}{{#if:{{{launched|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Launched</div><div class="infobox-application__value">{{{launched}}}</div></div>}}{{#if:{{{hosted|}}}|{{#if:{{{hosted_from|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Originally hosted</div><div class="infobox-application__value">{{{hosted_from}}}</div></div>
<div class="infobox-application__row"><div class="infobox-application__label">Currently hosted</div><div class="infobox-application__value">{{{hosted}}}</div></div>|
<div class="infobox-application__row"><div class="infobox-application__label">Hosted in</div><div class="infobox-application__value">{{{hosted}}}</div></div>}}}}{{#if:{{{access|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Access</div><div class="infobox-application__value">{{{access}}}</div></div>}}{{#if:{{{counterparts|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Related bots</div><div class="infobox-application__value">{{{counterparts}}}</div></div>}}
</div>{{#ifeq: {{NAMESPACENUMBER}} | 0 | [[Category:Applications]]}}</includeonly><noinclude>
== Description ==
A dark-themed infobox for the wiki's Discord bots/applications (Super-Shiritori, Word-Curatori, Vexitori). Replaces the old <code><nowiki>{{Character}}</nowiki></code> template, which was raw Fandom "Portable Infobox" markup (<code><nowiki><infobox type="Character"></nowiki></code>) left over from the Fandom migration -- that extension was never self-hostable, so it rendered as literal unparsed tags rather than an actual infobox, and its fields (Species, Gender, Portrayed by, Marital status...) were built for fictional characters, not bots.

== Syntax ==
<pre>
{{Infobox application
| name =
| color =
| bg =
| image = [[File:Example.png|250px]]
| caption =
| image1 =
| caption1 =
| image2 =
| caption2 =
| type = Discord Bot
| function =
| aliases =
| platform = Discord
| developer =
| language =
| status = Active
| launched =
| hosted_from =
| hosted =
| access =
| counterparts =
}}
</pre>

All fields are optional except <code>name</code> (which defaults to the page title). A blank/omitted field just doesn't render that row.

'''Single image:''' use <code>image</code> (full wikitext, e.g. <code><nowiki>[[File:Example.png|250px]]</nowiki></code>) and optionally <code>caption</code>.

'''Multiple images (clickable tab bar):''' once <code>image2</code> is set, the box switches to tabbed-gallery mode -- use <code>image1</code>/<code>caption1</code>, <code>image2</code>/<code>caption2</code>, up through <code>image6</code>/<code>caption6</code>. Each caption becomes a tab label; clicking a tab swaps the picture. See [[Super-Shiritori]] for a live 4-image example. (Requires JavaScript -- with it off, only the first image shows.)

'''Color scheme:''' <code>color</code> sets the accent color (tab bar, labels, header text -- default site orange <code>#F19000</code>); <code>bg</code> sets the card's background (default <code>#2a0f00</code>). Pick both to theme a box around its own images instead of the default orange/brown. Keep <code>bg</code> dark -- body text is a fixed light gray and won't stay readable on a light background.

<code>hosted</code> is always the '''current''' hosting location. Add <code>hosted_from</code> only if that location has changed since launch -- doing so splits the single "Hosted in" row into "Originally hosted" / "Currently hosted" instead. Leave <code>hosted_from</code> out for a bot that's never moved.

[[Category:Infobox templates]]
</noinclude>

Template:Infobox application/styles.css

2026-09-05T05:21:30Z

The CodeGhost: Fix: use a CSS class instead of the hidden attribute, which MediaWiki sanitizer strips from raw HTML

/* Colors come from --ia-accent / --ia-bg custom properties set inline by the
template (see Template:Infobox_application `color=` / `bg=` params) so each
page can theme its own infobox around its own images. The var() fallbacks
below are what you get if a page doesn't set them -- the original orange/
dark-brown look. */

.infobox-application {
float: right;
clear: right;
width: 300px;
margin: 0 0 1em 1em;
background-color: var(--ia-bg, #2a0f00);
border: 1px solid rgba(255, 255, 255, 0.15);
border-radius: 4px;
box-shadow: 0 4px 12px rgba(0, 0, 0, 0.4);
font-size: 88%;
line-height: 1.4;
}

.infobox-application__title {
background-color: #1a0a00;
color: var(--ia-accent, #F19000);
font-size: 120%;
font-weight: bold;
text-align: center;
padding: 8px;
border-bottom: 1px solid rgba(255, 255, 255, 0.15);
border-radius: 4px 4px 0 0;
}

.infobox-application__image {
text-align: center;
padding: 8px;
border-bottom: 1px solid rgba(255, 255, 255, 0.1);
}

.infobox-application__image img {
max-width: 100%;
}

.infobox-application__caption {
font-style: italic;
color: #D5D4D4;
font-size: 90%;
text-align: center;
padding: 4px 8px;
border-bottom: 1px solid rgba(255, 255, 255, 0.1);
}

.infobox-application__row {
display: flex;
padding: 4px 8px;
border-bottom: 1px solid rgba(255, 255, 255, 0.08);
}

.infobox-application__row:last-child {
border-bottom: none;
}

.infobox-application__label {
color: var(--ia-accent, #F19000);
font-weight: bold;
width: 40%;
flex-shrink: 0;
padding-right: 6px;
}

.infobox-application__value {
color: #D5D4D4;
width: 60%;
}

/* --- Multi-image tabbed gallery (image1/caption1, image2/caption2, ...) --- */
.infobox-application__gallery-tabs {
display: flex;
overflow-x: auto;
background-color: var(--ia-accent, #F19000);
}

.infobox-application__gallery-tab {
flex: 0 0 auto;
color: #1a0a00;
font-weight: bold;
font-size: 90%;
padding: 8px 10px;
cursor: pointer;
white-space: nowrap;
border-bottom: 3px solid transparent;
user-select: none;
}

.infobox-application__gallery-tab.is-active {
background-color: rgba(0, 0, 0, 0.2);
border-bottom-color: #1a0a00;
}

.infobox-application__gallery-tab:hover {
background-color: rgba(0, 0, 0, 0.12);
}

.infobox-application__gallery-slide {
text-align: center;
padding: 8px;
}

/* A plain "hidden" attribute gets stripped by MediaWiki's HTML sanitizer
(not on its allowlist for div), so visibility is tracked with this class
instead -- toggled by MediaWiki:Common.js. */
.infobox-application__gallery-slide.is-inactive {
display: none;
}

.infobox-application__gallery-slide img {
max-width: 100%;
}

.infobox-application__gallery-caption {
font-style: italic;
color: #D5D4D4;
font-size: 90%;
text-align: center;
padding: 0 8px 8px;
border-bottom: 1px solid rgba(255, 255, 255, 0.1);
}

/* Below this, a 300px fixed-width float leaves almost no room for the
article text beside it (down to a single-character-wide column on a
phone) -- drop the float and let the box take the full column width. */
@media screen and (max-width: 550px) {
.infobox-application {
float: none;
clear: both;
width: auto;
margin: 0 0 1em 0;
}
}

Super-Shiritori

2026-09-05T05:19:46Z

The CodeGhost: Switch the 4 profile pictures to the new clickable tab-bar gallery; fix Hosted in to reflect the move to Hawaii

{{Infobox application
| name = Super-Shiritori
| image1 = [[File:Super Shiritori Bot (Discord).png|250px]]
| caption1 = Main profile picture
| image2 = [[File:Super-Merritori.png|250px]]
| caption2 = Holiday profile picture
| image3 = [[File:Halloween Shiritori PFP.png|250px]]
| caption3 = Halloween profile picture
| image4 = [[File:Original Super-Shiritori PFP.webp|250px]]
| caption4 = Original profile picture
| aliases = Super Shiritori, Shiritori
| type = Discord Bot
| function = Flagship word-chain game bot
| platform = Discord
| status = Active
| launched = November 22, 2024
| hosted_from = Washington State, USA (via Discord)
| hosted = Hawaii, USA (via Discord)
| counterparts = [[Word-Curatori]] (originally called "Super Shiritori (Test Edition)")<br>[[Vexitori]]
}}

'''Super-Shiritori''' is the flagship Discord bot of the project, running a word-chain game in which players respond with a word beginning with the final letter of the previous word. Alongside its core game, it supports several related word-based modes, tracks detailed player statistics, and maintains the shared dictionary of over 1.6 million entries. It is one of [[Discord Bots|three separate bots]] that make up the project, running alongside [[Word-Curatori]] and [[Vexitori]].

== Features ==
* Multiplayer and solo word-chain gameplay, against other players or AI opponents with distinct personalities
* A dictionary exceeding 1.6 million entries, drawn from acronyms, user submissions, foreign-language borrowings, constructed languages, and established published dictionaries
* Additional game modes, including Word Bomb, Wordle, Anagram, and Protori
* A rarity-based word rolling and trading system
* Player statistics, leaderboards, and a leveling system with unlockable [[Achievements]] (formerly called titles)
* Deployable in any Discord server
* A small number of hidden text-trigger commands functioning as puzzle easter eggs

== Bot Commands ==

=== Multiplayer Shiritori ===
{| class="wikitable"
! Command !! Description
|-
| <code>/start_shiritori [#channel]</code> || Starts a multiplayer game in the specified channel. Requires the Manage Messages permission or bot owner status.
|-
| <code>/end_shiritori</code> || Manually ends the current game and displays final statistics.
|-
| <code>/invite_ai</code> || Invites an AI opponent with a randomly assigned personality into the current game.
|-
| <code>/murder_ai</code> || Attempts to remove the current AI opponent from the game.
|-
| <code>/leaderboard</code> || Displays the server's multiplayer leaderboard by category.
|-
| <code>/my_stats</code> || Displays the player's personal global multiplayer statistics.
|-
| <code>/levels_leaderboard</code> || Displays the server's level leaderboard.
|-
| <code>/level</code> || Displays the player's current level and experience progress.
|-
| <code>/restore_games</code> || Restores active games after a bot restart or shutdown.
|-
| <code>/global_stats</code> || Displays aggregated multiplayer statistics across all servers.
|}
''Main article:'' [[Multiplayer Shiritori]]

=== Protori ===
{| class="wikitable"
! Command !! Description
|-
| <code>/start_protori [#channel]</code> || Starts a Protori game in the specified channel. Requires the Manage Messages permission or bot owner/curator status.
|-
| <code>/end_protori</code> || Manually ends the current Protori game.
|-
| <code>/protori_stats</code> || Displays the player's Protori statistics, both globally and broken down per server.
|-
| <code>/protori_leaderboard</code> || Displays the Protori leaderboard, server or global.
|}
''Main article:'' [[Protori]]

=== Solo Shiritori ===
{| class="wikitable"
! Command !! Description
|-
| <code>/solo_shiritori</code> || Starts a private solo game against the AI in a dedicated thread.
|-
| <code>/solo_stats</code> || Displays the player's solo statistics.
|-
| <code>/solo_leaderboard</code> || Displays the global solo leaderboard.
|}
''Main article:'' [[Solo Shiritori]]

=== Wordle ===
{| class="wikitable"
! Command !! Description
|-
| <code>/wordle</code> || Starts a private Wordle game.
|-
| <code>/wordle_leaderboard</code> || Displays Wordle win streaks by word length and mode.
|-
| <code>/wordle_stats</code> || Displays the player's personal Wordle win streaks by mode.
|}
''Main article:'' [[Wordle]]

=== Word Bomb ===
{| class="wikitable"
! Command !! Description
|-
| <code>/wordbomb</code> || Starts a Word Bomb game.
|-
| <code>/wordbomb_leaderboard</code> || Displays the server's Word Bomb leaderboard.
|-
| <code>/wordbomb_stats</code> || Displays the player's personal Word Bomb statistics.
|}
''Main article:'' [[Wordbomb]]

=== Anagram ===
{| class="wikitable"
! Command !! Description
|-
| <code>/anagram</code> || Starts a private Anagram game.
|-
| <code>/anagram_stats</code> || Displays the player's personal Anagram statistics.
|-
| <code>/anagram_leaderboard</code> || Displays the server's Anagram leaderboard.
|}
''Main article:'' [[Anagram]]

=== Dictionary and Words ===
{| class="wikitable"
! Command !! Description
|-
| <code>/dictionaries</code> || Checks the player's progress against specific themed word lists.
|-
| <code>/check</code> || Checks whether one or more words are in the dictionary.
|-
| <code>/characters</code> || Displays the character count of the given word or words.
|-
| <code>/solve</code> || Searches for words matching a given prompt, length, or other criteria.
|-
| <code>/suggest</code> || Suggests a word for addition to the dictionary, or proposes removal of an existing entry.
|-
| <code>/define</code> || Returns an AI-generated definition of a word.
|-
| <code>/word_collection</code> || Displays a player's collected words.
|-
| <code>/random_word</code> || Returns a random word that has not yet been played.
|-
| <code>/wordhunt</code> || A recurring personal challenge, refreshing every 12 hours, that prompts the player to find dictionary words they have not yet used.
|}
''Main article:'' [[Dictionary Information]]

=== Casino and RNG ===
{| class="wikitable"
! Command !! Description
|-
| <code>/roll</code> || Rolls for a random word, weighted by rarity.
|-
| <code>/set_casino</code> || Sets or removes the channels where <code>/roll</code> may be used.
|-
| <code>/rng_draw</code> || Spins for a chance at rarer rewards.
|-
| <code>/rng_stats</code> || Displays the player's personal rolling statistics.
|-
| <code>/rng_global</code> || Displays global rolling statistics.
|-
| <code>/rng_set_luck</code> || Sets the player's luck multiplier for rolls.
|-
| <code>/word_trade</code> || Trades a word with another player.
|}

=== Achievements ===
{| class="wikitable"
! Command !! Description
|-
| <code>/achievements</code> || Displays the player's unlocked and obtainable achievements. Public/Private visibility choice.
|-
| <code>/set_achievement</code> || Sets or clears the player's displayed achievement from among those unlocked.
|}
''Main article:'' [[Achievements]]

=== Configuration and Utility ===
{| class="wikitable"
! Command !! Description
|-
| <code>/toggle_corrections</code> || Toggles whether invalid words are deleted and warned about, or only marked with a reaction. Requires the Manage Messages permission.
|-
| <code>/config_view</code> || Displays the server's configuration for AI event logging and word suggestion notifications.
|-
| <code>/server</code> || Returns an invite link to the official support server.
|-
| <code>/wiki</code> || Returns a link to this wiki.
|-
| <code>/curator_form</code> || Returns a link to the Word Curator application form.
|-
| <code>/help</code> || Displays a list of all commands.
|}

== Quick Chat Commands ==
{| class="wikitable"
! Command !! Description
|-
| <code>!i</code> || An expanded version of <code>/check</code> with more detail.
|-
| <code>!level</code> || Quick view of the player's level and experience progress.
|-
| <code>!achieve</code>, <code>!achievement</code>, <code>!achievements</code> || Opens the player's list of unlocked and obtainable achievements. All three aliases work identically.
|-
| <code>!check</code> || Curator only. Checks the status of pending word suggestions and removals.
|-
| <code>!status</code> || Displays the current game's status, including words played, average word length, and the next required letter.
|-
| <code>!longest</code> || Displays the top five longest words played in the current game.
|-
| <code>!rng <word></code> || Checks a word's rarity and global ownership.
|}
A small number of additional text-trigger commands exist as hidden puzzle easter eggs. Their exact triggers are not documented publicly here. Separately, a set of documented explainer commands — <code>!hyphens</code>, <code>!neoses</code>, <code>!aisource</code>, and their aliases — answer common questions about dictionary rules; see [[Dictionary Information]].

== AI Opponents ==
Multiplayer games may include an AI opponent, added either randomly through <code>/invite_ai</code> or by summoning a specific personality with a text command. Each of the 19 personalities follows its own word-selection logic — NOOB favors short, simple words, PRO requires words of at least twelve letters, MIMIC attempts to answer with an anagram of the player's own last word, and so on. Two further AI types, Sniper and Assassin, layer additional mechanics — one-shot dramatic word plays and a hijack-and-silence risk/reward exchange, respectively — on top of the base system.

''Main article:'' [[AI Bots]]

== Game Modes ==

=== Multiplayer Shiritori ===
The core game mode. Players take turns submitting words in a shared channel, each beginning with the final letter of the previous word. Repeated words, invalid characters, and words that do not follow the required letter all end a player's turn or the game, depending on server configuration.

''Main article:'' [[Multiplayer Shiritori]]

=== Protori ===
A scoring-based variant of multiplayer Shiritori. Rather than simply continuing the chain, every accepted word earns points from a flat per-letter point table, weighted by how rare each letter is in the dictionary rather than a standard Scrabble-style tile distribution; a word's base score is just the sum of its letters' values. Continuing more deeply into the previous word than just its final letter — matching several trailing characters in a row — earns a chain bonus of roughly 1% of the word's base score per matched character, up to about +79% for a very deep match. Playing a word that has already been used ends the game immediately and costs the player a 250-point penalty.

''Main article:'' [[Protori]]

=== Solo Shiritori ===
A private word-chain match played against an adaptive AI opponent in a dedicated thread. The AI begins as ROOKIE and its behavior shifts over time based on the player's performance and random chance.

''Main article:'' [[Solo Shiritori]]

=== Word Bomb ===
An elimination game for up to 16 players, each starting with three lives. On each turn, a player must submit a valid dictionary word containing an assigned prompt string before a timer runs out; failing to do so costs a life. Games started through <code>/wordbomb</code> are configurable across several options, including bomb speed, starting difficulty (one of sixteen named buckets, from Tranquil down to the single-word Singularity tier), prompt length, allowed special characters, and an optional themed category filter.

''Main article:'' [[Wordbomb]]

=== Wordle ===
A private word-guessing game with two modes: Standardized, which applies stricter word validity rules, and Full Dictionary, which allows any word in the bot's full dictionary. Players choose a target word length and may optionally allow hyphenated words as valid answers. Win streaks are tracked separately for each word length and mode.

''Main article:'' [[Wordle]]

=== Anagram ===
A private single-player game in which the bot selects a base word and the player attempts to find as many valid words as possible using only the letters available in it.

''Main article:'' [[Anagram]]

=== Dictionary Tools ===
Two related but separate features track a player's progress through the dictionary. <code>/dictionaries</code> reports progress against specific themed word lists. <code>/wordhunt</code> is a recurring personal challenge, refreshing every 12 hours, that surfaces dictionary words the player has not yet used.

== Fool's Mode ==
A special, occasional state, traditionally run around April Fools' Day, in which the bot's word validation is deliberately loosened for comedic effect — words with no spaces are accepted as playable regardless of dictionary membership, and several commands (<code>!i</code>/<code>!info</code>, <code>/check</code>, the end-of-game summary) start returning deliberately unreliable or nonsensical output. It is toggled on and off manually by the bot's operator rather than being scheduled automatically by the code itself.

''Main article:'' [[Fool's Mode]]

== Development ==
''Super-Shiritori'' has been developed and maintained by Ghost (no_where.ghost_002) since November 22, 2024, with administrative and moderation support from Kos (kos256) and GreenyMage (greenymage).

The bot's dictionary began as a small curated word list originally compiled by OMG, creator of the Roblox game ''Word Bomb''. It later expanded through a bulk import of 320,000 words, followed by ongoing contributions from users, dictionary scraping from sources such as Merriam-Webster and Oxford, and the inclusion of acronyms, constructed languages, and foreign-language borrowings. The dictionary now exceeds 1.6 million entries. There is no anti-cheat system in place; players are free to consult external dictionaries or search engines, though playing without assistance is encouraged.

The bot runs on hardware maintained directly by its developer, [[Ghost (Owner)|Ghost]], rather than on any cloud hosting service. It went offline on April 27, 2026, at the start of a military [https://en.wikipedia.org/wiki/Permanent_change_of_station Permanent Change of Station] ({{wc|PCS}}) relocation that took Ghost from South Korea through Japan, Alaska, and Los Angeles, California, before he finally settled in Hawaii on June 8, 2026. A subsequent housing shortage there delayed the bot's return well past initial estimates; it came back online on August 10, 2026, after roughly three and a half months offline — the longest outage in the bot's history. Household expenses connected to the move, including hosting costs, were covered as part of U.S. government {{wc|PCS}} support.

Since coming back online, an automatic restart-on-crash mechanism has been added, intended to make genuine 24/7 uptime realistic going forward; as of this writing, expected downtime is limited to maintenance, a crash severe enough to take the host machine itself down, or a power outage.

Two further features followed directly from that same reality. A planned restart or shutdown can now carry a custom message to every active game instead of one of two generic canned notices, so players get an accurate heads-up — an estimated outage length, for example — rather than a vague "update" notice. For the opposite case, a total, zero-warning loss of power gives the bot no chance to warn anyone before going offline at all; there's no way around that physically. What it can do instead is explain itself retroactively: reconnecting after any outage it wasn't able to shut down cleanly for now posts a message acknowledging the unplanned downtime, noting that unannounced power loss is a real and recurring possibility given the host machine's location, and confirming that any interrupted games have already been restored.

== Official Design ==
* The name is always spelled "Super-Shiritori".
* The official color is hex #F91000, informally named "Shiritorier's-Orange" as of December 1st.
* The logo is a mahjong-style tile featuring the Japanese characters ボ ("bo") and ツ ("tsu").

== External Links ==
* [https://discord.com/oauth2/authorize?client_id=1309504109308674089 Invite the bot to a server]
* [https://discord.gg/WahVXSkA7H Support server]
* [https://forms.gle/kUGHkSsxMH43iugb8 Word Curator Assessment Form]

== See also ==
* [[Discord Bots]]
* [[AI Bots]]
* [[Multiplayer Shiritori]]
* [[Solo Shiritori]]
* [[Protori]]
* [[Anagram]]
* [[Wordbomb]]
* [[Wordle]]
* [[Achievements]]
* [[Fool's Mode]]
* [[Manual-Tori]]
* [[Dictionary Information]]
* [[Word-Curatori]]
* [[Vexitori]]

[[Category:Information]]

Vexitori

2026-09-05T05:19:45Z

The CodeGhost: Give the box its own red/dark theme matching the profile picture

{{Infobox application
| name = Vexitori
| color = #E24C4C
| bg = #1a0808
| image = [[File:Vexitori.png|250px]]
| caption = Profile picture
| type = Discord Bot
| function = Vexillopedia flag-guessing game
| platform = Discord
| status = Active
| launched = August 12, 2026
| hosted = Hawaii, USA (via Discord)
| counterparts = [[Super-Shiritori]]<br>[[Word-Curatori]]
}}

'''Vexitori''' is a Discord bot dedicated to running [[Vexillopedia]], a continuous, automatic flag-guessing game (vexillology, the study of flags). It runs as a fully independent bot process, one of [[Discord Bots|three separate bots]] alongside [[Super-Shiritori]] and [[Word-Curatori]] — all three operate in the same Discord server, but Vexitori's flag game has no dependency on Shiritori, Anagram, Word Bomb, or any other game's state.

== Gameplay ==
Vexitori runs a continuous loop in a dedicated game channel: as soon as one round ends, a short pause is followed by the next flag spawning automatically, with no player action required to start a round.

Each round posts an embed showing the flag's '''Location''', '''Type''', and '''Time Era''' alongside the flag image itself — but not its name. Players guess by clicking a "Click here to Guess?" button, which opens a text-entry popup; a submitted guess is checked against the flag's full list of accepted names (a flag can have more than one correct answer — alternate names, spellings, or former names all count).

The first correct guess starts a '''15-second''' countdown before the round locks; anyone who guesses correctly before it ends is recorded as a winner, so a round is rarely a race to be first so much as a race to answer before the window closes. If nobody interacts with a round at all for '''5 minutes''', it ends early on its own rather than waiting indefinitely.

When a round ends, results are posted showing every winner, the exact name they typed, whether it was their first time correctly answering that flag with that specific name (marked 🆕) or a repeat, and their current win streak. Every '''50th consecutive round won''' by the same player triggers a bonus: a "Special Flag" spawns exclusively for that player for 20 seconds, drawn from a separate pool of flags reserved only for this purpose.

A separate channel supports free-form regex search: typing a pattern directly into it (no command prefix) searches every flag's accepted names for a match and returns a paginated result list.

== Commands ==
{| class="wikitable"
! Command !! Description
|-
| <code>/vexillum_information</code> || Looks up a specific flag by name or ID, or shows overall database totals if no flag is given.
|-
| <code>/vexillolist</code> || A paginated, filterable list of every flag in the database, showing personal completion progress.
|-
| <code>/vex_add</code> || Curator-only. Adds a new flag (image, location, type, time era, and one or more accepted names) to the database.
|-
| <code>/vex_edit</code> || Curator-only. Edits an existing flag's image, names, location, type, time era, or displayed ("dominant") name.
|-
| <code>/vex_delete</code> || Curator-only. Removes a flag from the database. Deletion is logged with an undo control.
|-
| <code>!vexrgb</code> || Curator-only. Randomizes the embed accent color of every flag in the database.
|-
| <code>!id</code> || Restricted to specific individuals. Lists all flag IDs currently in use, or renumbers a flag's ID.
|}

== Flag Pools ==
Flags are identified by a numeric ID. Ordinary rounds are drawn only from flags with a '''positive''' ID, and the game avoids repeating any flag that appeared in roughly the last 25 rounds. Flags with a '''negative''' ID are held back from normal rotation entirely and only ever appear as the 50-win-streak Special Flag reward.

== Architecture ==
Vexitori runs as its own separate Discord bot process — a distinct login token and OS process from both [[Super-Shiritori]] and [[Word-Curatori]] — rather than as a module inside the main game bot. This was possible because the flag game touches none of Super-Shiritori's shared game state; its only real dependency, the flag database itself, is self-contained within Vexitori.

== Status ==
Vexillopedia (the flag database Vexitori runs) is still an actively developed, in-testing project, maintained separately from Super-Shiritori itself. As of a public announcement on August 8, 2026, its maintainer stated he is currently hospitalized, for reasons he has chosen not to disclose publicly, and that new flag submissions are paused with no set timeline until he returns.

== See also ==
* [[Discord Bots]]
* [[Super-Shiritori]]
* [[Word-Curatori]]

[[Category:Information]]

Word-Curatori

2026-09-05T05:19:43Z

The CodeGhost: Fix Hosted in (was showing the 2023 launch location, not current) and give the box its own cyan/dark theme

{{Infobox application
| name = Word-Curatori
| color = #5BC8F2
| bg = #081018
| image = [[File:Word-Curatori.png|250px]]
| caption = Profile picture
| type = Discord Bot
| function = Word curation & dictionary management
| platform = Discord
| status = Active
| launched = August 28, 2023
| hosted_from = Washington State, USA (via Discord)
| hosted = Hawaii, USA (via Discord)
| access = Dictionary write access (sole writer)
| counterparts = [[Super-Shiritori]]<br>[[Vexitori]]
}}

'''Word-Curatori''' is the Discord bot responsible for word curation: it is the only one of [[Discord Bots|three separate bots]] — alongside [[Super-Shiritori]] and [[Vexitori]] — that is allowed to write to the dictionary files. Curators use it directly to add or remove words, and it runs the review workflow behind [[Super-Shiritori]]'s <code>/suggest</code> command. For the standards curators actually apply when deciding whether a word belongs, see [[Dictionary Information]]; this page covers the bot itself.

== Commands ==
{| class="wikitable"
! Command !! Description
|-
| <code>!add</code> (alias <code>!a</code>) || Curator only. Adds one word to a dictionary. Accepts a single typed word, an attached text file (one word per line), or a path to a text file on the bot's own machine. With no dictionary named, the word goes to a staging area and merges into the main dictionary shortly after.
|-
| <code>!remove</code> (alias <code>!r</code>) || Curator only. Removes one word, the same three ways <code>!add</code> accepts input. With no dictionary named, it's removed from the main dictionary and every themed category file it appears in.
|-
| <code>!check</code> || Curator only. Lists suggestions and removal requests (submitted elsewhere via <code>/suggest</code>) still waiting for a curator to Accept or Reject.
|-
| <code>!help</code> || Shows the bot's own command list.
|-
| <code>/suggest_ban</code> || Bans a user from using <code>/suggest</code>. Restricted to server mods, admins, and the bot owner — deliberately '''not''' gated on the word curator role, since who gets to submit suggestions is treated as a moderation decision rather than a curation one.
|-
| <code>/suggest_unban</code> || Reverses a <code>/suggest_ban</code>. Same restriction as above.
|}

<code>/suggest</code> itself is registered on [[Super-Shiritori]] (so it's discoverable from anywhere alongside every other player command), but everything that happens after it's invoked — validating the words, checking them against the live dictionary, posting the review embed, and handling the Accept/Review Manually/Reject/Cancel buttons — actually runs on Word-Curatori. The two bots talk over a small local-only connection for this purpose.

== Background Tasks ==
Word-Curatori runs several tasks on its own schedule, independent of any command:
* '''Limbo merge''' — every 2 minutes, words accepted via <code>/suggest</code> or added without a specific dictionary named are merged from a staging area into the live main dictionary.
* '''Dictionary backup''' — an hourly snapshot of the dictionary files.
* '''Auto-category backfill''' — runs once at startup, sorting words into a few automatically-derived categories (such as by length or palindrome status) rather than requiring a curator to do it by hand.

== Architecture ==
Word-Curatori runs as a completely separate Discord bot process from [[Super-Shiritori]] and [[Vexitori]] — its own login token, its own OS process — specifically so that heavy curation work (bulk word additions, full dictionary rewrites) can never stall the game bot's responsiveness. Running two bots as threads or async tasks inside one process would still contend for the same CPU time under Python's GIL; a genuinely separate process gives real operating-system-level isolation instead.

Word-Curatori is the '''sole writer''' of the dictionary files. [[Super-Shiritori]] only ever reads them, picking up whatever changes Word-Curatori has made within about 30 seconds.

== See also ==
* [[Dictionary Information]]
* [[Super-Shiritori]]

[[Category:Information]]

MediaWiki:Common.js

2026-09-05T05:18:43Z

The CodeGhost: Add infobox gallery tab-switching and mobile infobox reordering (below lead paragraph, Wikipedia-style)

Template:Infobox application

2026-09-05T05:18:41Z

The CodeGhost: Add per-bot color/bg theming, multi-image tab-bar gallery, and split hosted into origin/current

<includeonly><templatestyles src="Infobox application/styles.css"/><div class="infobox-application"{{#if:{{{color|}}}{{{bg|}}}| style="{{#if:{{{color|}}}|--ia-accent: {{{color}}};}}{{#if:{{{bg|}}}| --ia-bg: {{{bg}}};}}"}}>
<div class="infobox-application__title">{{{name|{{PAGENAME}}}}}</div>{{#if:{{{image2|}}}|
<div class="infobox-application__gallery">
<div class="infobox-application__gallery-tabs">
<div class="infobox-application__gallery-tab is-active" data-ia-tab="0">{{{caption1|Image 1}}}</div>{{#if:{{{image2|}}}|<div class="infobox-application__gallery-tab" data-ia-tab="1">{{{caption2|Image 2}}}</div>}}{{#if:{{{image3|}}}|<div class="infobox-application__gallery-tab" data-ia-tab="2">{{{caption3|Image 3}}}</div>}}{{#if:{{{image4|}}}|<div class="infobox-application__gallery-tab" data-ia-tab="3">{{{caption4|Image 4}}}</div>}}{{#if:{{{image5|}}}|<div class="infobox-application__gallery-tab" data-ia-tab="4">{{{caption5|Image 5}}}</div>}}{{#if:{{{image6|}}}|<div class="infobox-application__gallery-tab" data-ia-tab="5">{{{caption6|Image 6}}}</div>}}
</div>
<div class="infobox-application__gallery-slide" data-ia-slide="0">{{{image1|}}}{{#if:{{{caption1|}}}|<div class="infobox-application__gallery-caption">{{{caption1}}}</div>}}</div>{{#if:{{{image2|}}}|<div class="infobox-application__gallery-slide" data-ia-slide="1" hidden>{{{image2}}}{{#if:{{{caption2|}}}|<div class="infobox-application__gallery-caption">{{{caption2}}}</div>}}</div>}}{{#if:{{{image3|}}}|<div class="infobox-application__gallery-slide" data-ia-slide="2" hidden>{{{image3}}}{{#if:{{{caption3|}}}|<div class="infobox-application__gallery-caption">{{{caption3}}}</div>}}</div>}}{{#if:{{{image4|}}}|<div class="infobox-application__gallery-slide" data-ia-slide="3" hidden>{{{image4}}}{{#if:{{{caption4|}}}|<div class="infobox-application__gallery-caption">{{{caption4}}}</div>}}</div>}}{{#if:{{{image5|}}}|<div class="infobox-application__gallery-slide" data-ia-slide="4" hidden>{{{image5}}}{{#if:{{{caption5|}}}|<div class="infobox-application__gallery-caption">{{{caption5}}}</div>}}</div>}}{{#if:{{{image6|}}}|<div class="infobox-application__gallery-slide" data-ia-slide="5" hidden>{{{image6}}}{{#if:{{{caption6|}}}|<div class="infobox-application__gallery-caption">{{{caption6}}}</div>}}</div>}}
</div>
|{{#if:{{{image|}}}|
<div class="infobox-application__image">{{{image}}}</div>}}{{#if:{{{caption|}}}|
<div class="infobox-application__caption">{{{caption}}}</div>}}}}{{#if:{{{type|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Type</div><div class="infobox-application__value">{{{type}}}</div></div>}}{{#if:{{{function|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Function</div><div class="infobox-application__value">{{{function}}}</div></div>}}{{#if:{{{aliases|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Aliases</div><div class="infobox-application__value">{{{aliases}}}</div></div>}}{{#if:{{{platform|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Platform</div><div class="infobox-application__value">{{{platform}}}</div></div>}}{{#if:{{{developer|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Developer</div><div class="infobox-application__value">{{{developer}}}</div></div>}}{{#if:{{{language|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Language</div><div class="infobox-application__value">{{{language}}}</div></div>}}{{#if:{{{status|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Status</div><div class="infobox-application__value">{{{status}}}</div></div>}}{{#if:{{{launched|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Launched</div><div class="infobox-application__value">{{{launched}}}</div></div>}}{{#if:{{{hosted|}}}|{{#if:{{{hosted_from|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Originally hosted</div><div class="infobox-application__value">{{{hosted_from}}}</div></div>
<div class="infobox-application__row"><div class="infobox-application__label">Currently hosted</div><div class="infobox-application__value">{{{hosted}}}</div></div>|
<div class="infobox-application__row"><div class="infobox-application__label">Hosted in</div><div class="infobox-application__value">{{{hosted}}}</div></div>}}}}{{#if:{{{access|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Access</div><div class="infobox-application__value">{{{access}}}</div></div>}}{{#if:{{{counterparts|}}}|
<div class="infobox-application__row"><div class="infobox-application__label">Related bots</div><div class="infobox-application__value">{{{counterparts}}}</div></div>}}
</div>{{#ifeq: {{NAMESPACENUMBER}} | 0 | [[Category:Applications]]}}</includeonly><noinclude>
== Description ==
A dark-themed infobox for the wiki's Discord bots/applications (Super-Shiritori, Word-Curatori, Vexitori). Replaces the old <code><nowiki>{{Character}}</nowiki></code> template, which was raw Fandom "Portable Infobox" markup (<code><nowiki><infobox type="Character"></nowiki></code>) left over from the Fandom migration -- that extension was never self-hostable, so it rendered as literal unparsed tags rather than an actual infobox, and its fields (Species, Gender, Portrayed by, Marital status...) were built for fictional characters, not bots.

== Syntax ==
<pre>
{{Infobox application
| name =
| color =
| bg =
| image = [[File:Example.png|250px]]
| caption =
| image1 =
| caption1 =
| image2 =
| caption2 =
| type = Discord Bot
| function =
| aliases =
| platform = Discord
| developer =
| language =
| status = Active
| launched =
| hosted_from =
| hosted =
| access =
| counterparts =
}}
</pre>

All fields are optional except <code>name</code> (which defaults to the page title). A blank/omitted field just doesn't render that row.

'''Single image:''' use <code>image</code> (full wikitext, e.g. <code><nowiki>[[File:Example.png|250px]]</nowiki></code>) and optionally <code>caption</code>.

'''Multiple images (clickable tab bar):''' once <code>image2</code> is set, the box switches to tabbed-gallery mode -- use <code>image1</code>/<code>caption1</code>, <code>image2</code>/<code>caption2</code>, up through <code>image6</code>/<code>caption6</code>. Each caption becomes a tab label; clicking a tab swaps the picture. See [[Super-Shiritori]] for a live 4-image example. (Requires JavaScript -- with it off, only the first image shows.)

'''Color scheme:''' <code>color</code> sets the accent color (tab bar, labels, header text -- default site orange <code>#F19000</code>); <code>bg</code> sets the card's background (default <code>#2a0f00</code>). Pick both to theme a box around its own images instead of the default orange/brown. Keep <code>bg</code> dark -- body text is a fixed light gray and won't stay readable on a light background.

<code>hosted</code> is always the '''current''' hosting location. Add <code>hosted_from</code> only if that location has changed since launch -- doing so splits the single "Hosted in" row into "Originally hosted" / "Currently hosted" instead. Leave <code>hosted_from</code> out for a bot that's never moved.

[[Category:Infobox templates]]
</noinclude>

Template:Infobox application/styles.css

2026-09-05T05:18:40Z

The CodeGhost: Add --ia-accent/--ia-bg custom-property support and multi-image tabbed gallery styles

/* Colors come from --ia-accent / --ia-bg custom properties set inline by the
template (see Template:Infobox_application `color=` / `bg=` params) so each
page can theme its own infobox around its own images. The var() fallbacks
below are what you get if a page doesn't set them -- the original orange/
dark-brown look. */

.infobox-application {
float: right;
clear: right;
width: 300px;
margin: 0 0 1em 1em;
background-color: var(--ia-bg, #2a0f00);
border: 1px solid rgba(255, 255, 255, 0.15);
border-radius: 4px;
box-shadow: 0 4px 12px rgba(0, 0, 0, 0.4);
font-size: 88%;
line-height: 1.4;
}

.infobox-application__title {
background-color: #1a0a00;
color: var(--ia-accent, #F19000);
font-size: 120%;
font-weight: bold;
text-align: center;
padding: 8px;
border-bottom: 1px solid rgba(255, 255, 255, 0.15);
border-radius: 4px 4px 0 0;
}

.infobox-application__image {
text-align: center;
padding: 8px;
border-bottom: 1px solid rgba(255, 255, 255, 0.1);
}

.infobox-application__image img {
max-width: 100%;
}

.infobox-application__caption {
font-style: italic;
color: #D5D4D4;
font-size: 90%;
text-align: center;
padding: 4px 8px;
border-bottom: 1px solid rgba(255, 255, 255, 0.1);
}

.infobox-application__row {
display: flex;
padding: 4px 8px;
border-bottom: 1px solid rgba(255, 255, 255, 0.08);
}

.infobox-application__row:last-child {
border-bottom: none;
}

.infobox-application__label {
color: var(--ia-accent, #F19000);
font-weight: bold;
width: 40%;
flex-shrink: 0;
padding-right: 6px;
}

.infobox-application__value {
color: #D5D4D4;
width: 60%;
}

/* --- Multi-image tabbed gallery (image1/caption1, image2/caption2, ...) --- */
.infobox-application__gallery-tabs {
display: flex;
overflow-x: auto;
background-color: var(--ia-accent, #F19000);
}

.infobox-application__gallery-tab {
flex: 0 0 auto;
color: #1a0a00;
font-weight: bold;
font-size: 90%;
padding: 8px 10px;
cursor: pointer;
white-space: nowrap;
border-bottom: 3px solid transparent;
user-select: none;
}

.infobox-application__gallery-tab.is-active {
background-color: rgba(0, 0, 0, 0.2);
border-bottom-color: #1a0a00;
}

.infobox-application__gallery-tab:hover {
background-color: rgba(0, 0, 0, 0.12);
}

.infobox-application__gallery-slide {
text-align: center;
padding: 8px;
}

.infobox-application__gallery-slide[hidden] {
display: none;
}

.infobox-application__gallery-slide img {
max-width: 100%;
}

.infobox-application__gallery-caption {
font-style: italic;
color: #D5D4D4;
font-size: 90%;
text-align: center;
padding: 0 8px 8px;
border-bottom: 1px solid rgba(255, 255, 255, 0.1);
}

/* Below this, a 300px fixed-width float leaves almost no room for the
article text beside it (down to a single-character-wide column on a
phone) -- drop the float and let the box take the full column width. */
@media screen and (max-width: 550px) {
.infobox-application {
float: none;
clear: both;
width: auto;
margin: 0 0 1em 0;
}
}

Template:Infobox application/styles.css

2026-09-05T05:08:30Z

The CodeGhost: Fix mobile: drop the float below 550px, was squeezing article text into a 1-char-wide column

.infobox-application {
float: right;
clear: right;
width: 300px;
margin: 0 0 1em 1em;
background-color: #2a0f00;
border: 1px solid rgba(255, 255, 255, 0.15);
border-radius: 4px;
box-shadow: 0 4px 12px rgba(0, 0, 0, 0.4);
font-size: 88%;
line-height: 1.4;
}

.infobox-application__title {
background-color: #1a0a00;
color: #F19000;
font-size: 120%;
font-weight: bold;
text-align: center;
padding: 8px;
border-bottom: 1px solid rgba(255, 255, 255, 0.15);
border-radius: 4px 4px 0 0;
}

.infobox-application__image {
text-align: center;
padding: 8px;
border-bottom: 1px solid rgba(255, 255, 255, 0.1);
}

.infobox-application__image img {
max-width: 100%;
}

.infobox-application__caption {
font-style: italic;
color: #D5D4D4;
font-size: 90%;
text-align: center;
padding: 4px 8px;
border-bottom: 1px solid rgba(255, 255, 255, 0.1);
}

.infobox-application__row {
display: flex;
padding: 4px 8px;
border-bottom: 1px solid rgba(255, 255, 255, 0.08);
}

.infobox-application__row:last-child {
border-bottom: none;
}

.infobox-application__label {
color: #F19000;
font-weight: bold;
width: 40%;
flex-shrink: 0;
padding-right: 6px;
}

.infobox-application__value {
color: #D5D4D4;
width: 60%;
}

/* Below this, a 300px fixed-width float leaves almost no room for the
article text beside it (down to a single-character-wide column on a
phone) -- drop the float and let the box take the full column width. */
@media screen and (max-width: 550px) {
.infobox-application {
float: none;
clear: both;
width: auto;
margin: 0 0 1em 0;
}
}

Template:Character

2026-09-05T05:06:25Z

The CodeGhost: Retire this template -- it was raw Fandom Portable-Infobox markup that never worked here; replaced by Template:Infobox application on all 3 pages that used it

#REDIRECT [[Template:Infobox application]]

Super-Shiritori

2026-09-05T05:06:02Z

The CodeGhost: Switch to the new Infobox application template (old Character infobox was broken Fandom Portable-Infobox markup)

{{Infobox application
| name = Super-Shiritori
| image = <gallery>
Super Shiritori Bot (Discord).png|Main profile picture
Super-Merritori.png|Holiday profile picture
Halloween Shiritori PFP.png|Halloween profile picture
Original Super-Shiritori PFP.webp|Original profile picture
</gallery>
| aliases = Super Shiritori, Shiritori
| type = Discord Bot
| function = Flagship word-chain game bot
| platform = Discord
| status = Active
| launched = November 22, 2024
| hosted = Washington State, USA (via Discord)
| counterparts = [[Word-Curatori]] (originally called "Super Shiritori (Test Edition)")<br>[[Vexitori]]
}}

'''Super-Shiritori''' is the flagship Discord bot of the project, running a word-chain game in which players respond with a word beginning with the final letter of the previous word. Alongside its core game, it supports several related word-based modes, tracks detailed player statistics, and maintains the shared dictionary of over 1.6 million entries. It is one of [[Discord Bots|three separate bots]] that make up the project, running alongside [[Word-Curatori]] and [[Vexitori]].

== Features ==
* Multiplayer and solo word-chain gameplay, against other players or AI opponents with distinct personalities
* A dictionary exceeding 1.6 million entries, drawn from acronyms, user submissions, foreign-language borrowings, constructed languages, and established published dictionaries
* Additional game modes, including Word Bomb, Wordle, Anagram, and Protori
* A rarity-based word rolling and trading system
* Player statistics, leaderboards, and a leveling system with unlockable [[Achievements]] (formerly called titles)
* Deployable in any Discord server
* A small number of hidden text-trigger commands functioning as puzzle easter eggs

== Bot Commands ==

=== Multiplayer Shiritori ===
{| class="wikitable"
! Command !! Description
|-
| <code>/start_shiritori [#channel]</code> || Starts a multiplayer game in the specified channel. Requires the Manage Messages permission or bot owner status.
|-
| <code>/end_shiritori</code> || Manually ends the current game and displays final statistics.
|-
| <code>/invite_ai</code> || Invites an AI opponent with a randomly assigned personality into the current game.
|-
| <code>/murder_ai</code> || Attempts to remove the current AI opponent from the game.
|-
| <code>/leaderboard</code> || Displays the server's multiplayer leaderboard by category.
|-
| <code>/my_stats</code> || Displays the player's personal global multiplayer statistics.
|-
| <code>/levels_leaderboard</code> || Displays the server's level leaderboard.
|-
| <code>/level</code> || Displays the player's current level and experience progress.
|-
| <code>/restore_games</code> || Restores active games after a bot restart or shutdown.
|-
| <code>/global_stats</code> || Displays aggregated multiplayer statistics across all servers.
|}
''Main article:'' [[Multiplayer Shiritori]]

=== Protori ===
{| class="wikitable"
! Command !! Description
|-
| <code>/start_protori [#channel]</code> || Starts a Protori game in the specified channel. Requires the Manage Messages permission or bot owner/curator status.
|-
| <code>/end_protori</code> || Manually ends the current Protori game.
|-
| <code>/protori_stats</code> || Displays the player's Protori statistics, both globally and broken down per server.
|-
| <code>/protori_leaderboard</code> || Displays the Protori leaderboard, server or global.
|}
''Main article:'' [[Protori]]

=== Solo Shiritori ===
{| class="wikitable"
! Command !! Description
|-
| <code>/solo_shiritori</code> || Starts a private solo game against the AI in a dedicated thread.
|-
| <code>/solo_stats</code> || Displays the player's solo statistics.
|-
| <code>/solo_leaderboard</code> || Displays the global solo leaderboard.
|}
''Main article:'' [[Solo Shiritori]]

=== Wordle ===
{| class="wikitable"
! Command !! Description
|-
| <code>/wordle</code> || Starts a private Wordle game.
|-
| <code>/wordle_leaderboard</code> || Displays Wordle win streaks by word length and mode.
|-
| <code>/wordle_stats</code> || Displays the player's personal Wordle win streaks by mode.
|}
''Main article:'' [[Wordle]]

=== Word Bomb ===
{| class="wikitable"
! Command !! Description
|-
| <code>/wordbomb</code> || Starts a Word Bomb game.
|-
| <code>/wordbomb_leaderboard</code> || Displays the server's Word Bomb leaderboard.
|-
| <code>/wordbomb_stats</code> || Displays the player's personal Word Bomb statistics.
|}
''Main article:'' [[Wordbomb]]

=== Anagram ===
{| class="wikitable"
! Command !! Description
|-
| <code>/anagram</code> || Starts a private Anagram game.
|-
| <code>/anagram_stats</code> || Displays the player's personal Anagram statistics.
|-
| <code>/anagram_leaderboard</code> || Displays the server's Anagram leaderboard.
|}
''Main article:'' [[Anagram]]

=== Dictionary and Words ===
{| class="wikitable"
! Command !! Description
|-
| <code>/dictionaries</code> || Checks the player's progress against specific themed word lists.
|-
| <code>/check</code> || Checks whether one or more words are in the dictionary.
|-
| <code>/characters</code> || Displays the character count of the given word or words.
|-
| <code>/solve</code> || Searches for words matching a given prompt, length, or other criteria.
|-
| <code>/suggest</code> || Suggests a word for addition to the dictionary, or proposes removal of an existing entry.
|-
| <code>/define</code> || Returns an AI-generated definition of a word.
|-
| <code>/word_collection</code> || Displays a player's collected words.
|-
| <code>/random_word</code> || Returns a random word that has not yet been played.
|-
| <code>/wordhunt</code> || A recurring personal challenge, refreshing every 12 hours, that prompts the player to find dictionary words they have not yet used.
|}
''Main article:'' [[Dictionary Information]]

=== Casino and RNG ===
{| class="wikitable"
! Command !! Description
|-
| <code>/roll</code> || Rolls for a random word, weighted by rarity.
|-
| <code>/set_casino</code> || Sets or removes the channels where <code>/roll</code> may be used.
|-
| <code>/rng_draw</code> || Spins for a chance at rarer rewards.
|-
| <code>/rng_stats</code> || Displays the player's personal rolling statistics.
|-
| <code>/rng_global</code> || Displays global rolling statistics.
|-
| <code>/rng_set_luck</code> || Sets the player's luck multiplier for rolls.
|-
| <code>/word_trade</code> || Trades a word with another player.
|}

=== Achievements ===
{| class="wikitable"
! Command !! Description
|-
| <code>/achievements</code> || Displays the player's unlocked and obtainable achievements. Public/Private visibility choice.
|-
| <code>/set_achievement</code> || Sets or clears the player's displayed achievement from among those unlocked.
|}
''Main article:'' [[Achievements]]

=== Configuration and Utility ===
{| class="wikitable"
! Command !! Description
|-
| <code>/toggle_corrections</code> || Toggles whether invalid words are deleted and warned about, or only marked with a reaction. Requires the Manage Messages permission.
|-
| <code>/config_view</code> || Displays the server's configuration for AI event logging and word suggestion notifications.
|-
| <code>/server</code> || Returns an invite link to the official support server.
|-
| <code>/wiki</code> || Returns a link to this wiki.
|-
| <code>/curator_form</code> || Returns a link to the Word Curator application form.
|-
| <code>/help</code> || Displays a list of all commands.
|}

== Quick Chat Commands ==
{| class="wikitable"
! Command !! Description
|-
| <code>!i</code> || An expanded version of <code>/check</code> with more detail.
|-
| <code>!level</code> || Quick view of the player's level and experience progress.
|-
| <code>!achieve</code>, <code>!achievement</code>, <code>!achievements</code> || Opens the player's list of unlocked and obtainable achievements. All three aliases work identically.
|-
| <code>!check</code> || Curator only. Checks the status of pending word suggestions and removals.
|-
| <code>!status</code> || Displays the current game's status, including words played, average word length, and the next required letter.
|-
| <code>!longest</code> || Displays the top five longest words played in the current game.
|-
| <code>!rng <word></code> || Checks a word's rarity and global ownership.
|}
A small number of additional text-trigger commands exist as hidden puzzle easter eggs. Their exact triggers are not documented publicly here. Separately, a set of documented explainer commands — <code>!hyphens</code>, <code>!neoses</code>, <code>!aisource</code>, and their aliases — answer common questions about dictionary rules; see [[Dictionary Information]].

== AI Opponents ==
Multiplayer games may include an AI opponent, added either randomly through <code>/invite_ai</code> or by summoning a specific personality with a text command. Each of the 19 personalities follows its own word-selection logic — NOOB favors short, simple words, PRO requires words of at least twelve letters, MIMIC attempts to answer with an anagram of the player's own last word, and so on. Two further AI types, Sniper and Assassin, layer additional mechanics — one-shot dramatic word plays and a hijack-and-silence risk/reward exchange, respectively — on top of the base system.

''Main article:'' [[AI Bots]]

== Game Modes ==

=== Multiplayer Shiritori ===
The core game mode. Players take turns submitting words in a shared channel, each beginning with the final letter of the previous word. Repeated words, invalid characters, and words that do not follow the required letter all end a player's turn or the game, depending on server configuration.

''Main article:'' [[Multiplayer Shiritori]]

=== Protori ===
A scoring-based variant of multiplayer Shiritori. Rather than simply continuing the chain, every accepted word earns points from a flat per-letter point table, weighted by how rare each letter is in the dictionary rather than a standard Scrabble-style tile distribution; a word's base score is just the sum of its letters' values. Continuing more deeply into the previous word than just its final letter — matching several trailing characters in a row — earns a chain bonus of roughly 1% of the word's base score per matched character, up to about +79% for a very deep match. Playing a word that has already been used ends the game immediately and costs the player a 250-point penalty.

''Main article:'' [[Protori]]

=== Solo Shiritori ===
A private word-chain match played against an adaptive AI opponent in a dedicated thread. The AI begins as ROOKIE and its behavior shifts over time based on the player's performance and random chance.

''Main article:'' [[Solo Shiritori]]

=== Word Bomb ===
An elimination game for up to 16 players, each starting with three lives. On each turn, a player must submit a valid dictionary word containing an assigned prompt string before a timer runs out; failing to do so costs a life. Games started through <code>/wordbomb</code> are configurable across several options, including bomb speed, starting difficulty (one of sixteen named buckets, from Tranquil down to the single-word Singularity tier), prompt length, allowed special characters, and an optional themed category filter.

''Main article:'' [[Wordbomb]]

=== Wordle ===
A private word-guessing game with two modes: Standardized, which applies stricter word validity rules, and Full Dictionary, which allows any word in the bot's full dictionary. Players choose a target word length and may optionally allow hyphenated words as valid answers. Win streaks are tracked separately for each word length and mode.

''Main article:'' [[Wordle]]

=== Anagram ===
A private single-player game in which the bot selects a base word and the player attempts to find as many valid words as possible using only the letters available in it.

''Main article:'' [[Anagram]]

=== Dictionary Tools ===
Two related but separate features track a player's progress through the dictionary. <code>/dictionaries</code> reports progress against specific themed word lists. <code>/wordhunt</code> is a recurring personal challenge, refreshing every 12 hours, that surfaces dictionary words the player has not yet used.

== Fool's Mode ==
A special, occasional state, traditionally run around April Fools' Day, in which the bot's word validation is deliberately loosened for comedic effect — words with no spaces are accepted as playable regardless of dictionary membership, and several commands (<code>!i</code>/<code>!info</code>, <code>/check</code>, the end-of-game summary) start returning deliberately unreliable or nonsensical output. It is toggled on and off manually by the bot's operator rather than being scheduled automatically by the code itself.

''Main article:'' [[Fool's Mode]]

== Development ==
''Super-Shiritori'' has been developed and maintained by Ghost (no_where.ghost_002) since November 22, 2024, with administrative and moderation support from Kos (kos256) and GreenyMage (greenymage).

The bot's dictionary began as a small curated word list originally compiled by OMG, creator of the Roblox game ''Word Bomb''. It later expanded through a bulk import of 320,000 words, followed by ongoing contributions from users, dictionary scraping from sources such as Merriam-Webster and Oxford, and the inclusion of acronyms, constructed languages, and foreign-language borrowings. The dictionary now exceeds 1.6 million entries. There is no anti-cheat system in place; players are free to consult external dictionaries or search engines, though playing without assistance is encouraged.

The bot runs on hardware maintained directly by its developer, [[Ghost (Owner)|Ghost]], rather than on any cloud hosting service. It went offline on April 27, 2026, at the start of a military [https://en.wikipedia.org/wiki/Permanent_change_of_station Permanent Change of Station] ({{wc|PCS}}) relocation that took Ghost from South Korea through Japan, Alaska, and Los Angeles, California, before he finally settled in Hawaii on June 8, 2026. A subsequent housing shortage there delayed the bot's return well past initial estimates; it came back online on August 10, 2026, after roughly three and a half months offline — the longest outage in the bot's history. Household expenses connected to the move, including hosting costs, were covered as part of U.S. government {{wc|PCS}} support.

Since coming back online, an automatic restart-on-crash mechanism has been added, intended to make genuine 24/7 uptime realistic going forward; as of this writing, expected downtime is limited to maintenance, a crash severe enough to take the host machine itself down, or a power outage.

Two further features followed directly from that same reality. A planned restart or shutdown can now carry a custom message to every active game instead of one of two generic canned notices, so players get an accurate heads-up — an estimated outage length, for example — rather than a vague "update" notice. For the opposite case, a total, zero-warning loss of power gives the bot no chance to warn anyone before going offline at all; there's no way around that physically. What it can do instead is explain itself retroactively: reconnecting after any outage it wasn't able to shut down cleanly for now posts a message acknowledging the unplanned downtime, noting that unannounced power loss is a real and recurring possibility given the host machine's location, and confirming that any interrupted games have already been restored.

== Official Design ==
* The name is always spelled "Super-Shiritori".
* The official color is hex #F91000, informally named "Shiritorier's-Orange" as of December 1st.
* The logo is a mahjong-style tile featuring the Japanese characters ボ ("bo") and ツ ("tsu").

== External Links ==
* [https://discord.com/oauth2/authorize?client_id=1309504109308674089 Invite the bot to a server]
* [https://discord.gg/WahVXSkA7H Support server]
* [https://forms.gle/kUGHkSsxMH43iugb8 Word Curator Assessment Form]

== See also ==
* [[Discord Bots]]
* [[AI Bots]]
* [[Multiplayer Shiritori]]
* [[Solo Shiritori]]
* [[Protori]]
* [[Anagram]]
* [[Wordbomb]]
* [[Wordle]]
* [[Achievements]]
* [[Fool's Mode]]
* [[Manual-Tori]]
* [[Dictionary Information]]
* [[Word-Curatori]]
* [[Vexitori]]

[[Category:Information]]

Vexitori

2026-09-05T05:05:58Z

The CodeGhost: Switch to the new Infobox application template (old Character infobox was broken Fandom Portable-Infobox markup)

{{Infobox application
| name = Vexitori
| image = [[File:Vexitori.png|250px]]
| caption = Profile picture
| type = Discord Bot
| function = Vexillopedia flag-guessing game
| platform = Discord
| status = Active
| launched = August 12, 2026
| hosted = Hawaii, USA (via Discord)
| counterparts = [[Super-Shiritori]]<br>[[Word-Curatori]]
}}

'''Vexitori''' is a Discord bot dedicated to running [[Vexillopedia]], a continuous, automatic flag-guessing game (vexillology, the study of flags). It runs as a fully independent bot process, one of [[Discord Bots|three separate bots]] alongside [[Super-Shiritori]] and [[Word-Curatori]] — all three operate in the same Discord server, but Vexitori's flag game has no dependency on Shiritori, Anagram, Word Bomb, or any other game's state.

== Gameplay ==
Vexitori runs a continuous loop in a dedicated game channel: as soon as one round ends, a short pause is followed by the next flag spawning automatically, with no player action required to start a round.

Each round posts an embed showing the flag's '''Location''', '''Type''', and '''Time Era''' alongside the flag image itself — but not its name. Players guess by clicking a "Click here to Guess?" button, which opens a text-entry popup; a submitted guess is checked against the flag's full list of accepted names (a flag can have more than one correct answer — alternate names, spellings, or former names all count).

The first correct guess starts a '''15-second''' countdown before the round locks; anyone who guesses correctly before it ends is recorded as a winner, so a round is rarely a race to be first so much as a race to answer before the window closes. If nobody interacts with a round at all for '''5 minutes''', it ends early on its own rather than waiting indefinitely.

When a round ends, results are posted showing every winner, the exact name they typed, whether it was their first time correctly answering that flag with that specific name (marked 🆕) or a repeat, and their current win streak. Every '''50th consecutive round won''' by the same player triggers a bonus: a "Special Flag" spawns exclusively for that player for 20 seconds, drawn from a separate pool of flags reserved only for this purpose.

A separate channel supports free-form regex search: typing a pattern directly into it (no command prefix) searches every flag's accepted names for a match and returns a paginated result list.

== Commands ==
{| class="wikitable"
! Command !! Description
|-
| <code>/vexillum_information</code> || Looks up a specific flag by name or ID, or shows overall database totals if no flag is given.
|-
| <code>/vexillolist</code> || A paginated, filterable list of every flag in the database, showing personal completion progress.
|-
| <code>/vex_add</code> || Curator-only. Adds a new flag (image, location, type, time era, and one or more accepted names) to the database.
|-
| <code>/vex_edit</code> || Curator-only. Edits an existing flag's image, names, location, type, time era, or displayed ("dominant") name.
|-
| <code>/vex_delete</code> || Curator-only. Removes a flag from the database. Deletion is logged with an undo control.
|-
| <code>!vexrgb</code> || Curator-only. Randomizes the embed accent color of every flag in the database.
|-
| <code>!id</code> || Restricted to specific individuals. Lists all flag IDs currently in use, or renumbers a flag's ID.
|}

== Flag Pools ==
Flags are identified by a numeric ID. Ordinary rounds are drawn only from flags with a '''positive''' ID, and the game avoids repeating any flag that appeared in roughly the last 25 rounds. Flags with a '''negative''' ID are held back from normal rotation entirely and only ever appear as the 50-win-streak Special Flag reward.

== Architecture ==
Vexitori runs as its own separate Discord bot process — a distinct login token and OS process from both [[Super-Shiritori]] and [[Word-Curatori]] — rather than as a module inside the main game bot. This was possible because the flag game touches none of Super-Shiritori's shared game state; its only real dependency, the flag database itself, is self-contained within Vexitori.

== Status ==
Vexillopedia (the flag database Vexitori runs) is still an actively developed, in-testing project, maintained separately from Super-Shiritori itself. As of a public announcement on August 8, 2026, its maintainer stated he is currently hospitalized, for reasons he has chosen not to disclose publicly, and that new flag submissions are paused with no set timeline until he returns.

== See also ==
* [[Discord Bots]]
* [[Super-Shiritori]]
* [[Word-Curatori]]

[[Category:Information]]

Word-Curatori

2026-09-05T05:05:53Z

The CodeGhost: Switch to the new Infobox application template (old Character infobox was broken Fandom Portable-Infobox markup)

{{Infobox application
| name = Word-Curatori
| image = [[File:Word-Curatori.png|250px]]
| caption = Profile picture
| type = Discord Bot
| function = Word curation & dictionary management
| platform = Discord
| status = Active
| launched = August 28, 2023
| hosted = Washington State, USA (via Discord)
| access = Dictionary write access (sole writer)
| counterparts = [[Super-Shiritori]]<br>[[Vexitori]]
}}

'''Word-Curatori''' is the Discord bot responsible for word curation: it is the only one of [[Discord Bots|three separate bots]] — alongside [[Super-Shiritori]] and [[Vexitori]] — that is allowed to write to the dictionary files. Curators use it directly to add or remove words, and it runs the review workflow behind [[Super-Shiritori]]'s <code>/suggest</code> command. For the standards curators actually apply when deciding whether a word belongs, see [[Dictionary Information]]; this page covers the bot itself.

== Commands ==
{| class="wikitable"
! Command !! Description
|-
| <code>!add</code> (alias <code>!a</code>) || Curator only. Adds one word to a dictionary. Accepts a single typed word, an attached text file (one word per line), or a path to a text file on the bot's own machine. With no dictionary named, the word goes to a staging area and merges into the main dictionary shortly after.
|-
| <code>!remove</code> (alias <code>!r</code>) || Curator only. Removes one word, the same three ways <code>!add</code> accepts input. With no dictionary named, it's removed from the main dictionary and every themed category file it appears in.
|-
| <code>!check</code> || Curator only. Lists suggestions and removal requests (submitted elsewhere via <code>/suggest</code>) still waiting for a curator to Accept or Reject.
|-
| <code>!help</code> || Shows the bot's own command list.
|-
| <code>/suggest_ban</code> || Bans a user from using <code>/suggest</code>. Restricted to server mods, admins, and the bot owner — deliberately '''not''' gated on the word curator role, since who gets to submit suggestions is treated as a moderation decision rather than a curation one.
|-
| <code>/suggest_unban</code> || Reverses a <code>/suggest_ban</code>. Same restriction as above.
|}

<code>/suggest</code> itself is registered on [[Super-Shiritori]] (so it's discoverable from anywhere alongside every other player command), but everything that happens after it's invoked — validating the words, checking them against the live dictionary, posting the review embed, and handling the Accept/Review Manually/Reject/Cancel buttons — actually runs on Word-Curatori. The two bots talk over a small local-only connection for this purpose.

== Background Tasks ==
Word-Curatori runs several tasks on its own schedule, independent of any command:
* '''Limbo merge''' — every 2 minutes, words accepted via <code>/suggest</code> or added without a specific dictionary named are merged from a staging area into the live main dictionary.
* '''Dictionary backup''' — an hourly snapshot of the dictionary files.
* '''Auto-category backfill''' — runs once at startup, sorting words into a few automatically-derived categories (such as by length or palindrome status) rather than requiring a curator to do it by hand.

== Architecture ==
Word-Curatori runs as a completely separate Discord bot process from [[Super-Shiritori]] and [[Vexitori]] — its own login token, its own OS process — specifically so that heavy curation work (bulk word additions, full dictionary rewrites) can never stall the game bot's responsiveness. Running two bots as threads or async tasks inside one process would still contend for the same CPU time under Python's GIL; a genuinely separate process gives real operating-system-level isolation instead.

Word-Curatori is the '''sole writer''' of the dictionary files. [[Super-Shiritori]] only ever reads them, picking up whatever changes Word-Curatori has made within about 30 seconds.

== See also ==
* [[Dictionary Information]]
* [[Super-Shiritori]]

[[Category:Information]]

Template:Infobox application

2026-09-05T05:04:31Z

2026-08-26T04:01:11Z

The CodeGhost: I was wondering why the other stuff doesn't exist in the page i was fiddling with

.mbox {
background-color: rgb(230, 230, 230);
border-color: rgb(230, 230, 230);
border-width: 0.5;
border-left-color: rgb(230, 230, 230);
border-radius: 0.1;
font-size: 11;
}

/* Internal links (use .internal first) */
a.internal:link,
a.internal:visited {
color: #de93db; /* pink */
}

/* Explicit safeguard: only links on *your* wiki */
.mw-parser-output a[href^="https://supershiritori.fandom.com"]:link,
.mw-parser-output a[href^="https://supershiritori.fandom.com"]:visited {
color: #de93db;
}

/* External + interwiki links */
a.external:link,
a.external:visited,
a.extiw:link,
a.extiw:visited {
color: #7d3cff; /* violet */
font-weight: bold;
text-decoration: underline dotted;
}

/* Fallback for any remaining http links (safety net) */
.mw-parser-output a[href^="http"]:link,
.mw-parser-output a[href^="http"]:visited {
color: #7d3cff;
}

/* Redlinks */
a.new,
.mw-parser-output a.new {
color: #ff0000; /* red */
}

/* FORCE BREAK GIANT ARTICLE TITLES */
.page-header__title-wrapper,
.page-header__main,
.page-header__title,
h1.page-header__title {
display: block !important;
min-width: 0 !important;
max-width: 100% !important;
width: 100% !important;
word-break: break-all !important;
overflow-wrap: break-word !important;
white-space: normal !important;
flex: 1 1 auto !important;
}

/* FORCE BREAK INSIDE BODY ARTICLES */
.mw-parser-output {
word-break: break-all !important;
overflow-wrap: break-word !important;
}

MediaWiki:Commons.css

The CodeGhost: Redirected page to Discord Bots

#REDIRECT [[Discord Bots]]