From f4260339740c08dcc2da8929c5f9ea705daf4dc0 Mon Sep 17 00:00:00 2001 From: dmca-sync-bot Date: Thu, 28 May 2026 19:41:20 +0000 Subject: [PATCH] Process DMCA request --- 2026/05/2026-05-27-tencent-3.md | 96 +++++++++++++++++++++++++++++++++ 1 file changed, 96 insertions(+) create mode 100644 2026/05/2026-05-27-tencent-3.md diff --git a/2026/05/2026-05-27-tencent-3.md b/2026/05/2026-05-27-tencent-3.md new file mode 100644 index 0000000000..6f95bcdf5f --- /dev/null +++ b/2026/05/2026-05-27-tencent-3.md @@ -0,0 +1,96 @@ +Before disabling any content in relation to this takedown notice, GitHub +- contacted the owners of some or all of the affected repositories to give them an opportunity to [make changes](https://docs.github.com/en/github/site-policy/dmca-takedown-policy#a-how-does-this-actually-work). +- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice). + +To learn about when and why GitHub may process some notices this way, please visit our [README](https://github.com/github/dmca/blob/master/README.md#anatomy-of-a-takedown-notice). + +--- + +**Are you the copyright holder or authorized to act on the copyright owner's behalf? If you are submitting this notice on behalf of a company, please be sure to use an email address on the company's domain. If you use a personal email address for a notice submitted on behalf of a company, we may not be able to process it.** + +Yes, I am authorized to act on the copyright owner's behalf. + +**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?** + +Yes + +**Please provide the Zendesk ticket number of your previously submitted notice. Zendesk ticket numbers are 7 digit ID numbers located in the subject line or body of your confirmation email.** + +4294592 + +**Does your claim involve content on GitHub or npm.js?** + +GitHub + +**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.** + +I, [private], hereby accept the entrustment of Shenzhen Tencent Computer Systems Company Limited (hereinafter referred to as "Tencent") to issue this letter regarding the infringement of Tencent's copyrights by users on your platform: +Tencent exclusively operates the game Roco Kingdom: World and is entitled to protect its legitimate rights and interests, including intellectual property rights, against infringements of the aforesaid game. + +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** + +This repository is a fork / copy of the infringing repository [private] (reported in the same batch). It contains the same proprietary game data extracted from our copyrighted software *Roco Kingdom World*, developed and published by Tencent Games, along with additional cheating tools. + +Specifically: + +1. Decoded proprietary game data (directories: Bin/, PB/, Config/, Dialogue/, BattleCamera/, BattleFsm/, Nav/, Record/, StarLight/) +Identical to the parent repository — this repository contains hundreds of copyrighted game configuration files decoded from our proprietary binary formats into readable JSON, including monster/pet data, battle parameters, skill definitions, quest configurations, and dialogue scripts. + +2. Reverse engineering tools (files: Bin/decode_bin.py, PB/decode_pb.py) +The same decoding tools as in the parent repository, used to extract and reverse-engineer our proprietary binary formats and Protobuf protocol definitions. + +3. Additional cheating tools (directory: tools/) +This fork adds automated cheating scripts not present in the original repository: +- **tools/roco_query.py**: A query tool built using our extracted game data, used to look up internal monster attributes, skill data, and map configurations. +- **tools/roco_shiny.py**: A tool that uses our extracted data to track rare monster spawn mechanics, providing users with an unfair advantage. +- **tools/roco_loop2.py** and **tools/roco_loop2_gui.py**: Automated keypress loop scripts that send repeated input to our game client, constituting game automation / cheating software. + +This repository combines unauthorized copies of our copyrighted game data with automated cheating tools. + +**If the original work referenced above is available online, please provide a URL.** + +https://rocom.qq.com/ + +**We ask that a DMCA takedown notice list every specific file in the repository that is infringing, unless the entire contents of the repository are infringing on your copyright. Please clearly state that the entire repository is infringing, OR provide the specific files within the repository you would like removed.** + +**Based on the above, I confirm that:** + +The entire repository is infringing + +**Identify the full repository URL that is infringing:** + +https://github.com/li3500764/Roco-Kingdom-World-Data + +**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our Complaints about Anti-Circumvention Technology if you are unsure.** + +No + +**If you are reporting an allegedly infringing fork, please note that each fork is a distinct repository and must be identified separately. Please read more about forks. As forks may often contain different material than in the parent repository, if you believe any of the repositories or files in the forks are infringing, please list each fork URL below:** + +**Based on the representative number of forks I have reviewed, I believe that all or most of the forks are infringing to the same extent as the parent repository.** + +**Is the work licensed under an open source license?** + +No + +**What would be the best solution for the alleged infringement?** + +Reported content must be removed + +**Do you have the alleged infringer’s contact information? If so, please provide it.** + +**I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law.** + +**I have taken fair use into consideration.** + +**I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed.** + +**I have read and understand GitHub's Guide to Submitting a DMCA Takedown Notice.** + +**So that we can get back to you, please provide either your telephone number or physical address.** + +[private] + +**Please type your full name for your signature.** + +[private]