Legal
Terms of Service
Please read these Terms before you play. They explain what the Launcher changes on your computer, which hardware identifiers it stores on your computer and sends to the Server, how bans and reviews of new accounts work, and the rules you agree to follow. The launcher shows this document on first run and asks you to accept it; the current version is always published here.
1. About these Terms
Daedric Online is a community-run, free-to-play roleplay server for The Elder Scrolls V: Skyrim Special Edition, operated by its administrator ("Daedric Online", "we", "us", "our"). These Terms of Service ("the Terms") are an agreement between you and Daedric Online.
The Terms cover everything we provide ("the Service"): the Daedric Online launcher ("the Launcher"), the client files it installs into your Skyrim installation ("the Client"), the game server and the proximity-voice server ("the Server"), our Discord community, and the website at daedriconline.com.
By pressing I agree in the Launcher, or by connecting to the Server, you accept the Terms. If you do not accept them, do not use the Service. You can stop using the Service at any time by closing the Launcher; Revert to Vanilla in its Settings removes most of what we installed, and section 4 lists what it does not undo.
Two other documents apply alongside the Terms. Our Privacy Notice explains what information we collect and how we use it. The server rules posted in the #rules channel of our Discord are part of the Terms; where the rules are more specific than the Terms, the rules apply.
2. Who can play
- You must be at least 18 years old. The Service is written for adults, and Skyrim itself is rated for mature audiences.
- You must own a genuine copy of The Elder Scrolls V: Skyrim Special Edition, with the free Anniversary Edition content installed, on the game version the Launcher checks for. We do not provide the game.
- You must have a Discord account, be a member of the Daedric Online Discord, and link that account in the Launcher. We may decline to link Discord accounts that were created very recently.
- You must link, in the Launcher, the Steam account that owns Skyrim Special Edition. Each Steam account can be linked to only one Daedric Online account. If you play a copy from another store (for example GOG, Game Pass or Epic) or through Steam Family Sharing, open a ticket in our Discord and staff can exempt your account from this requirement.
- You must not have been banned from the Service, under this account or any other, or with the Steam account you link.
The Service depends on other companies' products, and you must also comply with their terms: Bethesda Softworks and ZeniMax Media for Skyrim, Steam or the store you bought the game from, Discord, Nexus Mods for the mod collection, and Patreon if you choose to support us. We are not affiliated with, endorsed by or sponsored by any of them.
3. Your account
Linking Discord sends you to Discord's own login page and asks only for the identify permission: your Discord user ID, username, display name and avatar. The Launcher never sees your Discord password. Discord's page sends a one-time code back, through your web browser, to a temporary listener on your own PC, which stays open for up to two minutes. The Launcher exchanges that code with Discord for a sign-in token limited to that permission and passes the token to the Server, which uses it once to ask Discord who you are and does not store it. The Server stores your user ID and display name, remembers the installation identifier you linked from, and issues you a player number. The installation identifier is a random value the Launcher generates on your PC; the Server also uses it to recognise the installation, and to authorise the voice connection when the Server has not issued a voice pass (see section 4). The Launcher makes a new one when you press Log out, and when the Server asks for it to be renewed, in which case it asks you to sign in with Discord once more. It keeps the installation identifier and any session token encrypted with Windows' own protection for your Windows user, where your PC supports it.
Linking Steam sends you to Steam's own sign-in page in your web browser. The Launcher never sees your Steam password. Steam sends a signed confirmation of your Steam ID back, through your browser, to a temporary listener on your own PC, which stays open for up to two minutes, and the Launcher passes it to the Server. The Server checks that confirmation with Steam, then asks Steam's public Web API whether that Steam account owns Skyrim Special Edition, how old the account is, whether its game details are visible and whether it has VAC bans. For the ownership check your Steam Game details must be public while you link; you can make them private again afterwards. The Server stores your Steam ID (a public number), the age of the account in days and the yes or no answers to those questions, and nothing else from Steam. The Launcher stores none of it.
- You are responsible for everything done through your account. Keep your Discord account secure. Staff will never ask you for your password.
- Use your own Discord account. Several people may play from one PC, but each person must link their own account: Log out in the Launcher switches accounts, and each account has its own characters.
- Link your own Steam account. A Steam account that is banned from the Service blocks every Daedric Online account linked to it, and cannot be linked again.
- Do not create or use additional accounts to evade a ban, to hold more characters than you are allowed, or to gain an advantage. Playing from a PC or a network that someone else also plays from is allowed; our tools flag accounts that share a machine or an address, and staff may ask you about it.
- Accounts, characters and player numbers are personal. You may not sell, buy, rent, give away or otherwise transfer them.
4. What the Launcher does on your computer
The Launcher is an installer, an updater and a launcher for a heavily modded game. Because it changes files inside your Skyrim installation, you should know exactly what it does before you use it. It:
- Finds your Skyrim installation by reading Steam's registry entries and library files, or uses the folder you set in Settings.
- Downloads our client files from the Server, installs them into the Skyrim folder, and checks them again each time you press Play. The list of those files, the Launcher's own updates and the optional crash watchdog are accepted only when they carry our digital signature; without it the Launcher installs nothing and tells you why. A file of ours that is missing or has changed is downloaded again, replacing the changed copy. The game plugins (.esp, .esm and .esl files), the SkyrimPlatform scripts in Data\Platform\Plugins (.js files), the Skyrim Script Extender files and script extender plugin DLLs that we ship, and SkyrimPlatform's core DLL, are compared by their SHA-256 hash on every check, so an edited copy is replaced even when its size has not changed. Our other files, including the game scripts (.pex files) and the other program files we ship, are compared by size, and also by hash when the Server publishes a new version of the client files and when you run Verify with Skyrim closed. If the Server cannot be reached, Play skips this check. The first time one of our files replaces a file that was already there, the Launcher keeps a copy of that file in a DaedricData folder inside the game folder. If the file being replaced is read-only and is also stored under another name (for example a copy Vortex keeps), the Launcher moves it to DaedricData\quarantine instead of changing it.
- Replaces the game's plugin load order (Plugins.txt, in your AppData folder) with the Daedric Online load order each time you press Play, and when you run Verify with Skyrim closed. The first time, it keeps a copy of the load order you had.
- Writes a client settings file (Data\Platform\Plugins\skymp5-client-settings.txt) each time you press Play. It holds your player number, any session token the Server has issued to you, the Server's address and port, your voice and key-bind settings, the in-game diagnostics and profiling options from the Launcher's settings, and a random code, new on each launch, that the game uses to recognise the Launcher's voice messages. These values replace any the file already had. Other settings already in the file are kept, except two that switch off parts of the Server's checks on your PC (blockedEventSources and ignoreLoadOrderMismatch): the Launcher removes them, and writes blockedEventSources back as an empty list.
- Moves aside files that would break the build. Another server's launcher folder and a short list of files known to crash the game are moved to DaedricData\quarantine, with a record of where each one came from. SkyrimPlatform scripts we did not ship are moved from Data\Platform\Plugins to Data\Platform\PluginsNoLoad, and the Launcher shows you their names. Plugin files of your own that are not part of the collection (any .esm or .esl file, and a .esp file that is switched on in Plugins.txt, or every one of them when Plugins.txt is missing or cannot be read), together with their .bsa archives, are moved to DaedricData\quarantine, with the same record, only if you agree when the Launcher asks. Other files those mods installed stay where they are. These moves, and the mod file repair described below, keep every file they take out of place. The one exception is in the repair: when the file in the Data folder is only a hardlink to the copy Vortex keeps, the repair may remove that link instead of moving it, and Vortex's copy stays where it is.
- Sets SkyrimPlatform to load scripts only from our client's folder. Each time you press Play, and when you run Verify with Skyrim closed, it sets the PluginFolders line in Data\SKSE\Plugins\SkyrimPlatform.ini to Data/Platform/Plugins, and moves any script or settings file in Data\Platform\PluginsDev to Data\Platform\PluginsNoLoad\Dev. Before it changes that line, it copies the old file next to it; it keeps the five newest copies and deletes older ones. If the file is missing, it creates it with SkyrimPlatform's standard settings and that line. In the same file, when the BackendName line in the [Browser] section names a browser that cannot show our menus (for example nirnlab, which draws through the NirnLab UI Plugin, or off), it sets that line to auto, SkyrimPlatform's own browser.
- Rebuilds the files RaceMenu needs outside its archive (its character-creation menu and its translation files). When RaceMenu.bsa is in the Data folder and the Launcher has no record of those files, or they are missing or differ from its record, it extracts them from that archive into Data\interface, replacing any file already at those paths without keeping a copy, and records them in the DaedricData folder. This happens when the Launcher starts (once you have accepted these Terms), each time you press Play, and when you run Verify, even while Skyrim is running.
- Checks the mod files that the Daedric Online collection installs through Vortex against the exact revision of the collection this Launcher is pinned to, and names the mod behind any file that does not match. When the Launcher sees no game running, it may repair such a file using only copies already on your PC: it links the file to the matching copy Vortex already keeps in its mod staging folder (a hardlink, as Vortex's own deployment makes), or it extracts that one file from the matching mod archive already in your Vortex downloads folder, after checking that the archive's size and MD5 checksum are those of the pinned Nexus Mods file and that the extracted file's SHA-256 hash matches. The file it replaces is moved to DaedricData\quarantine inside the game folder. It keeps a record of the archive checksums it has computed in the DaedricData folder, so that an archive is not read twice. In doing this the Launcher never writes inside Vortex's own folders, never downloads files from Nexus Mods and makes no request to the Nexus Mods API. A file it cannot repair this way is listed for you, with the step to take in Vortex or on the Nexus Mods website.
- Checks Skyrim's own plugin files (Skyrim.esm, Update.esm, Dawnguard.esm, HearthFires.esm, Dragonborn.esm, the four Creation Club plugins the game loads by itself and _ResourcePack.esl) by their SHA-256 hash against the files of Skyrim 1.6.1170 each time you press Play and when you run Verify. A file that has the size of a later official Steam release of Skyrim, or the size of a known official variant, is checked by size only, and its name and size go into the build report the Launcher sends to the Server. Any other file that does not match stops Play. When the Launcher sees no game running and a Skyrim 1.6.1170 download that Steam's download_depot command already put on your PC holds the matching file, it checks that file's SHA-256 hash and copies it into the Data folder, moving the file it replaces to DaedricData\quarantine; it only reads Steam's download folder. Otherwise the message offers to put the Steam command that downloads the file on your clipboard and to open Steam's console, as the guided downgrade does.
- To tell which mod a file belongs to and how to repair it, reads, without changing them, Vortex's deployment records in the game folder, its mod staging folder (including the collection.json files that show which collection revision is installed), its download folders, and the Windows registry entry that says which program opens nxm:// links. To find download folders you have moved, it lists the folder that holds the staging folder and the folder above that, looking for folders Vortex has marked as download folders. None of these folder locations is sent to the Server.
- When you press a button that asks for it, opens the Daedric Online collection in Vortex at the exact revision this Launcher is pinned to, or opens a mod file's page on the Nexus Mods website in your web browser. If Vortex is not the program that opens nxm:// links on your PC, the collection's page opens in your browser instead. If the Server names a newer revision of the collection, the collection buttons on the Launcher's main screen open the page the Server gives for that revision in your browser instead; the buttons shown when Play cannot go ahead, and those in Verify, still use the pinned revision. The Launcher hands Vortex no nxm:// link except one for the Daedric Online collection, and it does not register itself as the program that opens nxm:// links. When Creation Club files are missing, the message that stops Play and the matching row in Verify tell you how to get them back from your store. On Steam only, they also offer a Verify in Steam button that opens Steam's own check of Skyrim's files. That check re-downloads every game file that does not match the version your store offers today, so if the Launcher has downgraded your game it puts the newer version back, and you have to run the downgrade again before you can play.
- Puts back stock game files that another server's launcher moved into a folder inside Data, and removes that folder once it is empty if it is one the Launcher recognises.
- Deletes Skyrim's Creation Club catalogue file (ContentCatalog.txt, in your AppData folder) each time you press Play and each time you run Verify (Verify does this even while Skyrim is running), because an out-of-date copy can crash the game; Skyrim builds a new one from the content actually installed. The Launcher keeps one copy of the last file it deleted in the DaedricData folder, and replaces that copy each time.
- Checks the game version. If Steam has updated Skyrim past the version we support, the Launcher offers a guided downgrade: you enter the download commands in Steam's own console (the Launcher can open the console and put each command on your clipboard), and the Launcher checks that the downloaded files are the right build and copies them over the game's files. It keeps copies of the game's executable and a few other small files from the main game folder that it replaces; Steam's Verify integrity of game files puts back the rest. The Launcher never asks for or handles your Steam login.
- Offers, in Settings, a recommended graphics profile. It edits SkyrimPrefs.ini only when you apply it, keeps a copy of the original file the first time, and has a button that puts that copy back.
- Has an Enable Community Shaders switch, above Play and in Settings, which is off until you turn it on. While it is off, each Play renames Data\SKSE\Plugins\CommunityShaders.dll to CommunityShaders.dll.disabled so that it does not load, first deleting an older CommunityShaders.dll.disabled if there is one; while it is on, Play renames that file back. Rebuild Community Shaders in Settings deletes the compiled shader cache (Data\ShaderCache), which is built again the next time the game starts.
- Starts the game through the Skyrim Script Extender and checks every few seconds whether it is still running. While it runs, the STOP button force-closes every running SkyrimSE.exe process, without letting the game shut down normally.
- Hosts proximity voice. Pressing Play opens your microphone and contacts the voice server, using the voice pass the Server gave the Launcher when you last signed in (it is valid for 12 hours, works only for voice, and is kept in the Launcher's AppData folder), or your installation identifier when there is no current pass, before the Launcher has finished its checks. It happens even when a check then stops the launch, for example an unsupported game version, missing mod files, the question about plugin files of your own, missing Creation Club files, a server it cannot reach, or a sign-in it cannot complete; when the launch stops that way, the microphone is closed again. The Launcher also opens it whenever else it finds Skyrim running: when the Launcher starts, or you accept these Terms, while Skyrim is already open, and when any copy of Skyrim, including one you started yourself, is running within about five minutes after a game the Launcher was watching has closed or failed to start. Once open, it stays open until the Launcher sees that the game has closed. It sends audio only while you hold the push-to-talk key in Daedric Online; the voice server relays that audio to players near you in the world. The voice section of Settings also opens the microphone briefly to list your devices, and while you run its microphone test, which plays your voice back to you on your PC only.
- Keeps itself up to date. A few seconds after it starts, before you have answered these Terms, then every 30 minutes and whenever our server announces a new version, it asks our server for the latest Launcher version. Each of these requests carries a random update identifier that the update component creates and keeps in the Launcher's AppData folder. The Launcher downloads a new version in the background and installs it when you restart or close the Launcher, including when you close it without accepting these Terms.
- Checks the state of your installation from the moment it starts, also before you have answered these Terms. It asks our server for its status every 15 seconds, keeps a request open to our server so that it hears about new versions at once, and fetches our news, our list of client files and the collection revision the Server uses. It compares the client files already on your PC with that list every few minutes (more often while our server cannot be reached), reads your Data folder every few seconds, and reads Vortex's records, to show the state of your client files and mods. None of this changes a file in your Skyrim folder or sends an identifier.
- If a Daedric Online admin asks you to help diagnose a crash, you can turn on the crash watchdog in Settings. It downloads a small debugging tool from our server, attaches it to Skyrim, and writes full memory dumps of the game to your AppData folder when the game freezes or crashes. Each time it starts, it deletes older dumps and keeps the two newest. The dumps stay on your PC unless you choose to send them to us; they can contain anything the game had in memory at the time.
- Stores its own settings, logs and diagnostics under your Windows user profile (AppData).
- Stores the install marker the Server gives it, as small visible files in up to six folders on your PC. Section 5 says what the marker is, where the files are and what happens to them when you uninstall.
- Has a Disable Daedric client button beside Play (Settings explains it under Play other servers / singleplayer), so the same Skyrim installation can run singleplayer or on another server. When the Launcher sees no game running, it moves our client files and the client settings file into the DaedricData folder, except the files in the main game folder (the script extender and its preloader) and the Address Library files. It puts back the files our client files had replaced, from the copies the Launcher kept, and each file in DaedricData\quarantine whose original place is empty, including files known to crash the game and another server's launcher folder. It puts back your own load order (Plugins.txt), or deletes Plugins.txt if the Launcher kept no copy of it. Restore Daedric client, or Play while the client is disabled, moves our files back. Before it does, it deletes any other file at one of those paths without keeping a copy, except a read-only file that is also stored under another name (for example a copy Vortex keeps), which it moves to DaedricData\quarantine.
- Revert to Vanilla runs only when the Launcher sees no game running. It deletes our client files, the collection's mod files that it can identify in the Data folder (including those Vortex installed), the client settings file and the DaedricData folder. It puts back, from the copies the Launcher kept, the files our client files had replaced (this can be a mod's own version of a file we ship, which then stays in Data), your load order (Plugins.txt) and SkyrimPrefs.ini; if it kept no copy of Plugins.txt, it deletes Plugins.txt and Skyrim creates a new one. It puts back each file in DaedricData\quarantine whose original place is empty at that moment, except the files the Launcher moved there to make room for our client files or for a repaired mod file; those are deleted with the DaedricData folder. A mod file the Launcher repaired is deleted like any other mod file. None of these steps deletes or replaces a file that is read-only and also stored under another name (for example a link to the copy Vortex keeps): Revert leaves such a file where it is and lists it. Removing the collection in Vortex removes those in the Data folder; after that, running Revert again deletes those that were moved to DaedricData to make room. Revert to Vanilla does not undo the other changes described in this section: the SkyrimPlatform.ini change (the copies of that file stay beside it), the scripts moved to Data\Platform\PluginsNoLoad, the stock game files put back into Data, the Creation Club catalogue, or a downgrade. It changes nothing in Vortex's own folders, so remove the collection in Vortex as well, or Vortex will deploy its mods again.
- Reset Deployed Mods, in Settings under Uninstall, is a separate permanent reset. After you confirm the game folder and acknowledge the warning, it deletes every file outside a static base-game path list in that folder, including personal mods, SKSE, ENB, tool output, extra Creation Club content, other language files, and DaedricData including backups. It preserves the listed Steam base-game files and the Creations, Data.backup and Skyrim folders. It does not repair modified or missing base-game files or restore backups. There is no undo. It refuses a linked game or Data folder, leaves other linked paths untouched, and leaves read-only files that also have another name (such as Vortex hardlinks). It reports paths it could not remove. Saves outside the selected game folder are untouched. Close Skyrim and mod tools first (Vortex or other mod managers or anything Skyrim related).
Three of the steps above run only when the Launcher sees no game running: Revert to Vanilla, Disable Daedric client and the repair of a mod file. That is the Launcher's own view of the game, not your computer's. It watches the game it starts, a game that is already open when it starts, and any game running for about five minutes after a game it was watching has closed. A Skyrim you start at any other time is invisible to it, and these steps will go ahead while that game is open. Close Skyrim yourself before you use them: a file the game has open cannot be replaced reliably. Verify checks for a running game itself, so it is not affected.
The Launcher does not change Windows settings, security or firewall settings, your Steam settings or your audio device levels, and it does not keep running in the background after you close it, beyond finishing an update it has already downloaded. Some antivirus products flag the crash-watchdog tool, and occasionally the Launcher itself, because attaching a debugger to a game looks like malware behaviour; the Launcher never disables or reconfigures your antivirus.
5. Hardware identification, bans and alternate accounts
To keep banned players out and to detect alternate accounts, the Launcher identifies the computer it runs on. The first time you press Play after the Launcher starts, it reads the following values from Windows:
- the motherboard's SMBIOS UUID and serial number, and the BIOS serial number;
- the serial number of one physical disk;
- the hardware address (MAC) of one physical network adapter;
- the Windows installation identifier (MachineGuid) and the Windows hardware-configuration identifier;
- and, when the computer's manufacturer and model name match a known virtual-machine product, that name.
The Launcher keeps what it read until you close it. It reads the values again at a later Play only if the first reading found none of the SMBIOS UUID, the disk serial number and the Windows installation identifier. Each value is turned into a one-way hash on your own PC, using a fixed key, and the hashes are sent to the Server each time you press Play. Only those hashes leave your computer, and placeholder values that manufacturers ship on many identical boards are discarded. We do not receive the underlying values; the Server stores the hashes and compares them with other hashes. The Server also records the internet (IP) address you connect from, as described in the Privacy Notice.
Each time you press Play, and when your account is first set up, the Launcher also sends a wider device report. It reads it from Windows without administrator rights (from the Windows registry, one Windows management query and the Launcher's own view of your screens and graphics cards), and reuses a report for up to ten minutes. It contains:
- as one-way hashes made on your PC in the same way as the values above: the manufacturer, product and serial codes of up to 12 monitors that Windows has recorded as connected to the computer; the date and time Windows was installed; the hardware identifiers of the graphics cards; the permanent hardware address built into up to four network adapters (USB adapters are left out); the serial number of the Windows drive's volume; and the serial numbers of up to eight memory modules;
- in readable form, a general description of the computer: the processor model, the graphics card models, the amount of memory, the resolution and model name of each display, the Windows build number and the day Windows was installed, the time zone, the language setting and the keyboard layouts;
- fixed labels when the computer shows signs of being a virtual machine or of running through a remote-display adapter (for example the name of the virtualisation product), and two labels for when two parts of Windows disagree about the computer's manufacturer or model.
None of these values refuses, holds or restricts anyone by itself. The Server compares them with the devices of banned accounts as supporting evidence, and treats a value shared by many unrelated accounts as meaningless. Playing in a virtual machine or over remote play is not against the rules; using it to evade a ban is.
When you sign in, link Discord or set up your account, the Server may also give the Launcher an install marker: a random number, signed by the Server, that identifies this installation. It contains no hardware or personal information. The Launcher keeps it as a small visible file named install.id (for our test server, a file named after that server) in a folder named DaedricOnline, in up to six places:
- the Launcher's own AppData folder (%APPDATA%\Daedric Online);
- %LOCALAPPDATA%\DaedricOnline and %APPDATA%\DaedricOnline;
- Documents\My Games\Skyrim Special Edition\DaedricOnline;
- %PROGRAMDATA%\DaedricOnline, which every Windows user on the computer shares;
- Data\SKSE\Plugins\DaedricOnline inside your Skyrim folder.
The Launcher reads these files at the same moments and sends the markers it finds (up to eight) and the number of places that held one. It uses ordinary files only: it does not hide them and writes nothing to the Windows registry for them. Uninstalling the Launcher and Revert to Vanilla leave them in place (Reset Deployed Mods removes the copy in the Skyrim folder), and you may delete them yourself. In the shared ProgramData folder and in the Skyrim folder, the Launcher never overwrites a marker that belongs to another installation, so a copied game folder or another Windows user's marker can be sent along with yours; the Server treats a marker found only in those two places as weaker evidence than one in your own user folders.
The Server also looks up what kind of network your internet address belongs to (for example a home connection, a mobile network, a data centre, a VPN service or the Tor network) in public lists that we download and keep on the Server. Your address is not sent to anyone for this. The network type is a small, capped part of the evidence described below, it never refuses, holds or restricts anyone by itself, and addresses that many people share count for less.
The Server uses these identifiers to:
- enforce machine bans, which apply to a computer regardless of which account is used on it;
- detect accounts that appear to share a computer or a network, and report that to staff as evidence to weigh, not as proof; two accounts are treated as sharing a computer only when at least two of the SMBIOS UUID, the disk serial number and the Windows installation identifier match, or when one of them matches and none of the other values differs;
- recognise a computer across a reinstall of the Launcher;
- keep a list of the computers each account has played from, so that it can require a fresh Discord sign-in in the Launcher before an account is used from a computer it has not played from before;
- tie each session token it issues to the internet address the token is first used from, so that it can refuse the same token when it comes from an unrelated address;
- keep a ban case for each banned person: one record that links the accounts, Discord accounts, Steam accounts, install markers and hashed device identifiers seen with that person's banned accounts, and that gains the identifiers of each later attempt to return, taken only from sign-ins the Server has verified. A ban therefore applies to the person and to every account and device linked to them, not only to the account that was banned;
- score how closely a newer account matches a banned person, from the identifiers above, the network type, the age of the linked Discord account and how soon after a ban the account appeared, and show close matches to staff for review. An account that matches closely may be placed on probation: it can still play, but it cannot trade with other players, sell from stalls, give or drop items for others, loot other players after a fight, rob, use storage shared with other players, or hold an office or court role, until staff clear it or it has played long enough without new evidence after a review. Staff may hold an account that matches very closely until they have reviewed it. Evidence from a shared network alone never leads to probation or a hold.
How long we keep these: the device report and the install markers seen with an account, for 180 days after the account last sent them, and for as long as the account is banned. A ban case is kept while any of its bans is in force; its identifiers and its record of attempts are removed 180 days after its last ban is lifted, and daily backup copies of ban cases are kept for 14 days. Evidence scores are kept for 90 days, and review records and ended probations for 180 days.
You should know three consequences. A machine ban affects everyone who plays from that computer, including other members of your household; if you share a PC with someone who has been banned, contact staff; staff may also review accounts that share a computer or an installation with a banned person. If the Launcher cannot read at least one identifying value, for example because security software blocks it, the Server may refuse your login until it can; staff can help. And these identifiers are read on your own computer, so they are not tamper-proof: you must not spoof, block or alter them, edit the Launcher's files or settings to misrepresent your identity, or use virtual machines or similar techniques to evade a ban. Doing so is itself grounds for a ban.
6. Client integrity, cheating and exploits
Everyone plays on the same build. Before each launch the Launcher verifies our client files against the Server's manifest, and the collection's mod files against the revision it is pinned to, and sends the Server a build report. When the game connects, the Client reports which plugins it actually loaded. While you play, the Server can also ask the Client to read the plugin files it names and send back their sizes and checksums of their contents, sealed with a one-time code, together with any errors in reading them and how long the reading took; the Server compares these with its own copies of those files. The Server may refuse or disconnect clients that do not match or do not answer, and it may treat a mismatch as evidence of tampering.
The build report is sent with your installation identifier and contains:
- which build the Launcher is running (a hash of the Server's client file list it checked against), and whether every required mod is installed;
- the Launcher's version number, and the revision of the Daedric Online collection it checked against;
- whether you pressed Play anyway, and on which warnings (the game version, missing Creation Club files, or mod files that do not match); for mod files that did not match, up to 50 of their names inside the Data folder, whether each was missing or different, and the Nexus Mods mod and file numbers each belongs to;
- whether the signed release record our Server publishes was present and valid, the reason when it was not, and the record's serial number, hash and signing key, including whether a signed supplement to it was accepted (the Launcher keeps the last valid record, and the highest serial number it has seen, in the DaedricData folder);
- the names of the SkyrimPlatform script and settings files it moved aside on that launch (up to 50 from each folder), the result of the SkyrimPlatform.ini check (already correct, changed, created, SkyrimPlatform not installed, or failed), which kind of PluginFolders line the file had before (none, SkyrimPlatform's default, ours, or another), and which browser its BackendName line named before (none, auto, tilted, nirnlab, off, or another) and whether it was changed; the folder names in that line are not sent;
- the name, size and SHA-256 hash of each DLL file in Data\SKSE\Plugins, the Skyrim Script Extender plugins that load into the game (up to 200 files; a file larger than 64 MB is listed without a hash), and whether they passed the Launcher's check described next. Before each launch, and when you run Verify, the Launcher compares every DLL file in that folder with the DLLs we ship and those the Daedric Online collection installs. When you press Play, it moves every other DLL file out of that folder into DaedricData\quarantine in your Skyrim folder, records where each one went, and tells you which files it moved; it deletes none of them, and Revert to Vanilla puts them back. A DLL from the collection at a different version is only reported, with a note to update that mod. A changed copy of one of our own DLLs is replaced by our client file check; if it still differs, or a file cannot be read or moved, Play does not go ahead and the Launcher names the file.
You must not:
- modify, replace or remove our client files, plugins or scripts, or inject code into the game or the Launcher;
- alter, replay or forge network traffic between the Client and the Server, or read or edit the game's memory to gain information or an advantage;
- use cheats, hacks, trainers, macros, bots, auto-clickers or any automation of play;
- load SkyrimPlatform plugins we did not ship, or use another server's launcher on the same installation while ours manages it;
- abuse bugs or exploits. If you find one, report it with /ticket in game or in #bug-reports on Discord, and do not use it in the meantime.
Mods outside the collection are unsupported: the Launcher may ask to move their plugin files aside, and anything that changes gameplay, gives an advantage over other players or interferes with the Client may be treated as cheating.
7. Conduct in the world and in the community
The full rules are posted in #rules on our Discord and may be updated there. In summary, you agree to:
- Earn it in the world. Reputation, rank, wealth, factions and legend are won through play, not claimed in Discord.
- Stay in character where it counts. The game world is in character by default; keep out-of-character talk to the OOC channels.
- No metagaming. Do not use knowledge from Discord, streams or other out-of-character sources to drive your character's actions.
- Respect the systems. PvP, robbery, cuffs, death, respawn and looting are decided by the server's mechanics; do not force outcomes the game did not grant, and do not circumvent them.
- Keep it Skyrim. Stay lore-plausible unless an event sanctions otherwise.
- Consent and comfort. Respect an out-of-character "no", fade to black, and keep extreme or mature content out of shared spaces.
- No harassment, hate speech, slurs, threats or discrimination of any kind. No doxxing or sharing anyone's personal information.
- No advertising other servers, no spam, no scams, and no impersonating staff.
- Respect staff and game-master decisions, and appeal through the proper channel rather than arguing moderation in public.
- One community, one standard: a ban on Discord is a ban in the game, and vice versa.
8. Moderation and enforcement
Staff (the administrator and the game masters) may warn, kick, mute, restrict, freeze, rename or move characters, remove content, place accounts on probation or hold them for review, and temporarily or permanently ban accounts and machines. A permanent ban applies to the person: it extends to the other accounts and devices linked to them through their ban case (section 5). To investigate a report they may inspect an account's characters, location, inventory, spells, property, activity logs and linked-account reports. Staff actions are recorded in our moderation logs.
A ban from the game is mirrored to our Discord, and a Discord ban is mirrored to the game. Moderation decisions are made at our discretion; we aim to tell you the reason and, for a temporary ban, the duration. To appeal, use our ban page, which shows your ban and lets you appeal it even if you were removed from our Discord, or write to us at the contact address below.
Because the Service is free, our remedy for a breach is to restrict or end your access. We do not owe compensation for lost play time, characters or items when we do so.
9. Characters, items and progress
Characters, items, gold, property, mastery and every other form of in-game progress are features of the Service. They have no real-world value, are not your property, and may be changed, rebalanced, moved, reset or removed as the game develops. In particular:
- The Service is in open alpha. Bugs, rollbacks, wipes and resets are possible, and we may change any system at any time.
- We keep backups of the world, but we cannot promise to restore lost progress.
- Deleting a character is a soft deletion; staff may be able to restore it for a time, but we do not guarantee it.
- The number of characters an account can hold depends on the roles its Discord account holds, such as a supporter role, a staff role or a role earned through play, up to a limit the Server sets.
- You may not sell or buy characters, items, gold or accounts for real money, or advertise such trades.
10. Supporting the server
Playing is free. Supporting the running costs is optional and is handled entirely by Patreon, under Patreon's own terms. A supporter role assigned to your Discord account grants in-game benefits, such as additional character slots. Support is a voluntary contribution, not a purchase of goods or services from us: benefits may change or end as the game develops, we do not process payments, and we cannot issue refunds. Refund questions go to Patreon.
11. Content you create
Character names, chat, voice, letters, notice-board posts, ticket text, bug reports and anything else you create through the Service are yours. So that we can run the Service, you grant us a non-exclusive, royalty-free, worldwide licence to store, display, relay, moderate and reproduce that content within the Service for as long as it is needed, including showing it to other players and keeping copies in moderation records. You must have the right to use anything you submit, and it must follow the rules above. We may remove content, and staff may rename characters whose names break the rules.
12. Software, ownership and third parties
The Launcher, the game logic on the Server, our own plugins, assets and website are the property of Daedric Online and its contributors. You may use them only to play on the Service. You may not redistribute our client files, run your own server with our content, or reverse-engineer the Launcher or the Client except where the law or an open-source licence allows it.
The Client is built on the open-source SkyMP project and SkyrimPlatform, licensed under the GNU GPL and AGPL version 3. Those components remain under their own licences, which give you rights the Terms do not take away, and the corresponding source code for the versions we distribute is available on request. The mods in the collection belong to their authors and are used under their own permissions; see our credits page. The Elder Scrolls and Skyrim are trademarks of ZeniMax Media Inc.
13. Privacy
How we handle your information is set out in our Privacy Notice. In short, we hold your Discord user ID and display name, the roles you hold in our Discord, your player number and installation identifier, your Steam ID with the age of that Steam account and the yes or no results of the Steam checks described above, the hashed device identifiers, device description and install markers described above, a small number of recent IP addresses and the type of network they belong to, any ban case, evidence score, review or probation record that concerns you, your characters and their gameplay data, connection and build-verification logs, moderation records, and whatever you send us in tickets and reports. Ordinary chat and proximity voice are relayed to nearby players and are not recorded by us; other players may, of course, record their own screens. We do not sell personal information. Contact details for privacy requests are in the notice.
14. Availability, changes and ending the Service
We may change, suspend, restart or shut down any part of the Service at any time, with or without notice, and we may end or restrict your access if you breach the Terms or the rules. You may stop using the Service at any time. When your access ends, we may keep the information described in the Privacy Notice for as long as it is needed to enforce bans and keep moderation records.
15. Disclaimer and limitation of liability
The Service is provided free of charge, as is and as available, without warranties of any kind. The Launcher modifies files inside your Skyrim installation and the Client changes how the game runs. We cannot promise that the Service will be uninterrupted, error-free or compatible with your hardware, your other mods or your save games, and we recommend keeping your own backups.
To the fullest extent permitted by law, we are not liable for any loss or damage arising from your use of the Service, including loss of data, save games, mods, game files, progress or play time, or any indirect or consequential loss. Nothing in the Terms excludes or limits liability that cannot be excluded or limited by law, including liability for death or personal injury caused by negligence, for fraud, or for wilful misconduct. If you are a consumer, you keep every right that the law of your country gives you and that cannot be waived by agreement.
16. Changes to the Terms
We may update the Terms as the Service develops. Each version carries a number and a date, shown at the top of this document. When we make a change that matters to you, the Launcher will ask you to read and accept the new version before you can play again; smaller corrections take effect when they are published on the website. Continuing to use the Service after a change means you accept it.
17. Governing law
The Terms are governed by the laws of the country in which the administrator of Daedric Online is established, except where the mandatory consumer-protection law of your country of residence applies. If you have a dispute with us, please contact us first so that we can try to resolve it informally.
18. Contact
Questions about the Terms, appeals and privacy requests can be sent to [email protected] or raised in our Discord community.