In early 2025, a Final Fantasy XIV mod ignited concerns about player stalking due to reports of 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, sending it to a central database controlled by the mod's creator. This exposed information typically inaccessible through in-game features, including "Content ID" and "Account ID," enabling cross-character tracking. This exploited the Content ID system introduced with the Dawntrail expansion, designed for account-wide blacklisting.
Opting out required joining the Playerscope Discord server. Essentially, any player outside this server was potentially having their data scraped, raising significant privacy concerns. The community reacted strongly, with many labeling the mod's purpose as stalking.
Initially hosted on Github, the mod's popularity surged after its discovery. Subsequently removed from Github due to Terms of Service violations, it reportedly appeared on alternative platforms, though IGN verified its absence from Gittea and Gitflic. However, its potential circulation within private communities remains a possibility.
Naoki 'Yoshi-P' Yoshida, producer and director of Final Fantasy XIV, addressed the situation on the game's official forum, directly referencing Playerscope. He stated that Square Enix was aware of the mod and community concerns, exploring options including removal requests and potential legal action. Yoshida reassured players that account details like addresses and payment information were inaccessible via this tool.
He urged players to avoid third-party tools, emphasizing the violation of the Final Fantasy XIV User Agreement and potential safety risks. While tools like Advanced Combat Tracker are commonly used (and cross-referenced on sites like FFlogs), Yoshida's legal threat marked a significant escalation.
Community Reaction:
The community's response to Yoshida's statement was largely critical. Players questioned the lack of solutions addressing the root cause, suggesting focusing on preventing client-side data exposure. Disappointment was expressed regarding the statement's failure to acknowledge the fundamental issue. The Playerscope author has yet to comment.
