In early 2025, a Final Fantasy XIV mod ignited concerns about player stalking after reports surfaced detailing its ability to harvest sensitive player data. This included character details, retainer information, linked alternate characters, and more.
The mod, "Playerscope," tracked players' data within a certain radius, transmitting it to a central database controlled by the mod's creator. This exposed information typically inaccessible through in-game tools, including "Content ID" and "Account ID," enabling cross-character tracking. This exploited the Content ID system introduced in the Dawntrail expansion, originally intended for player blacklisting.
Opting out required joining the Playerscope Discord and explicitly disabling data collection. Otherwise, virtually every Final Fantasy XIV player outside this Discord was potentially having their data scraped, raising significant privacy concerns. The community's reaction was swift and critical, with many citing the mod's obvious potential for stalking.
Initially hosted on Github, the mod's popularity exploded after its discovery. Subsequently removed from Github due to Terms of Service violations, it allegedly reappeared on alternative platforms like Gittea and Gitflic, though IGN verified its absence from those sites. The possibility of its continued circulation within private communities remains.
Yoshida outlined potential responses: requesting the mod's removal and pursuing legal action. He reassured players that account details like addresses and payment information were inaccessible via these tools. He urged players to avoid using third-party tools, refrain from sharing installation details, and emphasized the violation of the Final Fantasy XIV User Agreement, highlighting the potential threat to player safety.
While third-party tools like Advanced Combat Tracker are commonly used (and data cross-referenced on sites like FFlogs), Yoshida's legal threat represents a significant escalation.
Community Response:
The community's response to Yoshida's statement was overwhelmingly negative. Many criticized the lack of solutions focusing on preventing data exposure on the client-side, suggesting a failure to address the root problem. The Playerscope author has yet to comment.
