Super 6ix chat

A category is a heading that groups related chat rooms. For example, “Winter Cup” can contain “race-chat” and “setup-help”. You do not post messages into a category heading.

A channel is a conversation room. Open it to read or send messages. Messages stay in that room; they are not sent to every channel in the category.

A Discord server is the whole community, such as your racing club. RaceCentral’s series and chat categories are separate from its Discord server and categories. Renaming a chat category does not rename your series.

Everyone means visible to anyone who can access the series. Series members means all members of that series and the site owner—not organisers only. A category named “Organisers” does not make its channels private. Do not put organiser-only information in a members channel.

Collapsing a category only tidies your own channel list. It does not change access or stop message sharing. The red circle beside a channel shows your unread count.

1. Open Chat for the intended series. Select the Manage chat cog, or the + beside a category or channel to open the editor. Desktop right-click on a channel is another shortcut.
2. Enter a Category name and select Create category. A category does not connect to Discord automatically.
3. Open the category, expand Create channel, enter its name and description, review Who can read this channel?, then select Create channel.
4. Use Save name or Save channel after editing. A save applies that form only, keeps this editor open, and preserves other unsaved inputs.
5. Drag a category or channel name to reorder it. Release to save the order. Channels stay in their current category. A simple click still opens or expands the item. Move up / Move down are the non-drag alternative.
6. To move a channel into a different category, use Move to category and Move channel. Its audience does not change just because the heading changes.
7. Use × or Escape to close. If a form has unsaved changes, choose Save and close, Discard changes, or Keep editing. Discard does not undo earlier saves.

Connected channels must be disconnected before renaming, moving category, archiving or changing audience. Individual pairs can be reordered locally without disconnecting; this does not reorder Discord. Legacy bridge mappings must be resolved before reordering. Archive removes an RC item from active use but retains its history; restoring does not reconnect Discord. There is no permanent-delete control here.

The bot is RaceCentral’s automated member in your Discord server. It receives eligible Discord messages and sends RC messages to approved partner channels. Your personal Discord connection identifies you; it does not install the bot or make you a Discord manager.

1. Open your RaceCentral profile and use Connect Discord to link the intended identity. If that option is missing, ask the site administrator.
2. Ask the server owner or an authorised manager to check whether the official RaceCentral bot is already installed. Reuse that installation.
3. If needed, open Series management → Social Media & Communication → Discord chat bridge → Add RaceCentral bot. Select the intended existing server and review the application and permissions before authorising. Do not activate the separate legacy whole-series bridge just to install the bot.
4. For public individual links, the bot needs View Channel, Send Messages and Read Message History in the intended channel. File delivery also needs attachment permissions. The installation action may request broader legacy capabilities; ask the administrator if these are unexpected. Do not grant Administrator to bypass an error.
5. In Discord settings, enable Advanced → Developer Mode. Use Copy Server ID for the server and Copy Channel ID for the existing text channel. Copy a category’s ID only into a category ID field. Names and IDs are not interchangeable.

You must have authority to manage the Discord destination as well as RC integration rights. The bot’s access is not the audience’s access. Do not make a private channel public to force a link.

The RaceCentral platform operator runs the bridge service. You do not need your own bot, a developer application or a bot token. Never send passwords or tokens to another person. If the installation action is missing, ask the site administrator rather than using an unofficial invitation.

1. Confirm that this series is published and both the RC room and its existing Discord text-channel partner are public. Link your Discord identity and install the official bot first.
2. Open the RC category → Connect to Discord → the intended RC channel. Enter the exact Discord server and channel names and IDs.
3. Check the audience and destination. Tick the approval for sharing new messages, then select Request channel link.
4. Wait for Connected. “Awaiting Discord verification” is a request, not active sharing. Private or unknown access stays blocked.
5. Post harmless test text in RC and check for one attributed copy in the selected Discord channel. Post different harmless text in Discord and check for one copy in RC. Check that unselected channels and old histories remain unchanged.

You may explicitly pair one RC conversation with multiple approved destinations. They share the same new public conversation, including messages arriving from other paired servers. Every Discord channel can belong to only one live RC pair. Do not overlap individual links with a category or legacy bridge mapping.

New channels are never linked automatically. Old messages and messages sent while deliberately disconnected are not copied. Reconnecting establishes a fresh start point. Bot/webhook messages, edits, reactions, voice, forums and threads are not shared by this individual-channel bridge.

Connect a category to Discord → Use an existing Discord category: save the server and category IDs, then select Verify access & load channels. The bot checks your linked Discord identity, management permission and actual channel access. In the verified list, leave unwanted channels unlinked. For each selected channel choose a new Everyone room in RC or an eligible existing RC room, approve new-message sharing, then select Connect selected channels. Wait for Connected: the bot rechecks Discord before activation. Repeat for another approved server if needed.

Private, already-linked and unsupported channels are omitted. Reviews expire after 10 minutes; if channels or permissions change, review the refreshed list and confirm again. New RC rooms require channel-creation/audience permission. This flow does not create new channels on Discord; that separate provisioning option is not available yet.

Disconnect pair stops further delivery for that exact pair. Both channels and their existing history remain. A delivery already in progress may finish; completed disconnect prevents subsequent delivery. Other pairs stay connected.

After resolving an access problem, use Verify & reconnect, review the named partners, and confirm the fresh new-message start point. Wait for Connected and repeat the harmless two-direction test. Disconnected-period messages are not replayed.

• Saved draft, no messages: a draft is not connected. Verify access, select channels and confirm. The platform’s bot service must be running; your browser does not perform provider requests.
• Pending or blocked: check published series, public audiences, linked Discord identity, your destination-management permission and the bot’s channel permissions. Ask the site administrator to check the bridge if a valid request stays pending. Do not submit duplicates.
• Access changed: stop private posts and ask the authorised owner to resolve the actual permission difference. Do not widen access just to clear a warning.
• Duplicate names: compare exact IDs. Names alone never merge conversations. Do not recreate or delete populated channels to troubleshoot.
• Delivery is uncertain: check the destination before resending and tell authorised support the affected pair and time, without posting credentials or private message contents. Some failures require review rather than an automatic resend.
• Management control missing: check your assigned scope. Structure, access management and integration permissions are separate. A chat-manager role does not grant access to private messages.