As seen below
Also more proof
And Claude’s response on why he couldnt get the information from the page:
Yes, those pages do contain the specific gallery/prefab lists. I could see fragments of that text because the search engine had already rendered and indexed the pages, so the snippets it returned to me included real content. That’s how I pulled the Kappa Kappa Pickle Co. breakdown and the Plumpton items.
What failed was my direct fetch of the pages. When I requested them, I got back essentially an empty shell — just page metadata (a base path, a meta-robots tag, a viewport tag) and the title, with no body content at all. That signature is characteristic of a client-side-rendered site: the server sends a minimal HTML skeleton, and the actual article content is injected afterward by JavaScript calling the site’s backend. My fetch tool retrieves the raw server response but does not execute JavaScript, so I received the skeleton before any content was populated.
Here’s the honest part, though: I don’t think this is a defect Epic would act on. The dev.epicgames.com docs render perfectly fine in a normal browser, and clearly to Google’s crawler too (which executes JS) — that’s why the searchable text exists. So a bug report saying “the release-notes page returns no content” would most likely come back as “working as intended,” because for human users and standard search engines it does work. The limitation here is on my retrieval side — no JS execution — not on their site being broken.
If you did want to report something accurate, the framing that would actually be valid is a feature request rather than a bug: that the release-notes pages don’t expose content in the initial server response (no server-side rendering / no static HTML fallback), which makes them inaccessible to any non-JS client or scraper. Some teams care about that for accessibility and indexing robustness. But it’s a “nice to have,” not a malfunction.
If it’s useful, I can instead just continue pulling the missing 40.10 / 40.20 / 40.30 specifics through more targeted searches — that route works fine and would get you the actual asset names.
If Chrome extension is installed, then it can access it by seeing the page through the browser