Skip to content

Commit 92388ae

Browse files
Merge pull request #12716 from github/updates
Added 2023/01/2023-01-09-game-code.md
2 parents 5723995 + b726fef commit 92388ae

File tree

1 file changed

+87
-0
lines changed

1 file changed

+87
-0
lines changed

2023/01/2023-01-09-game-code.md

+87
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,87 @@
1+
While GitHub did not find sufficient information to determine a valid anti-circumvention claim, we determined that this takedown notice contains other valid copyright claim(s).
2+
3+
---
4+
5+
Before disabling any content in relation to this takedown notice, GitHub
6+
- 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).
7+
- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice).
8+
9+
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).
10+
11+
---
12+
13+
**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
14+
15+
Yes, I am the copyright holder.
16+
17+
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
18+
19+
No
20+
21+
**Does your claim involve content on GitHub or npm.js?**
22+
23+
GitHub
24+
25+
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
26+
27+
I am the owner of the proprietary source code that has been stolen.
28+
29+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed. If possible, include a URL to where it is posted online.**
30+
31+
It is a proprietary game modification.
32+
33+
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
34+
35+
https://github.com/SkidderMC/FDPClient/blob/main/src/main/java/net/ccbluex/liquidbounce/features/module/modules/movement/flys/matrix/Matrix117Fly.kt
36+
https://github.com/SkidderMC/FDPClient/blob/main/src/main/java/net/ccbluex/liquidbounce/features/module/modules/movement/flys/aac/AAC520Fly.kt
37+
https://github.com/SkidderMC/FDPClient/blob/main/src/main/java/net/ccbluex/liquidbounce/features/module/modules/movement/flys/aac/AAC520VanillaFly.kt
38+
https://github.com/SkidderMC/FDPClient/blob/main/src/main/java/net/ccbluex/liquidbounce/features/module/modules/exploit/disablers/verus/OldGhostlyDisabler.kt
39+
https://github.com/SkidderMC/FDPClient/blob/main/src/main/java/net/ccbluex/liquidbounce/features/module/modules/exploit/disablers/verus/LatestVerusDisabler.kt
40+
https://github.com/SkidderMC/FDPClient/blob/main/src/main/java/net/ccbluex/liquidbounce/features/module/modules/exploit/disablers/verus/OldVerusMoveDisabler.kt
41+
https://github.com/SkidderMC/FDPClient/blob/main/src/main/java/net/ccbluex/liquidbounce/features/module/modules/exploit/disablers/other/OldMatrixDisabler.kt
42+
https://github.com/SkidderMC/FDPClient/blob/main/src/main/java/net/ccbluex/liquidbounce/features/module/modules/exploit/disablers/combat/MineplexCombatDisabler.kt
43+
https://github.com/SkidderMC/FDPClient/blob/main/src/main/java/net/ccbluex/liquidbounce/features/module/modules/exploit/disablers/verus/OldVerusCombatDisabler.kt
44+
45+
**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology">Complaints about Anti-Circumvention Technology</a> if you are unsure.**
46+
47+
Yes
48+
49+
**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**
50+
51+
Source Obfuscation, and locking down access to specific users.
52+
53+
**How is the accused project designed to circumvent your technological protection measures?**
54+
55+
Via social engineering a developer with our source code.
56+
57+
**<a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">Have you searched for any forks</a> of the allegedly infringing files or repositories? Each fork is a distinct repository and must be identified separately if you believe it is infringing and wish to have it taken down.**
58+
59+
No.
60+
61+
**Is the work licensed under an open source license?**
62+
63+
No
64+
65+
**What would be the best solution for the alleged infringement?**
66+
67+
Reported content must be removed
68+
69+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
70+
71+
No. I do not.
72+
73+
**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.**
74+
75+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
76+
77+
**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.**
78+
79+
**I have read and understand GitHub's <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/">Guide to Submitting a DMCA Takedown Notice</a>.**
80+
81+
**So that we can get back to you, please provide either your telephone number or physical address.**
82+
83+
[private]
84+
85+
**Please type your full legal name below to sign this request.**
86+
87+
[private]

0 commit comments

Comments
 (0)