alexnguyen25/patchoracle-skyblock-patches

Hypixel SkyBlock Patch Corpus — metadata and resolved anchors

What: one row per Hypixel SkyBlock patch, 2019-06-11 → 2026-07-15 — title, date, source, resolved publish timestamp, anchor precision, forum thread URL, and how many labeled market events the patch produced.

Why it's separate: the publish timestamp is the hard part of any event study on this game, and it is reusable independently of anyone's price labels. If you want to run your own analysis against your own price source, this is the anchor table you need.

Size

396 patches. 152 at hour precision, 244 at day precision. 163 carry a forum URL.

⚠️ Read anchor_precision before using anchor_ts

This is the single most important column and the easiest to misuse.

value	patches	meaning
hour	152	anchor_ts is a real forum post time at minute precision, scraped from the thread and validated against patch_date
day	244	anchor_ts is a placeholder of 00:00 UTC. It is a fiction. Real patches publish at a median ≈15:00 UTC

Always stratify intraday results by anchor_precision. In this project's own analysis, pooling the two hid a genuine effect: a +12h magnitude reaction significant at p=6e-5 in the well-anchored subsample was invisible when the day-precision fictions were mixed in. There is also a 1.7× diurnal volatility cycle in this market (08:00 UTC 0.77× vs 22:00 UTC 1.30×), so any all-hours baseline built on 00:00 placeholders will be biased.

~86.7% of the missing timestamps are recoverable, and this release does not do it

Of the 233 day-precision patches with no forum_url, 202 (86.7%) have a recoverable forum thread. The reason they were missing is a bug, not absent data: the scraper searched the raw wikitext for a literal https://hypixel.net/threads/… URL, but the wiki stores it as a template call —

{{Update Link|post=5481420|title=SkyBlock - Year 300}}

— which only expands to a URL at render time. Of 20 recovered threads sampled, 20 yielded a timestamp that passed the project's own trust check.

Deliberately not applied here. Filling those anchors changes downstream model features and would move published results, so it belongs in a separate, pre-registered pass. The anchor_ts_recoverable_note column marks exactly which rows are affected. One thing that pass will have to settle: at least one sampled patch's forum post is dated the day before its wiki patch_date, so which source is authoritative is a real decision.

Fields

Column	Meaning
patch_id	stable id, joins to patch / event_id in the companion event dataset
title	wiki changelog title (e.g. Changelog/2023/September 3) or RSS title
patch_date	calendar date from the wiki
source	wiki or rss
anchor_ts	resolved publish timestamp — see anchor_precision first
anchor_precision	hour (real) or day (placeholder)
anchor_ts_recoverable_note	whether this row's anchor is real, and if not, whether it is recoverable
forum_url	official forum thread, when known
n_chars	length of the patch text, useful for chunking/complexity analysis
n_events	bazaar item events extracted from this patch
n_usable_labels	of those, how many carry usable outcome labels

Caveats

• n_events is 0 for patches that touched no bazaar-resolvable item — a real property of the corpus, not missing data.
• Patch text itself is not included (it is the wiki's, and large); fetch it from the MediaWiki API using title.
• patch_date is the wiki's editorial date and can differ from the forum post date.

License & attribution

CC-BY-SA 4.0, inheriting the Hypixel SkyBlock Wiki's license. Credit: Hypixel SkyBlock Wiki (Fandom), Hypixel API. Not affiliated with Hypixel. Built by the PatchOracle project.

Companion datasets

• patchoracle-skyblock-patch-events — 2,078 patch→price events with outcome labels, the main dataset.
• patchoracle-skyblock-mayor-cells — the 42-cell mayor election event study.