Protocol Update — Guild Wars 3
Guild Wars 3 was officially announced yesterday. While the community is rightfully caught up in the hype, my focus remains on what this means for the data.
As a solo data enthusiast just starting to build out the Truediff extraction pipeline, this announcement actually serves as a perfect stress test for the architecture I am putting together.
1. The Raw Data
Based on the official announcements (stripping away the PR):
- Timeline: Prequel, set >1000 years before GW1, in Ancient Orr.
- Factions: Vaelwardens vs Rival Guilds.
- Release Window: Beta anticipated in 2027.
- Philosophy: ArenaNet promises to solve “player problems & frustrations” through innovation.
From a theorycrafting perspective, “frustrations” are solved through measurable improvements—things like I-frames, animation locks, and server tick-rate. My goal is to eventually measure these changes when the time comes.
2. Truediff Pipeline: Agnostic by Design
The system I am building (the engine behind Truediff) is an Agnostic Analysis Framework.
The core of my analysis engine is not hardcoded to a single game client’s behavior. My intention is that once the GW3 client is available (hopefully during the 2027 Beta), I will be able to adapt my testing methodologies to the new environment and start running empirical tests right away.
I am building this toolset now so that when GW3 launches, I will be ready from Day 1 to measure frame data, damage multipliers, and uncover hidden mechanics through rigorous analysis. I’ll simply open a new, isolated schema in the database for it.
3. Focus on the Baseline (GW2)
Until then, the work doesn’t stop. ArenaNet has confirmed their continued commitment to Tyria, which means Guild Wars 2 is my Baseline.
I will keep building my analysis protocols, running extensive tests on every GW2 patch, and logging the true diff between the official patch notes and reality. I am here to build the Almanac, and GW2 is the perfect testing ground to perfect this pipeline.
That’s the diff.