ddarchive

About ddarchive

What ddarchive is

The record, and the analysis on top of it

ddarchive is a public record of Devil Daggers runs, and the population analysis that a run-level record makes possible.

The game reports every run to the server run by Sorath, who made it. That server lists only the last hundred runs, and each one drops off the list as new ones arrive, so almost everything ever played leaves no record of the run itself. An archive keeps them instead: the run, the time, the gems, the kills, the way it ended, the date.

The analysis is the second half. A leaderboard can rank a personal best. It cannot show where runs actually end, what ends them at each dagger, or how many runs a new player takes to earn one. Those need a history of every run, which is what the archive is for.

The archive reads that list once a minute, or every thirty seconds while it is moving fast, and keeps every run it finds. It holds what has been played since recording began, and nothing from before that. An older collection of ddstats runs is held apart from it and published nowhere; the privacy section below says what it is and where it came from.

In the archive

Runs played
…
Players recorded
…
Runs the archive missed
…
Duplicate uploads (not counted)
…
Recording since
…

Every run the game has reported since recording began.

On the evening of Saturday 11 October 2026, more than a hundred runs were played in some minutes, so some dropped off the list between two of the archive's reads a minute apart. The archive was running throughout.

The Leaderboard's percentiles are measured against the official board as it stands now: a full copy taken on 11 August 2026, raised every hour by every run played since.

Some players' games get into a state where they upload one finished run again every twenty-two seconds or so, and the official server records each attempt as a new run. Those rows are archived, and almost all of them are recognised and not counted as runs played, on this page or anywhere else on this site. A run is recognised as one of them when the same player sends an identical run again sooner than that run itself lasted, which is not something a replayed game can do.

The other Devil Daggers services

What ddarchive is not, and what the others are

ddarchive is not a rehost of ddstats.com, and it is not a competitor to DDLIVE or devildaggers.info.

It does not render live leaderboards, it does not play back replays in 3D, and it does not host spawnsets, which are custom levels, or custom boards. Those are done, and done well, by the four services below. What ddarchive works on is the record itself and what can be measured from it.

It also offers a Mod builder, a free tool for making texture and sound mods, but it does not host mods. devildaggers.info is where they are shared.

ddstats.com Alex Wilkerson
Per-player run history, detailed run data recorded by a desktop client people choose to install, and a Discord bot the community uses daily.
DDLIVE, at ddstats.live matt
3D replay playback with a scrubber, run splits, a live globe, and per-run coaching insights computed from telemetry. It is the best place to watch a run back.
devildaggers.info Noah Stolk
The most developed data site for the game: spawnsets, custom leaderboards, mods, world-record progression, and a documented public API. Its open format documentation is what much of the community relies on to read the game's own files.
The official leaderboard Sorath
The game's own server, which every copy of Devil Daggers submits to. It is the source the other services read from, and the authority on whether a run is real.

How it works

Where the runs come from

ddarchive reads the official run list once a minute, and every thirty seconds while the list is moving fast enough that runs could drop off it between two reads. It only ever asks for runs newer than the last one it has, it never asks more often than once every thirty seconds, and it makes no requests to ddstats.com.

The official leaderboard's top 100 is read once a day, in one request.

The whole leaderboard has been read three times, without names, each in about 375 requests: on 9 August 2026, for the player counts the Leaderboard used until October; on 11 August, for each player's best time, which is where every personal best the site reports starts from, and which the Leaderboard keeps current by adding every run played since; and on 30 August, at one request every five seconds, kept for reference.

Every request names the project and gives a contact address. If a server signals it has had enough, ddarchive stops rather than slowing down, and it never moves to another address to get around a block.

How the site is built

The site is static files. The figures on it are computed from the archive on the server that hosts it and fetched by each page as data files from this site.

There are no third-party scripts, no analytics, no advertising, no embedded widgets and no cookies. The page loads nothing from any other host: the fonts and the colours are served from this site's own stylesheet. Opening a page on this site contacts this site and nothing else.

The colours start from samples of the game's own textures, adjusted where text or a chart needed them to read clearly, and the dagger colours are the gradients the game uses on its own leaderboard. The colour scales of the charts are chosen, and so are the death colours on the Statistics page's chart of when runs end, because the game gives its skulls no colour of their own.

Provenance and credits

Whose data this is

Devil Daggers was made by Sorath. The game, its name and its art are theirs.

Everything archived here comes from Sorath's server, which is where the game sends it.

ddstats.com is Alex Wilkerson's work, and Devil Daggers has a record at all because he built and ran a service for years. This site is not a rehost of it and does not read from it.

Credits

Open projects this work reads from, and the typefaces the pages ship. Each line names who made it and the licence it is offered under.

NoahStolk/DevilDaggersAssetEditor Noah Stolk
The reference for how the game's asset files are laid out. Used as documentation for our own implementation. No licence is stated on the repository, so nothing is copied from it.
NoahStolk/ddinfo-core Noah Stolk, MIT License
The replay format and the dagger thresholds, read from its source code.
lsaa/ddcore-rs lsaa, MIT License
The Rust implementation behind the ddstats client, and a second independent reading of the replay format to check ours against.
Archivo and Archivo Black Omnibus Type, SIL Open Font License 1.1
The typefaces, embedded in the page. Used and redistributed under the OFL.

Fan content and affiliation

Not affiliated with or endorsed by Sorath

ddarchive is an unofficial fan project, made by a player. It is not affiliated with, sponsored by, or endorsed by Sorath.

Nothing on this site comes from them, and nothing on it should be read as speaking for them. Devil Daggers, its name and its artwork belong to Sorath.

The site carries no advertising, sells nothing, and accepts no payment.

The game's art on this site

None of the game's art is shipped with this site. Its colours start from samples of the game's own textures, apart from the chart colours on the Statistics page, and the dagger colours are the gradients the game uses on its own leaderboard.

They are here to identify the game the site is about, as unofficial fan work, with no claim of ownership and nothing charged to anyone for them.

If Sorath want any of it taken down, or want the archive of their feed stopped, they can say so at the address below and it will be done.

Privacy and your data

Last updated 23 October 2026

What is stored, and why

If you have played Devil Daggers since 10 August 2026, this site holds your runs, and your current in-game name appears beside them. The tables below list everything it publishes about you.

Three sources of game data, then what visiting the site records. Every row below was checked against the code that writes it.

1. The official run feed, read once a minute (every thirty seconds when busy)
WhatWhere it comes from PublishedKept
Your current name, exactly as you set itthe game's own feed Yesone name per player, overwritten
Time, kills, gems, daggers fired and hit, how the run ended the game's own feedYeskept
The game's own id for the runthe game's own feed Yeskept
When the run endedthe game's own feed As a date the exact second is stored; only the last 12 minutes are published to the second, in the stream
Your numeric player idthe game's own feed Nokept
Your countrythe game's own feed No Not stored. The feed sends it for some players; it is read and discarded
Any previous namethe game's own feed No Not stored. The feed sends the name you had at the time on every row; it is read, used to refresh the one current name, and discarded
A personal best you set in the last 30 days: the day, the new time, your previous best, the rank it gives you, and how many players you passed worked out from your runs and the copy of the leaderboard Yes, on the home page, if it is among the most recent or the biggest not stored; worked out again from the runs every minute
How many runs you have played: today, in the last 7 and 30 days, and in total counted from your runs Yes, on the home page, for the ten players with the most not stored; counted again every minute
Your best time, found by typing your current name your runs and the copy of the leaderboard Yes, on the Leaderboard, to anyone who types your name, if you have played since 10 August 2026 rebuilt every hour. The published list holds a scrambled code made from each name, not the names themselves
2. The official leaderboard: one request a day
WhatWhere it comes from PublishedKept
The top 100: rank, name, player id, best time and that run's stats the official leaderboardYes, as the official leaderboard publishes it one snapshot per day
Every player's best time, as a number with no name attached the official leaderboard No three captures, from 9, 11 and 30 August 2026. They are what turn a name in the stream into a rank and a personal best, and what places each run on the Statistics page under the dagger its player held, without any of their player ids reaching your browser. Raised by every run since, the 11 August one is also what the Leaderboard counts
How many players have reached each second the official leaderboard, kept current from the run feedYes, as counts only, drawn on the Leaderboard rebuilt every hour
3. The earlier ddstats archive: held, published nowhere
WhatWhere it comes from PublishedKept
Runs with level splits, gem breakdowns and per-enemy counts ddstats.com's public pages; the runs were recorded by the ddstats client, for players who installed it Noheld offline, unpublished
An index of uploaded replays the ddstats replay service, shared by lsaa, who runs it Noheld offline
A handful of replay filesthe ddstats replay service, shared by lsaa No held offline, to read the file format. A replay carries every input of a run at sixty frames a second, including mouse movement

The runs in table 3 were collected from ddstats.com's public pages in August 2026, before this project settled its rules on requests. They are held offline, published nowhere, and have not been added to since.

4. Visiting this site
WhatWhere it comes from PublishedKept
The web server's log of each request: the page asked for, when, and your IP address with its last part removed, so it points to a network rather than to you. Your browser's details are not kept your browser, when it loads a page No deleted within 14 days. Used only to find broken links and to see if the site is being overloaded

There is nothing here to sign up for, so there are no accounts and no passwords, and ddarchive asks you for no email address. Nothing is sold, nothing is passed to a third party, and there is no advertising, no analytics and no cookies on this site.

Names are published exactly as you set them. Whatever is on the official leaderboard is what appears here, unaltered. Nothing is filtered, cleaned up or substituted. If your name is an email address, that is what shows, because it is the name the game shows every other player. If you would rather it did not appear here at all, the removal link below takes it off the site.

The reason for holding any of it is the archive itself. The official server lists only the last hundred runs, so a run that is not recorded before it drops off that list is not kept anywhere else.

Having your runs removed

You can ask to be taken off this site, and it will be done. You do not have to give a reason.

Email ddarchive@proton.me from any address, with the player name you play under or your player id.

Your name and your runs are then taken off this site: the stream, the home page's tables, the Leaderboard's search by name and every chart on the Statistics page. If you are in the official top 100, that table on the Leaderboard keeps your rank and time, which Sorath's board shows anyway, but not your name or your player id. The site's overall run counts still include your runs, with nothing to say they were yours.

Before runs are taken out, you will be asked to show that the player is you: a reply from an address or a Discord account already tied to that name, or a short phrase set as your in-game name for a day. That is there so one player cannot have another player's runs pulled. If a request is genuinely unclear, or if it is not possible to tell which player is meant, you will get a reply asking rather than a guess. Expect a reply within a week, and the request carried out within 30 days.

Your email address is used to answer the request and to carry it out. It is not added to the archive, it is not used for anything else, and the message is kept only until the request is done and confirmed.

Two things this cannot do. It cannot change anything on Sorath's official leaderboard, or on ddstats.com, DDLIVE or devildaggers.info, because those are other people's services. And it cannot recall a copy of the data that somebody else has already downloaded.

If you are in the EU or the UK

The basis for holding this data is legitimate interest: keeping a public record of a public game leaderboard, and analysing it. No special category data is involved. Nothing here makes an automated decision about anyone, and none of these figures has any legal or similarly significant effect. The per-player figures are performance analysis of published leaderboard results, and you can object to yours being computed.

You can ask what is held about a player name, ask for it to be corrected, ask for it to be deleted, or object to it being held at all. Use the same address. One person answers that mailbox.

You can also complain to your national data protection authority, and in the UK to the Information Commissioner's Office.

Terms of use

Last updated 9 August 2026

The data

It is a free fan archive. It may be wrong, and it may go away. Use it with that in mind.

  • The data is provided as is. It is assembled from the game's own feed and the official leaderboard. It can be incomplete, out of date or simply wrong, and it comes with no warranty of any kind. If something matters, check it against the game.
  • Records are cross-checked; everything else is a computed figure. No run is presented here as a record unless it appears on the official in-game leaderboard. Every other number is calculated from the archive, and the archive does not contain every run ever played.
  • Do not misrepresent it. Reuse the figures, quote them, build on them. Just do not present them as official, as Sorath's, or as endorsed by anyone here.

The service

It is one person's project on one person's hosting, and it is free to use.

  • Please do not hammer it. Read it like a person would. Automated access should identify itself with a contact address and stay well under one request per second. If you want a lot of data, write and ask for it. That is cheaper for both of us than scraping, and it saves you the trouble.
  • No guarantee that it stays up. Pages, figures and URLs can change, and the site can stop. Nothing here is promised to be available tomorrow.
  • Something wrong, or something that should not be here? Write to the address below. Corrections, takedown requests and privacy requests are all handled the same way, by a person reading the mail.

Contact

One address, read by a person

ddarchive@proton.me

Removal and privacy requests, corrections to a run or a figure, bugs, questions about where a number came from, requests for the data in bulk, and anything from Sorath or from the maintainers of the other services.

Who runs it

ddarchive is run by one person, a Devil Daggers player, as a community project. It is not a company and there is nothing to buy.

It is meant to be useful to the people who already maintain things in this community, so if it duplicates your work or gets something about your service wrong, say so and it will be fixed.