Skip to content

SHARING.md

Latest commit

 

History

History
156 lines (108 loc) · 5.39 KB

SHARING.md

File metadata and controls

156 lines (108 loc) · 5.39 KB
Raw

Giving it to a friend

Send them two things: the Vencord download page, and one command.

1. Install Vencord

https://vencord.dev/download/ — download, run it, click Install. Start Discord and check there's a Vencord section in Settings.

2. Paste one command

Windows — Start menu, type cmd, press enter, paste this:

powershell -c "irm https://raw.githubusercontent.com/destination/mediatab/main/get.ps1 | iex"

macOS — Spotlight (Cmd+Space), type Terminal, press enter, paste this:

curl -fsSL https://raw.githubusercontent.com/destination/mediatab/main/get.sh | bash

Then wait a couple of minutes. It installs whatever's missing (Git, Node.js on Windows via winget), downloads MediaTab, builds it against the latest Vencord, closes Discord and hooks it up.

3. Switch it on

Open Discord → Settings → Vencord → Plugins → search MediaTab → toggle it on → press Ctrl+R.

That's it. To update later, they run the same command again.

Why there's a build step at all

There's no way around it — Vencord compiles plugins into its bundle, so there's no file to drop in. See VENCORD-PLUGINS.md for why. The one-command installer just hides the build behind a single paste.

What they need

The installer handles most of this itself:
Vencord Must be installed first — the installer won't do this, and tells them so with a link
Node.js 22+ Auto-installed on Windows via winget; on macOS via Homebrew if present, otherwise it links to nodejs.org
git Same

Works on macOS, Windows and Linux.

If they'd rather not paste a command

Do it by hand

git clone https://github.com/destination/mediatab.git
cd mediatab
./scripts/setup.sh
# quit Discord completely, then:
./scripts/install.sh

Exactly what the one-liner does, just visible.

No git at all

Point them at https://github.com/destination/mediatab/releases/latest, have them download Source code (zip), unzip it, and run the two scripts from inside the folder. They'll still need Node and git installed, because setup.sh clones Vencord itself.

Not recommended — sending a built dist/

You could zip Vencord/dist/ and have them drop it into their Vencord data folder, skipping the build entirely. It would work.

Don't do this, and don't accept it from anyone else. "Replace your Discord client code with this bundle I sent you" is exactly the shape of every Discord token stealer. Your friend cannot read a minified 700KB bundle to check what's in it. Building from source means they run code they can actually inspect, from a Vencord checkout they cloned themselves. Keep that property.

The one-command installer keeps that property too: get.sh and get.ps1 are short enough to read in a minute, and they only ever fetch code from this public repo and from Vencord's own.

What the scripts do on their machine

install.sh finds their Vencord data folder automatically:

Platform Location
macOS ~/Library/Application Support/Vencord
Linux ~/.config/Vencord (or $XDG_CONFIG_HOME/Vencord)
Windows %APPDATA%\Vencord

If they have an unusual install — Vesktop, flatpak, portable — they can point at it directly:

VENCORD_DIR="/path/to/Vencord" ./scripts/install.sh

It then symlinks that folder's dist/ at the build in their clone. Their Discord app bundle is never modified, their stock Vencord build is moved aside rather than deleted, and their settings are backed up first. Fully reversible with ./scripts/uninstall.sh.

On Windows without Developer Mode, symlinks aren't allowed, so the script copies the build instead and tells them to re-run it after each rebuild.

Things to tell them

It's a ToS thing. Client mods are against Discord's Terms of Service, though nobody gets banned for using them. Point them at RULES-AND-RISK.md — it's the honest version, including why "undetectable" isn't something anyone can promise.

Updating is the same command. Vencord's own updater gets turned off, because it replaces dist/ with a downloaded release and would wipe the plugin out. Re-running the one-liner pulls the latest MediaTab and the latest Vencord and rebuilds both, so tell them: if something looks broken, paste the command again.

Don't screenshot it in servers that ban client mods. The Media browser is visibly not stock Discord.

If the header button goes missing after a Discord update, that's the patch. Right-click a channel → View Media still works, and MAINTENANCE.md explains the fix — which is usually a one-line regex change, with tests that tell you when it's right.

If they hit trouble

Symptom Fix
Could not find a Vencord install They haven't installed Vencord yet, or it's in a custom location — use VENCORD_DIR=...
Discord is still running Closing the window isn't quitting. macOS Cmd+Q; Windows/Linux quit from the tray icon
node >= 22 required Update Node from nodejs.org
Plugin isn't in the list The build didn't include it — re-run ./scripts/setup.sh and check for errors
Plugin is listed but no button They enabled it but didn't reload. Ctrl+R / Cmd+R
Everything looks right, still nothing DevTools console, look for Patch by MediaTab. See MAINTENANCE.md