Frequently asked questions

Yes. There is no paid plan, no limit on staff, and no ads. It is in beta and we plan to keep it free.

Sign in with Discord on the dashboard, add the bot to your Discord server, then paste your ER:LC server key into the box on your server's card. You find the key in your private server's settings, in the API section. Uplink checks it with ER:LC before saving it, and stores it encrypted.

There are three levels. Helpers can look at everything, warn, leave notes and clock in to shifts. Moderators can also kick, ban, jail, use the watchlist and announce in the game. Admins can change settings and keys. The server owner and anyone with Manage Server are admins. Admins pick the three roles in Settings or with /setup.

Yes, for Windows and macOS. Get it from the Download page. It is the Uplink website in its own window: press Sign in, sign in with Discord in your browser, and the app opens on your dashboard. It is not code-signed yet, so your computer warns you the first time you open it.

That is a setting on the Discord application, not on your server. The Add Uplink button on the dashboard works either way, because it asks Discord to send you back to Uplink afterwards. If you are using a different invite link and see this, whoever owns the Uplink application opens the Discord developer portal, goes to the Bot page, and turns off "Requires OAuth2 Code Grant". Also make sure Public Bot is on, so people other than the owner can add it.

The key was copied wrong, or it was regenerated in ER:LC and the old one stopped working. Copy it again from your private server settings and paste it in the server's Settings page. If you changed Uplink's own secrets (self-hosted), saved keys cannot be read any more and need pasting again.

ER:LC only answers while someone is in the private server. Uplink keeps checking and starts as soon as a player joins. Press "Check connection" on the Overview page to see exactly what ER:LC says.

ER:LC lets an unregistered app talk to one server only. The person running Uplink has to register it as an ER:LC public application, after which any number of servers can connect.

Uplink reads the commands ER:LC records and saves a case with the player, the staff member and the reason you typed after the name. ER:LC has no :warn command of its own, so a plain :warn is never recorded. To log a warning from the game, type :log warn Name reason (or :log note Name text), which ER:LC writes into its command log. Open Overview and press "Check connection": it lists the last commands ER:LC reported. If your command is not in that list, ER:LC did not record it, so Uplink never saw it. If it is there but no case appeared, check that "Log in-game moderation commands as cases" is on in Settings, and look for an alert about a name Uplink could not match.

ER:LC does not let an app read its own ban list, so Uplink keeps one. Bans made in Uplink, or typed as :ban in the game, go on it, and anyone on it is kicked the moment they join. You can switch that off in Settings.

Yes to both. Choose how long a ban lasts when you make it (or /case ban days:7), and Uplink lifts it when the time is up. In Settings an admin can also pick how many active warnings within how many days trigger a kick, a temporary ban or a ban. Those cases are made by "Uplink (automatic)".

The Map page shows everyone in the server as a dot on the ER:LC map, live. Helpers can look people up and warn them from it. Moderators can also kick, jail, ban, message and teleport. "Go to them" and "Bring them to me" use the Roblox account you linked, because ER:LC teleports one named player to another, so you need to be in the server too.

Reading your server works with the key, but ER:LC only lets an app send commands (kick, ban, messages, teleports) after the owner of the private server approves it once. In the server's Settings, under the ER:LC connection, there is a link. The owner opens it while signed in to Roblox and approves it. Cases still save while you wait; only the part in the game is refused. Press "Test sending a command" under Check connection afterwards. The full steps are in the docs under "Approving Uplink to run commands".

The Roblox account that owns the ER:LC private server. That is often not the person who runs the Discord server, so a Discord admin may need to copy the link from Settings (there is a button that copies a ready-made message) and send it to the owner. The link is safe to share, since all it does is let the owner approve Uplink. Each private server has its own link, and each only needs approving once.

In the server's Settings, press "Set up channels for me". Uplink makes a private Uplink category with a channel for mod calls, cases, joins, kills, commands, alerts and shifts, and links them. It needs the Manage Channels permission. You can also pick your own channels there, or use /setup.

Staff press "Start shift" on the Shifts page (or run /shift start) and "End shift" when they finish. Uplink totals the time per person for the last 7, 14 or 30 days. Separately it shows the time each person had a staff rank in the ER:LC server. A shift someone forgets to end counts for at most 16 hours.

Yes. An admin opens the Import page on the dashboard, pastes a Melonly API token (Melonly, then Settings, Panel, Server API Tokens), and checks what Uplink found. Choose what each Melonly log type becomes, then import. Cases keep their original dates, active bans go on the ban list, and nothing is sent to the game. Uplink does not keep the token, a log is never imported twice, and you can remove an import if it came out wrong.

The Activity page counts the larger of the time a person had a staff rank in the game and the time they clocked in. An admin sets how many hours are enough over 7, 14 or 30 days. To be away, ask for leave on the Leave page or with /loa request. While it is approved you are not marked below the quota.

Staff applications are on the Forms page: an admin opens the form and shares its link, people sign in with Discord to fill it in, and the Uplink bot sends them the answer. Ban appeals have their own page under Moderation with a public link per server. Players enter their case number and Roblox username, staff see the ban case next to the appeal, and accepting it lifts the ban.

It posts in the alerts channel, pings the moderator role and shows where you are in the game. You can ask once every five minutes. You can also run /backup.

Moderators press Start a session on the Sessions page, or run /session start. Uplink posts the announcement with the join code in the sessions channel set in Settings, and posts a summary when you end it.

Verify with Bloxlink first (on its website, or with its bot in your server). Then open the Link Roblox page on the site and press "Check my link", or run /link in Discord. Uplink asks Bloxlink which Roblox account your Discord account belongs to. Uplink never sees a Roblox password.

Bloxlink keys belong to one Discord server and only work for members of it, with the Bloxlink bot in that server. Copy the key from your server's page in the Bloxlink dashboard and paste it in your server's Settings, under "Bloxlink key". Uplink checks it before saving. It is optional: everything except Discord-to-Roblox name lookups works without it.

Your server key (encrypted), 14 days of logs, player counts for 7 days, and the cases, bans, watchlist and shift times your staff create. "Disconnect" in Settings deletes the saved key, and "Delete all data" erases everything for the server. Removing the bot also deletes the key. The privacy page has the full list.

Open a ticket in the support server and pick API Issue, Bug report or General Inquiry. For quick things, the /faq command in the support server has these same answers. You can also email support@uplinkrblx.xyz, and the status page shows whether Uplink is up.