A new GW DMCA action has created a serious problem for players relying on unofficial Warhammer army builders.
This time, Games Workshop has targeted the data infrastructure sitting behind several popular community tools. Consequently, the impact reaches much further than simply removing one website or application. For many players, the bigger question is what happens when the next points update arrives.
Community Army Builders Just Lost One of Their Most Important Data Sources
The enforcement action covers 37 Warhammer-related repositories maintained through BSData and hosted on GitHub. Those repositories supplied army information to several independent list-building tools across Games Workshop systems. Warhammer 40,000, Age of Sigmar, Necromunda, and older editions were among the affected game lines. Following the notice, BSData removed its repository collection rather than leaving the disputed files available.
Importantly, a DMCA notice represents a copyright claim rather than a legal judgment establishing infringement. Games Workshop’s complaint focused particularly on official rules text appearing inside the shared data. Examples included wording associated with Darnath Lysander and the Icon of Obstinacy ability. That makes the dispute more complicated than simply arguing over points costs or unit names. Community builders often need points, weapon options, detachments, and restrictions to function properly.
However, reproducing lengthy ability descriptions creates a much clearer copyright issue. Existing users may also see very little change immediately. Previously downloaded catalogs can remain available locally, while saved lists do not suddenly disappear. The real trouble begins when Games Workshop changes points, publishes new books, or introduces fresh units.
Without an actively maintained central repository, those catalogs will gradually become outdated. New Recruit, BattleScribe-compatible applications, Yellowscribe, and some Tabletop Simulator workflows have all benefited from BSData information. Consequently, this could fragment a community ecosystem that players have relied upon for years. Some users argue that unofficial builders remain easier to navigate than Games Workshop’s official alternatives. Meanwhile, others believe copying substantial rules wording made some form of enforcement increasingly likely. There has also been speculation surrounding paid features offered by New Recruit.
However, no confirmed evidence shows that monetization triggered the GW DMCA action. Simply reposting identical repositories elsewhere would probably leave the underlying dispute unresolved. Therefore, future community tools may need shorter descriptions, original wording, or different methods for handling official rules.
Final Thoughts
The important story here is not that BattleScribe-style tools suddenly stop working tomorrow. Instead, the GW DMCA action threatens the pipeline keeping those tools current. Existing catalogs may survive temporarily, but every future balance update increases the pressure. Ultimately, community developers must now decide whether these tools can evolve without recreating the same copyright problem.
