Blog

How to run a proper movie night in Discord, end to end

Connect the Plex library you already run to your Discord, start a room, and let everyone watch together — with attendance, resume points and a wrap-up. The full setup.

2026-09-06

You can screen-share a film in Discord in about ten seconds. Doing it well — so people can join late, so nobody has to ask "who's still watching", so the host isn't pinned to their desk — takes one afternoon of setup and then never needs touching again.

This is that afternoon, in order.

What you need

  • A machine that stays on. A spare PC, a NAS, a mini-PC under the TV. It does not need to be fast; it needs to be awake.
  • Plex on it. It is free for everything this needs, and it is the media server Asbern connects to.
  • The bot in your Discord, with the Server Manager role or Administrator.

That is the whole list. There is no hosting to buy — the library stays on your hardware and streams from there, which is exactly why nobody sells this as a service. Asbern is the link between your Plex and your Discord; it supplies no media of its own.

Step 1 — get the media server running

Install Plex, point it at the folder your films are in, and let it finish scanning. Watch one thing in the Plex web player before going any further. If it will not play there, no amount of Discord setup will help, and you will spend an hour looking in the wrong place.

⚠ Give the machine a static IP or a reserved DHCP lease. A media server that changes address every few weeks is the single most common reason a working setup stops working.

Step 2 — pair it with the bot

In Discord: /menu → More → Admin → Media → Host.

The console walks you through it in six steps and each one checks itself before moving on, so you find out immediately rather than at movie time:

  1. Where it is — the address of the machine.
  2. The token — Plex's own authentication, which the wizard tells you where to find.
  3. Which libraries — you can expose only the ones you want; a "Home Videos" library does not have to be visible to your server.
  4. A test fetch — the bot asks for the library listing and shows you what came back.
  5. A test stream — the part that actually matters, because a server that lists happily can still fail to transcode.
  6. Confirm.

The pairing code is shown once and is ephemeral. If you lose it, run the wizard again — it is idempotent and re-pairing costs nothing.

Step 3 — pick the room

A screening happens in a voice channel plus a card. Choose the voice channel you already use; there is no need to make a new one.

If you want a dedicated cinema category, the bot will build it for you — channels, permissions and all — from Admin → Categories, and it can unbind it later without deleting anything.

Step 4 — start something

/menu → Watch. Browse the library, or search it, and press play.

What happens then is the part that is different from screen sharing:

  • A card posts to the channel with the title, the artwork, who started it, and a Watch button.
  • Anyone who presses Watch gets their own link. They are not watching the host's screen; they are watching the stream, so the host can close their laptop.
  • Late arrivals get a resume point. The card knows where the film is up to.
  • Attendance is measured from the stream itself, per segment — not from who is sitting in the voice channel with the tab closed.

Step 5 — the wrap-up

When it ends the bot posts a wrap: who watched, how long each person actually watched, and what is next in the series if it was an episode. Watch time counts toward levels and pays into the economy the same way messages and voice do, so a film night is worth something to the people who turn up.

Live TV, if you have it

If you also run Threadfin (or anything that serves an M3U and an EPG to Plex), its channels appear as a browsable guide inside Discord — filter by category, page through it, and start a room on a channel exactly like starting one on a film. Sport is the obvious use, and it is the one people set up second.

Binge mode

For a series, the bot will advance to the next episode on its own when one finishes, and stop when the room empties. It resolves an unknown room state as "keep going" deliberately: refusing there visibly ends somebody's evening, while advancing to an empty room just plays to nobody.

Things worth knowing before your first night

  • Test the stream once, on the day, from a phone on mobile data. That is the path with the least margin, and it is the one that finds a firewall problem while you still have time.
  • Transcoding is where old hardware struggles, not streaming. If a film stutters for everyone at once, look at the media server's CPU before blaming the network.
  • The bot does not need to be on the same machine as the media server, but it does need to be able to reach it.

Why it is set up this way

Discord's own screen share is peer-to-peer from the host: their upload is the ceiling for everyone, and their machine has to stay open. Streaming from a media server moves that load to a machine whose job it is, which is why the same eight people who could not hold a stable 720p can watch 1080p without anyone thinking about it.

The full reference, including turning it off again, is in the media server guide.


More posts