Second Life + Discord · October 11, 2026 · 8 min read

How to Connect Second Life to Discord (No Scripts)

To connect Second Life to Discord without writing a line of LSL, sign in to Thunder Viewer in your browser, open Manage Discord, add the Thunder Viewer bot to your Discord server, pick a channel, and switch on the events you want: local chat, IMs, arrivals, group chat and more. Save, and in-world activity starts landing in Discord. Turn on the two-way options and your staff can answer from Discord too. Nothing to rez, no land permissions, no server to rent.

This is the hands-on, click-by-click companion to our complete guide to Discord bots for Second Life, which covers every approach and why communities bridge the two at all. Here we just get yours working.

What you'll have by the end

A Discord channel that receives the in-world events you chose, an optional two-way bridge so replies typed in Discord become IMs or local chat from your avatar, and an activity log for when something looks off. Expect about ten minutes, most of it spent deciding which events deserve a ping.

Prerequisites

• A Discord server where you can add apps. Discord only lets members with the Manage Server permission add a bot, so if it is a friend's or a store's server, ask an admin to do step 3 with you.
• A dedicated channel. Create one now, for example #sl-relay or #store-desk. Keeping the relay out of your general chat is the single best noise decision you will make.
• The avatar you want to relay. Sign in at Thunder Viewer with that avatar's Second Life username and password. With several avatars, the account switcher decides which one you are configuring.
• One session per avatar. Second Life allows one active login per account. If this avatar is open in Firestorm, signing in here will log the other one out. The usual pattern is your main avatar in Firestorm and the store or club avatar in Thunder Viewer.

How to connect Second Life to Discord, step by step

1. Open Manage Discord

After signing in, choose Manage Discord from the icon rail on the left (on a phone, under the More tab; see Second Life on mobile). The page header reads "Your in-world presence, in your Discord server", with a Relay off switch in the corner. It only turns on once setup is complete.

2. Find the "Connect your Discord" card

The first card is Connect your Discord. Its hint sums up the method: add the Thunder Viewer bot to your server, then choose the channel it posts to and reads from. The bot both posts your events and listens for replies, so there is no URL to copy around.

3. Add the Thunder Viewer bot to your server

1. Click Add Thunder Viewer to your Discord. Discord's authorization page opens in a new tab.
2. Choose your server and approve, then return to Thunder Viewer.

When the bot has joined, the card changes to a green check and Added to followed by your server's name. Add it to another server repeats the invite.

4. Pick the channel

1. Open the Channel dropdown. It lists the text channels the bot can see, grouped by server, with a search box at the top.
2. If the list says "No channels yet. Add the bot first" even though you just added it, click the circular Refresh channels button beside the dropdown.
3. Choose the channel you created earlier.

A channel already relaying another of your avatars appears greyed out with "Used by" and that avatar's name, so two avatars never post into the same feed by accident.

5. Choose what Discord does

The next card, What Discord does, holds every toggle, with a Search settings box for jumping to one. The two-way options sit at the top, followed by the notifications. The notification feeds:

• Local chat, Group chat, Friend requests and Teleport offers do what they say.
• Direct IMs relays the sender and full message. It carries a Private badge and stays off unless you turn it on.
• Arrivals / leaves posts when avatars enter or leave the region.
• Traffic snapshot posts a periodic avatar count. Switched on, the row reads "Every 15 minutes" with the number editable in place.
• Bot activity mirrors what your AI bot says and does, as an audit trail.

6. Turn on talking back (optional)

Two switches make it a two-way bridge:

• Reply to IMs from Discord: reply to an IM notification in Discord and your avatar sends it as a private IM.
• Speak in local chat from Discord: messages typed in the channel are spoken in-world.

Each depends on its matching feed, and the panel handles that: switch on IM replies with Direct IMs off and it turns Direct IMs on for you, with a notice saying why.

7. Save, then turn the relay on

1. A bar appears at the bottom reading Unsaved changes. Click Save changes. If the button is disabled, the reason is printed right next to it, for example "Pick a Discord channel for the bot to post in."
2. Flip the header switch so it reads Relay on.

8. Test it

IM the avatar from your main account and watch the message appear in Discord. If you enabled replies, answer in Discord and confirm the avatar IMs it back. Then open See the relay activity at the bottom of the page: the log is the fastest way to tell "nothing happened in-world" from "something failed".

Anti-noise setups that work

Running relays for in-world venues taught us one rule: the relay that gets read is the one that posts least. Local chat and arrivals in a busy region can fill a channel faster than anyone can scroll it, and a muted channel catches nothing. Start with the recipe that matches you and add feeds only on request.

A store. Direct IMs plus Reply to IMs from Discord, so customer questions reach staff and get answered from a phone. Add Arrivals / leaves only if the shop is quiet enough that each visitor is news. For busier stores, a Traffic snapshot every 30 to 60 minutes tells you the day's shape without a ping per visitor. More in our Second Life for business guide.

A club or venue. Traffic snapshot at the default 15 minutes during events, Group chat so the in-world group and the Discord server read one conversation, and Speak in local chat from Discord so the host can greet the room from backstage. Leave Local chat relay off on event nights unless someone is assigned to read it.

A personal avatar. Direct IMs, Friend requests and Teleport offers. That is the "someone is trying to reach me" set. Keep the channel private, since IMs arrive in full.

An AI-hosted avatar. Add Bot activity, so you can read exactly what your AI bot told visitors without logging in.

If you run several avatars, set one up the way you like and use Apply this setup to other avatars in the page header instead of repeating the clicks.

Troubleshooting

• "The bot can't post in that channel." The panel shows the fix: open the channel in Discord, click Edit Channel, go to Permissions, add Thunder Viewer, and allow View Channel and Send Messages.
• The channel is missing from the dropdown. The bot can only list channels it can see. Fix the permissions above, then click Refresh channels.
• Save stays disabled. Read the line beside the button. It names exactly what is missing, usually a channel or at least one feed.
• The relay switch refuses to turn on. It says "Finish setting up the relay on Manage Discord first." Save a channel and at least one feed, then try again.
• Events stopped overnight. The relay rides the avatar's session, so it runs exactly as long as the avatar is signed in. For an always-on relay, keep the avatar online 24/7; 24/7 sessions also come back after server restarts with their Discord relay settings restored.

The scripted alternative

The other common route is an in-world LSL relay: a scripted object, often bought on the Second Life Marketplace or written yourself, that you rez on your parcel and point at a Discord webhook with llHTTPRequest. It works, and some residents like owning the script. It relays what happens around where it is rezzed, so it needs land you can build on. The pillar guide compares this and the self-hosted options in full: Discord bot for Second Life.

Looking for a Second Life Discord to join?

Many people searching "Second Life Discord" want a community to join, not a relay to build. Plenty of Second Life communities, stores and creator groups run Discord servers and share invites in group notices, profiles or Marketplace store pages, so ask in the groups you already belong to. This tutorial covers the other direction: connecting your own avatar to a server you run.

FAQ

Do I need to know LSL to connect Second Life to Discord?

No. With Thunder Viewer the relay is configuration only: add the bot, pick a channel, switch on feeds. LSL is only involved if you choose an in-world scripted relay object instead.

Does the relay keep working when I log off?

It runs as long as the avatar's session does. Closing a tab on a normal session ends it shortly after. With a 24/7 stay-online session, the avatar stays in-world with the relay running while your computer is off.

Can staff reply to Second Life from Discord?

Yes. Reply to IMs from Discord turns a reply to an IM notification into a private IM from your avatar, and Speak in local chat from Discord speaks channel messages in-world. Anyone who can post in that channel speaks as your avatar, so restrict it to staff roles.

Which Second Life events can be relayed to Discord?

Local chat, direct IMs, group chat, friend requests, teleport offers, arrivals and leaves, a periodic traffic snapshot, and your AI bot's activity. Each is its own switch.

How do I pause or stop the relay?

Flip the header switch on Manage Discord back to Relay off. Your channel and feed choices stay saved, so turning it on again picks up exactly where you left off. To remove the bot entirely, kick Thunder Viewer from your Discord server like any other member.

Can I use one Discord server for several avatars?

Yes. Each avatar relays into its own channel, the dropdown marks channels another avatar already uses, and Apply this setup to other avatars copies a working configuration across your fleet.

Ready to wire up your own server? Try Thunder Viewer free.