Read the drop tables from the repo instead of warframe.com

warframe.com blocks requests from the server, so /Warframe had nothing to parse once deployed. Commit the page instead and read it from disk: the site now makes no network call at runtime, and the data it serves is whatever was current at the last deploy. scripts/update-droptables.sh refreshes the file, and the Rider publish configuration runs it as a before-run task ahead of the restore, so a deploy ships current data without anyone remembering to pull it. The external tool that points at it lives in Rider's own config rather than this repo, so a fresh checkout needs it adding by hand. The script will not replace a good copy with a bad one. The publish that follows ships whatever lands in Resources, and a block or an outage answers with an error page rather than an error, so a download far short of 4 MB and twenty sections is refused. A refresh that fails is a warning and not an error: the committed copy is still good data, and DE being down should not block a deploy that has nothing to do with Warframe. Having no copy at all is an error, because then there is nothing to publish. Two things here break only once published, and neither shows up in development, where the content root is the project directory and the file is simply there: The Web SDK's default content glob is wwwroot, *.json and *.config, which is why Resources/test-data.json publishes for free. An html file does not, so Blog.csproj names this one explicitly with CopyToPublishDirectory - a publish without it produced an output with no drop tables in it at all. The path resolves against AppContext.BaseDirectory rather than ContentRootPath. Both the content root and the working directory default to wherever the process was started from, so the published app run from / went looking in /Resources and found nothing. The tables ship next to the assembly, so that is what to anchor to. WarframeDropService loses the HttpClient, the url, the timeout and the twelve hour expiry that went with fetching. What replaces them is the file's own last write time: a stat per request, which keeps the parse a one-off in production while letting dotnet watch pick up a refresh without a restart. The page footer now dates the copy rather than the request. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

author: Marijn Besseling <njirambem@gmail.com> · 2026-09-13 18:41 UTC
commit: 60f0aebc39d7ebedeb8ad74c64ff5bbb6a9a0549
parent: d8bb8781b5
tree: browse at this commit

9 files changed +22385 -77

.run/Publish Blog to custom server.run.xml		+1 -0
Blog/Blog.csproj		+11 -0
Blog/Components/Pages/Warframe.razor		+2 -1
Blog/Components/Pages/Warframe.razor.cs		+6 -2
Blog/Program.cs		+4 -9
Blog/Resources/droptables.html	added	+22239 -0
Blog/Services/WarframeDropService.cs		+40 -53
CLAUDE.md		+28 -12
scripts/update-droptables.sh	added	+54 -0

This diff is longer than one page will show. The files below it keep their counts; read them at this commit's tree instead.

@@ -6,6 +6,7 @@
6	6	</runtimes>
7	7	</riderPublish>
8	8	<method v="2">
	9	+ <option name="ToolBeforeRunTask" enabled="true" actionId="Tool_External Tools_update droptables" />
9	10	<option name="ToolBeforeRunTask" enabled="true" actionId="Tool_External Tools_restore linux" />
10	11	</method>
11	12	</configuration>

@@ -20,6 +20,17 @@
20	20	</ItemGroup>
21	21
22	22	<ItemGroup>
	23	+ <!--
	24	+ The Web SDK's default content glob only covers wwwroot, .json and .config, so
	25	+ Resources/test-data.json is published on its own but the drop tables are not. /Warframe
	26	+ reads this at runtime, so name it explicitly or the deployed site has nothing to search.
	27	+ -->
	28	+ <Content Include="Resources/droptables.html"
	29	+ CopyToOutputDirectory="PreserveNewest"
	30	+ CopyToPublishDirectory="PreserveNewest" />
	31	+ </ItemGroup>
	32	+
	33	+ <ItemGroup>
23	34	<Folder Include="wwwroot\Icons\" />
24	35	</ItemGroup>
25	36

@@ -189,7 +189,8 @@
189	189
190	190	<p class="muted">
191	191	<a href="https://www.warframe.com/droptables">Drop tables</a> by Digital Extremes,
192		- last updated @tables.LastUpdate; read @Age(tables.FetchedAt).
	192	+ last updated @tables.LastUpdate. This copy was pulled @Age(tables.FetchedAt) and
	193	+ refreshes when the site is deployed.
193	194	</p>
194	195	}
195	196	</main>

@@ -104,7 +104,10 @@ public partial class Warframe : ComponentBase
104	104	private static string ItemCount(DropTables tables) =>
105	105	tables.Names.Count.ToString("N0", CultureInfo.InvariantCulture);
106	106
107		- /// <summary>How stale the copy on screen is.</summary>
	107	+ /// <summary>
	108	+ /// How long ago this copy of the page was downloaded, taken from the file's own timestamp. Days
	109	+ /// is the unit that matters here: the copy changes only when the site is deployed.
	110	+ /// </summary>
108	111	private static string Age(DateTimeOffset fetchedAt)
109	112	{
110	113	var age = DateTimeOffset.UtcNow - fetchedAt;
@@ -113,7 +116,8 @@ public partial class Warframe : ComponentBase
113	116	{ TotalMinutes: < 1 } => "just now",
114	117	{ TotalHours: < 1 } => $"{(int)age.TotalMinutes} min ago",
115	118	{ TotalDays: < 1 } => $"{(int)age.TotalHours} h ago",
116		- _ => $"{(int)age.TotalDays} d ago"
	119	+ { TotalDays: < 2 } => "yesterday",
	120	+ _ => $"{(int)age.TotalDays} days ago"
117	121	};
118	122	}
119	123	}

@@ -14,16 +14,11 @@ builder.Services.AddHttpClient<BrpService>(
14	14	client.BaseAddress = new Uri("https://brp.bes.is/");
15	15	});
16	16
17		-// /Warframe searches Digital Extremes' published drop tables: 4 MB of HTML, updated a few times a
18		-// month, parsed once and held in memory - see WarframeDropService.
	17	+// /Warframe searches Digital Extremes' published drop tables. warframe.com blocks requests from
	18	+// the server, so the 4 MB page ships in Blog/Resources and scripts/update-droptables.sh refreshes
	19	+// it before a publish. Singleton: the parsed tables live in the service, so a transient one would
	20	+// re-parse per request - see WarframeDropService.
19	21	builder.Services.Configure<WarframeOptions>(builder.Configuration.GetSection(WarframeOptions.Section));
20		-builder.Services.AddHttpClient(WarframeDropService.ClientName, client =>
21		-{
22		- // The page is served off a CDN; identify the caller rather than asking for 4 MB anonymously.
23		- client.DefaultRequestHeaders.UserAgent.ParseAdd("bes.is-droptables/1.0 (+https://bes.is/Warframe)");
24		-});
25		-
26		-// Singleton: the parsed tables live in the service, so a transient one would re-parse per request.
27	22	builder.Services.AddSingleton<WarframeDropService>();
28	23
29	24	// /rvrb reads the rvrb bot's stats straight off its BEAM, over Erlang distribution. The node this

Read the drop tables from the repo instead of warframe.com

9 files changed +22385 -77

.run/Publish Blog to custom server.run.xml +1 -0

Blog/Blog.csproj +11 -0

Blog/Components/Pages/Warframe.razor +2 -1

Blog/Components/Pages/Warframe.razor.cs +6 -2

Blog/Program.cs +4 -9

Blog/Resources/droptables.html +22239 -0

Blog/Services/WarframeDropService.cs +40 -53

CLAUDE.md +28 -12

scripts/update-droptables.sh +54 -0

@@ -0,0 +1,22239 @@
	1	+<!DOCTYPE html>
	2	+<html lang="en">
	3	+<head>
	4	+<meta charset="UTF-8">
	5	+<title>Warframe PC Drops</title>
	6	+<style>
	7	+table {
	8	+border: 0;
	9	+border-collapse: collapse;
	10	+margin-bottom: 20pt;
	11	+}
	12	+tr, td, th {
	13	+border: 1px solid black;
	14	+text-align: left;
	15	+padding: 3pt;
	16	+}
	17	+.pad-cell {
	18	+width: 50pt;
	19	+}
	20	+.blank-row {
	21	+border: 0;
	22	+height: 15pt;
	23	+}
	24	+p {
	25	+width: 500pt;
	26	+}
	27	+</style>
	28	+</head>
	29	+<body>
	30	+<p><b>Last Update:</b>
	31	+25 June, 2026
	32	+<h3>Disclaimer:</h3>
	33	+<p>This list represents data and drops from the PC version of the Free-to-play game Warframe.<br/>
	34	+That's right - Warframe is free! Which means our drop system is designed to maintain a balance. Our free players can earn the game's content, and our paying players who support us with purchases usually get first dibs on the content by using Platinum (which can be traded to free players)!<br/>
	35	+<p>This is automatically generated from our internal data but this data comes with no guarantees -- do not expect it to be comprehensive for how complex the game is.<br/>
	36	+This list will be maintained by an automated process combined with manual publishing with Updates (not all Hotfixes). We update often and new game systems may or may not be covered here.<br/>
	37	+This list can be discussed <a href="https://forums.warframe.com/topic/809777-drop-rates-pc-website/">here</a>.
	38	+Thank you for playing Warframe.</p>
	39	+<h3>Table of Contents:</h3>