Configs, keys and alts¶

The Configs tab in the menu holds the three things that are about the overlay rather than about a game: your saved setups, the switch that turns it all off, and your API keys.

Saved configs¶

Configs → profiles → save this setup writes every module, setting and keybind to a file.

Each one is an ordinary .json file in a folder the page shows you. Open folder opens it in Explorer, Finder or your file manager; copy path puts the path on your clipboard, for when there is no file manager to open.

To share a setup, press download beside it: a copy goes to your Downloads folder, which opens, ready to send. To use one you were sent, drop it in the configs folder and press load.

The config you loaded or saved last is marked with a line at the left of its row and reads loaded. Change anything it holds (a module on or off, a setting, a keybind) and its row says how many changes are unsaved (point at that line to see which modules), with two buttons in place of download and load: update writes your changes into that config, under the same name, and revert loads the saved version again (press it twice). Nothing is ever written until you press update. If you also share that config, fkdr offers to update the shared copy too: it keeps its code, and if it is on the portal it stays there (or stays off it). The loaded config is remembered when you restart; deleting or renaming its file stops it being tracked.

Loading a config only changes what it mentions

A config written by a different build, or by somebody whose build has a module yours does not, leaves everything it does not describe exactly as it was. It can add to your setup; it cannot quietly reset the parts it never covered.

A config never contains a secret. Your API keys are kept apart from it and your licence key is not in it either, so a config you send a friend cannot carry either of them, however it was written.

Cloud configs¶

Configs → cloud shares a config without sending a file.

Share a saved config: press share beside it. You get a 6-character code, like K7Q2MX, copied to your clipboard. Anyone with fkdr can use it. Press update later to change what the code gives out; the code stays the same.
Get a shared config: paste a code and press get. It lands in your saved configs as "name CODE"; nothing changes until you press load.
Your shared configs lists your codes and how many times each was used. Stop turns a code off.

You can share up to 5 configs at once. A code stays up as long as people keep using it, and is removed after 30 days without use. Chat works too: /fkdr config share, get, shared and unshare (see commands).

Cloud configs carry the same file as download, so they never contain your API keys or licence key.

The config portal¶

Configs → portal lists the configs people have published, with who made each one: their fkdr username, picture and badges, as the Social tab shows them.

Find one: search by name, description, author or code, and sort by top rated, most used or newest. Each card shows the stars, how many people rated it, how many used it, its module count, when it was last updated and whether it is a Classic or an Enhanced config.
Open one to read its description and comments. get saves it to your configs without changing anything; load saves it and applies it at once. Settings it does not mention are left alone.
Rate it with 1 to 5 stars. Click your rating again to clear it. You can't rate your own.
Comment (up to 500 characters). You can delete your own comments, and comments on your own configs. report flags one for review; three reports hide it until it has been reviewed.

Publish your own: on Configs → cloud, press publish beside one of your shared configs, add a short description (optional) and press publish again. You need a username in the Social tab first. unpublish takes it off the portal; its code keeps working, and its ratings and comments come back if you publish it again. Pressing update on the config later updates the published one too.

You can have 3 configs on the portal at once. A published config stays up as long as people keep opening, getting, rating or commenting on it, and is removed after 180 days without any of that. Chat works too: /fkdr config publish <code or name> [description] and /fkdr config unpublish <code or name>.

Turning everything off¶

Configs → profiles → disable all switches off every module at once. They are switched off, not hidden. The HUD goes with them, and nothing talks to the network until you turn it back on.

Pressing it again puts back exactly what was running before, and nothing that was not. It survives a restart, because somebody who switched the overlay off and quit meant it; the overlay says so in chat when the game starts that way.

You can bind a key to it under appearance → panic key, or use /fkdr panic. It is unbound until you choose one, so nobody turns the whole overlay off by accident.

API keys¶

Configs → api keys is the one place every third-party key goes. Each service has its own card: its name with a set or not set chip, what the key powers, where to get one, and the key field. Click a sign-up link on a card to copy it.

service	what it powers	where to get one
Hypixel	stats come from your own key instead of the shared stats service, so lookups never wait behind other players, and anti-sniper trackers refresh every 20s instead of every 60s. From developer.hypixel.net	developer.hypixel.net
Urchin / Coral	marks accounts on the Urchin blacklist, and adds them to a Tags search. Urchin's API is now called Coral; it is one service and one key	`/dashboard` with the Urchin Discord bot
Aurora	the number denicker in the Anti-sniper tab; winstreak estimates and ping work without it	add the Aurora app with Discord (`discord.com/oauth2/authorize?client_id=1244205279697174539`), then run `/api view` to get your key

A free Hypixel key expires 3 days after you make it. The Hypixel card shows the time left, for example set | expires in 2d 14h. It turns amber in the last 12 hours and red once the key has expired, with a link to developer.hypixel.net. Chat reminds you once when under 12 hours are left and once when it has expired. Pasting a new key starts the timer again. If Hypixel says the key is invalid, it is shown as expired straight away.

Keys are masked until you press edit, because people screenshot this menu to show each other their settings. They are kept on your computer and are never part of a shared config. Each key is sent only to its own service, apart from the Aurora relay when Aurora cannot be reached directly.

The account switcher¶

Press Alts on the multiplayer server list (beside Cancel) or run /fkdr alts.

The switcher is drawn like the menu, so it follows your theme, preset, accent animation and font; a theme picked a moment ago shows there straight away.

Four ways to add an account:

Microsoft: the usual one. It gives you a short code to type at the link in your own browser, on any device. You enter your password, second factor and consent with Microsoft; the overlay never sees any of it.
Refresh token: a Microsoft refresh token exported from another launcher.
Cookie: a Microsoft login cookie, a cookies.txt export or an M.C token, pasted in or loaded from a file. It is exchanged once and discarded.
Offline: a name only. It cannot join an online server, and the row says so.

Switch with one click. An account whose session has gone stale signs itself back in first, which is what the saved refresh token is for. Switch before connecting: changing who the client authenticates as while you are on a server does not tell that server anything.

What is on disk

A refresh token is the account. Saved accounts stay on your computer, never leave it, and nothing else in the overlay reads them. Any program running as you could read them, though, so only add accounts on a computer you trust.

Remove an account and the token goes with it. Removing it here does not sign it out anywhere else; to do that, revoke the app in your Microsoft account security settings.

Back to the account you launched with¶

The first row is the account your launcher signed the game in as, marked launcher, with restore beside it (or playing, when that is who you are now). Restoring is the session the launcher already gave the game: no sign-in, no refresh token, nothing is fetched, and it works whether or not that account is in the list below. /fkdr alts restore does the same thing without opening the screen.

It lasts for as long as the game is running. The launcher hands the game one session at startup and there is no way to ask for another, so if it could not be read at startup the row says so instead of offering a button that would do nothing. Restarting the game is then the way back.

Also on the server list¶

fkdr beside it opens the overlay's own menu over the server list, so you can read your friends list, message people and search tags before you pick a server. Closing it puts you back on the list.

Notification cards show over menus too, so a message reaches you while you are still deciding what to play.