Advertisement
Guest User

_02938_99_XJDRT_097

a guest
Jan 19th, 2018
1,741
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 64.52 KB | None | 0 0
  1. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 1 of 30 Page ID #:245
  2.  
  3.  
  4. 1 JAMES Y. PAK (SBN 304563) james.pak@skadden.com
  5. 2 SKADDEN, ARPS, SLATE, MEAGHER & FLOM LLP
  6. 525 University Avenue, Suite 1400
  7. 3 Palo Alto, CA 94301 Telephone: (650) 470-4500
  8. 4 Facsimile: (650) 470-4570
  9.  
  10. 5 KEVIN J. MINNICK (SBN 269620) kevin.minnick@skadden.com
  11. 6 SKADDEN, ARPS, SLATE, MEAGHER & FLOM LLP
  12. 300 South Grand Avenue, Suite 3400
  13. 7 Los Angeles, CA 90071 Telephone: (213) 687-5000
  14. 8 Facsimile: (213) 687-5600
  15.  
  16. 9 P. ANTHONY SAMMI (admitted pro hac vice) anthony.sammi@skadden.com
  17. 10 KURT WM. HEMR (admitted pro hac vice) kurt.hemr@skadden.com
  18. 11 SKADDEN, ARPS, SLATE, MEAGHER & FLOM LLP
  19. Four Times Square
  20. 12 New York, New York 10036 Telephone: (212) 735-3000
  21. 13 Facsimile: (212) 735-2000
  22. 14 Attorneys for Plaintiff Crytek GmbH
  23. 15
  24.  
  25. 16 IN THE UNITED STATES DISTRICT COURT
  26.  
  27. 17 FOR THE CENTRAL DISTRICT OF CALIFORNIA
  28.  
  29. 18 WESTERN DIVISION
  30. 19 CRYTEK GMBH, ) Case No. 2:17-cv-08937-DMG-FFM
  31. )
  32. 20 Plaintiff, ) PLAINTIFF'S OPPOSITION TO
  33. ) DEFENDANTS' MOTION TO
  34. 21 v. ) DISMISS THE FIRST AMENDED ) COMPLAINT OR CLAIMS FOR 22 CLOUD IMPERIUM GAMES CORP. ) RELIEF THEREIN OR, IN THE and ROBERTS SPACE INDUSTRIES ) ALTERNATIVE, TO STRIKE
  35. 23 CORP., ) PORTIONS OF THE FIRST
  36. ) AMENDED COMPLAINT
  37. 24 Defendants. )
  38. ) Date: February 9, 2018
  39. 25 ) Time: 9:30 a.m.
  40. ) Courtroom: 8C
  41. )
  42. )
  43. )
  44. )
  45.  
  46.  
  47.  
  48.  
  49. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 2 of 30 Page ID #:246
  50.  
  51. 1 TABLE OF CONTENTS
  52. 2 TABLE OF CONTENTS ............................................................................................ i
  53. 3 TABLE OF AUTHORITIES ....................................................................................iii
  54. 4 PRELIMINARY STATEMENT ............................................................................... 1
  55. 5 SUMMARY OF ARGUMENT ................................................................................. 2
  56. 6 ARGUMENT ............................................................................................................. 4
  57. 7 I. THE MOTION IGNORES
  58. SEVERAL OF THE CLAIMS STATED ............................................. 4
  59. 8
  60. II. CRYTEK HAS PLEADED
  61. 9 CLAIMS FOR BREACH OF CONTRACT ......................................... 6
  62. 10 A. BOTH CIG AND RSI ARE BOUND BY THE GLA ................ 6
  63. 11 1. RSI Is Identified As
  64. A "Licensee" In Exhibit 4 To The GLA ........................... 6
  65. 12
  66. 2. RSI Accepted The Terms
  67. 13 Of The GLA By Its Conduct ............................................ 7
  68. 14 3. If RSI Is Not A Party To The GLA,
  69. Then Crytek's Claims For Copyright
  70. 15 Infringement Are Even Stronger ...................................... 8
  71. 16 B. DEFENDANTS BREACHED
  72. THE GLA IN NUMEROUS WAYS .......................................... 8
  73. 17
  74. 1. The GLA Requires Defendants To Develop
  75. 18 Star Citizen "Exclusively" Using CryEngine ................... 8
  76. 19 2. The GLA Is A License For
  77. Only One Game, Yet Defendants Used
  78. 20 CryEngine To Develop Two Games .............................. 11
  79. 21 3. The GLA Requires Defendants To
  80. Display Crytek's Trademark and Copyright Notices ..... 13
  81. 22
  82. C. CRYTEK IS ENTITLED TO DAMAGES
  83. 23 FOR DEFENDANTS' BREACHES OF THE GLA ................ 14
  84. 24 1. The GLA Does Not Preclude
  85. Contract Claims for Damages ........................................ 14
  86. 25
  87. 2. Crytek Alleged Factual Bases For Its Damages ............. 18
  88. III. CRYTEK HAS SUFFICIENTLY PLEADED
  89. ITS CLAIMS FOR COPYRIGHT INFRINGEMENT ....................... 19
  90. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 3 of 30 Page ID #:247
  91.  
  92. 1 IV. NONE OF THE REMEDIES
  93. THAT CRYTEK SEEKS ARE BARRED ......................................... 20
  94. 2
  95. V. DEFENDANTS' MOTION TO STRIKE SHOULD BE DENIED .... 22
  96. 3
  97. CONCLUSION ........................................................................................................ 25
  98. 4
  99.  
  100. 5
  101. 6
  102. 7
  103. 8
  104. 9
  105. 10
  106. 11
  107. 12
  108. 13
  109. 14
  110. 15
  111. 16
  112. 17
  113. 18
  114. 19
  115. 20
  116. 21
  117. 22
  118. 23
  119. 24
  120. 25
  121. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 4 of 30 Page ID #:248
  122.  
  123. 1 TABLE OF AUTHORITIES
  124. 2 CASES
  125. 3 In re 2TheMart.com Sec. Litig.,
  126. 4 114 F. Supp. 2d 955 (C.D. Cal. 2000) .............................................................. 24
  127. 5 Applied Equipment Corp. v. Litton Saudi Arabia Ltd.7 Cal. 4th 503, 869 P.2d 454 (1994) ................................, ................................ 16
  128. 6 Beijing Zhongyi Zhongbiao Electronic Information Technology Co. v.
  129. 7 Microsoft Corp.No. C13-1300-MJP, 2013 WL 6979555 (W.D. Wash. Oct. 31, 2013), ............ 20
  130. 8 Comer v. Micor, Inc.,
  131. 9 436 F.3d 1098 (9th Cir. 2006) ............................................................................ 8
  132. 10 Delgado v. MillerCoors LLCNo. CV 16-5241 DMG (ASx), 2017 WL 1130165,
  133. 11 (C.D. Cal. Mar. 16, 2017) ................................................................................... 4
  134. 12 Emeryville Redevelopment Agency v. Harcros Pigments, Inc.101 Cal. App. 4th 1083 (2002) ................................................................, ... 12, 13
  135. 13 Erlich v. Menezes,
  136. 14 21 Cal. 4th 543, 981 P.2d 978 (1999) .............................................................. 16
  137. 15 Fantasy, Inc. v. Fogerty984 F.2d 1524 (9th Cir. , 1993) .......................................................................... 24
  138. 16 Fleischer v. A.A.P., Inc.,
  139. 17 180 F. Supp. 717 (S.D.N.Y. 1959) ................................................................... 25
  140. 18 Foley v. Interactive Data Corp.47 Cal. 3d 654, 765 P.2d 373 (1988), ................................................................ 17
  141. 19 Freeman & Mills, Inc. v. Belcher Oil Co.,
  142. 20 11 Cal. 4th 85, 900 P.2d 669 (1995) ................................................................ 17
  143. 21 Gssime v. Nassau CouNo. 09-cv-5581 nty(JS)(ARL, ), 2014 WL 810876 (E.D.N.Y. Feb. 28, 2014) ...... 25
  144. 22 Guardian Media Technologies, Ltd. v. Sears, Roebuck & Co.,
  145. 23 No. 14(C.D. Cal. July 9, -cv-767 PSG (PLAx), 2014 WL 2014) ................................12588283................................ .................... 12
  146. 24 Guillot-Vogt Associates, Inc. v. Holly & Smith,
  147. 25 848 F. Supp. 682 (E.D. La. 1994) .................................................................... 22
  148. Hernandez v. Monsanto Co.,
  149. No. CV 16-1988-DMG (Ex), 2016 WL 6822311
  150. (C.D. Cal. July 12, 2016) .................................................................................... 4
  151. Long v. Authentic Athletix LLC,
  152. No. 16-cv-03129-JSC, 2017 WL 6493094 (N.D. Cal. Dec. 19, 2017) .............. 8
  153. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 5 of 30 Page ID #:249
  154.  
  155. 1 MDY Industries, LLC v. Blizzard Entertainment, Inc.,
  156. 629 F.3d 928 (9th Cir. 2010) ............................................................................ 19
  157. 2
  158. Minden Pictures, Inc. v. John Wiley & Sons, Inc.,
  159. 3 795 F.3d 997 (9th Cir. 2015) ............................................................................ 11
  160. 4 Oasis West Realty, LLC v. Goldman,
  161. 51 Cal. 4th 811, 250 P.3d 1115 (2011) .............................................................. 6
  162. 5
  163. Range Road Music, Inc. v. East Coast Foods, Inc.,
  164. 6 668 F.3d 1148 (9th Cir. 2012) .......................................................................... 19
  165. 7 Riedel v. JP Morgan Chase Bank, N.A.,
  166. No. EDCV 13-01146-VAP (SPx), 2015 WL 12657068
  167. 8 (C.D. Cal. Apr. 3, 2015) ................................................................................... 22
  168. 9 Russell v. Union Oil Co. of California,
  169. 7 Cal. App. 3d 110 (1970) .................................................................................. 8
  170. 10
  171. Saregama India Ltd. v. Young,
  172. 11 No. CV 0219856 RJK, 2003 WL 25769784 (C.D. Cal. Mar. 11, 2003) ......... 22
  173. 12 Slottow v. American Casualty Co. of Reading, Pa.,
  174. 10 F.3d 1355 (9th Cir. 1993) ............................................................................ 22
  175. 13
  176. Survivor Prods., LLC v. Fox Broad. Co.,
  177. 14 No. 01-cv-3234, 2001 WL 35829267 (C.D. Cal. June 12, 2001) .................... 24
  178. 15 Washington Mutual Finance Group, LLC v. Bailey,
  179. 364 F.3d 260 (5th Cir. 2004) .............................................................................. 8
  180. 16
  181. STATUTES
  182. 17
  183. 18 17 U.S.C. § 106 ........................................................................................................... 19
  184. 19 17 U.S.C. § 504(c)(2) .................................................................................................. 22
  185. 20 Cal. Civ. Code § 1641 ............................................................................................. 9, 14
  186. 21 Cal. Civ. Code § 1647 ................................................................................................. 24
  187. 22 Cal. Civ. Code § 1655 ................................................................................................. 13
  188. 23
  189. 24
  190. 25
  191.  
  192. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 6 of 30 Page ID #:250
  193.  
  194. PRELIMINARY STATEMENT
  195. Defendants' Motion seeking dismissal and other relief is without merit. Rather, that Motion is a blatant effort to impose delay and burden on Crytek as it seeks to vindicate its rights under its contract with Defendants and its copyrights.
  196. The facts here are straightforward: Plaintiff Crytek GmbH ("Crytek") granted Cloud Imperium Games Corp. ("CIG") and Roberts Space Industries Corp. ("RSI") (collectively, "Defendants") a license to use Crytek's powerful video game development platform, CryEngine, in the development of Defendants' video game called "Star Citizen." Pursuant to that Game License Agreement (the "GLA"), Crytek agreed to provide technical support and know-how to Defendants and licensed CryEngine to Defendants at a discounted rate, in return for certain promises from Defendants.
  197. But after accepting Crytek's assistance — and after raising record-breaking amounts from video game consumers in a crowdfunding campaign — Defendants began to break their promises to Crytek:
  198. • Defendants promised that they would develop Star Citizen with CryEngine, not any other development platform. But Defendants now boast that they have breached that promise, and are promoting a competing development platform.
  199. • Defendants promised that they would prominently display Crytek's copyright notices and trademarks both within Star Citizen and in any marketing materials for Star Citizen. But Defendants have admittedly breached that promise.
  200. • Even though Defendants had licensed Crytek's technology to develop only one game (Star Citizen), they later separated Star Citizen's feature "Squadron 42" into a standalone game without obtaining a license to use Crytek's technology in two games.
  201.  
  202. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 7 of 30 Page ID #:251
  203.  
  204. 1 • Defendants promised to provide Crytek with any improvements or 2 bug fixes that they made to CryEngine while developing Star
  205. 3 Citizen. Defendants never made a good faith effort to honor that
  206. 4 promise.
  207. 5 • Defendants promised that they would maintain the confidentiality of 6 Crytek's valuable technology. But they published excerpts of
  208. 7 Crytek's source code unilaterally and shared Crytek's technology 8 with a third-party developer without obtaining Crytek's approval.
  209. 9 Defendants say this action never should have been filed. Indeed, if only they 10 had kept their promises, the action never would have been filed. But now that 11 Crytek seeks to enforce its contractual rights and copyrights, Defendants deny 12 having any enforceable obligation to Crytek and move the Court to dismiss Crytek's 13 claims in their entirety. Defendants' arguments simply do not withstand scrutiny, 14 and certainly cannot meet the demanding standard required to obtain dismissal of 15 Crytek's claims as a matter of law. The Court should deny Defendants' Motion and 16 permit Crytek to proceed so that it may vindicate its rights.
  210. 17 SUMMARY OF ARGUMENT
  211. 18 Crytek has sufficiently stated claims for both breach of contract and copyright 19 infringement. Defendants' motion to dismiss should be denied.
  212. 20 As a preliminary matter, Defendants seek dismissal of Crytek's First Amended
  213. 21 Complaint in its entirety, but that Complaint alleges numerous breaches of contract 22 and copyright infringement that Defendants' motion does not address at all.
  214. 23 Defendants have proffered no basis to dismiss those aspects of Crytek's claims.
  215. 24 The arguments that Defendants do make are unpersuasive:
  216. 25 First, with regard to Crytek's claims for breach of contract, RSI is bound by the GLA for several reasons, including that (i) RSI is a signatory to at least one portion of the GLA; (ii) RSI has accepted the contract by its conduct; and (iii) RSI is equitably estopped from arguing that it is not bound by the GLA. If RSI is deemed
  217. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 8 of 30 Page ID #:252
  218.  
  219. 1 not to be bound by the GLA, however, Defendants' infringement of Crytek's 2 copyrights is even more pervasive. Defendants' claim that their conduct was 3 authorized by the GLA conflicts with the GLA's plain terms providing that
  220. 4 Defendants were required to use CryEngine exclusively, were required to promote 5 Crytek by prominently displaying its copyright notices and trademarks, and were
  221. 6 licensed to develop only one standalone game, not two. Defendants' contention that
  222. 7 the GLA does not permit damages for intentional breaches of its terms — thereby 8 rendering the entire GLA unenforceable and illusory — is contrary to both common 9 sense and the express terms of the GLA.
  223. 10 Second, with regard to Crytek's claims for copyright infringement, Defendants 11 argue that the GLA authorized their use of CryEngine to develop Squadron 42. That 12 is incorrect because the GLA authorized development of only one game, Star
  224. 13 Citizen, not two games. Defendants further argue that having breached the GLA by
  225. 14 embedding a different engine in place of CryEngine, they can no longer be held 15 liable for copyright infringement. This argument ignores both the pervasive 16 copyright infringement that took place before Defendants breached the exclusivity
  226. 17 requirement of the GLA and Crytek's allegations that Defendants' infringement is in 18 fact ongoing. In any event, Defendants' bare assertion that they "are not using any 19 copyrighted work belonging to Crytek" (Defts.' Br. at 15) presents a disputed factual 20 question that cannot be resolved on a motion to dismiss.
  227. 21 Defendants' motion to strike should also be denied. Defendants seek to strike
  228. 22 certain portions of an allegation that sets forth information concerning Ortwin 23 Freyermuth, one of Defendants' founders, who negotiated the GLA on Defendants'
  229. 24 behalf notwithstanding having previously served as counsel for Crytek. The
  230. 25 allegation also informs the Court that the person who negotiated the GLA on behalf of Crytek is now employed by Defendants. All of that information may become relevant if the Court were to hold that there are ambiguous provisions of the GLA such that the finder of fact must review the negotiations of the GLA to construe it.
  231. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 9 of 30 Page ID #:253
  232.  
  233. 1 ARGUMENT1
  234. 2 I. THE MOTION IGNORES SEVERAL OF THE CLAIMS STATED
  235. 3 Defendants' Motion simply does not address several of Crytek's theories of 4 liability, which precludes dismissal of those aspects of Crytek's claims.
  236. 5 First, pursuant to Section 7.3 of the GLA, Defendants were required to
  237. 6 provide Crytek with any bug fixes and optimizations made to CryEngine.2 This
  238. 7 "Reverse Technology Transfer" entailed granting Crytek "a non-exclusive, royalty8 free and perpetual license" to use any such bug fixes or optimizations internally at
  239. 9 Crytek, incorporate them into future releases of CryEngine, and distribute them to 10 third parties. (GLA § 7.3 (Goldman Decl. Ex. A, ECF No. 20-3).) Indeed,
  240. 11 Defendants have publicly claimed to have made extensive optimizations to
  241. 12 CryEngine. (See, e.g., Christopher Roberts, Lumberyard for those interested…, RSI
  242. 13 Community Forums (Dec. 2016), https://forums.robertsspaceindustries.com/
  243. 14 discussion/364217 ("We stopped taking new builds from Crytek towards the end of
  244. 15
  245. 16 1 Crytek will not belabor the standards for resolving motions to dismiss and motions to strike, with which this Court is well familiar. E.g., Hernandez v.
  246. 17 Monsanto Co., No. CV 16-1988-DMG (Ex), 2016 WL 6822311, at *2 (C.D. Cal.
  247. 18 July 12, 2016)accepted as true, to state a claim to relief that is plausible on its face.") (internal ("A plaintiff's complaint must contain sufficient factual matter,
  248. 19 quotation marks and citations omitted); Delgado v. MillerCoors LLC, No. CV 16-
  249. 5241 DMG (ASx), 2017 WL 1130165, at *3-4 (C.D. Cal. Mar. 16, 2017) ("As a
  250. 20 general matter, motions to strike are disfavored and are generally not granted unless it is clear that the matter to be stricken could have no possible bearing on the subject 21 matter of litigation.") (same).
  251. 22 2 Defendants suggest that the Court should draw negative inferences from the
  252. 23 fact that Crytek did not file the GLA as an exhibit to its initial and amended complaints. (E.g., Defts.' Br. at 1-2 (accusing Crytek of "conceal[ing]" the GLA
  253. 24 from the Court by "deliberately omitt[ing]" and "hiding" the GLA); id. at 9
  254. (describing the GLA as "the hidden document"); id. at 18 (arguing that "the entire
  255. 25 FAC should be dismissed for failure to state a claim particularly given the lack of candor by Crytek regarding the GLA."). The GLA contains sensitive business information concerning Crytek's licensing practices and Crytek was not obliged to attach it to a public filing. In any event, the terms of the GLA contradict Defendants' contentions here.
  256. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 10 of 30 Page ID #:254
  257.  
  258. 1 2015. . . . What runs Star Citizen and Squadron is our heavily modified version of 2 the engine which we have dubbed StarEngine.") (emphasis added); (see also First 3 Amended Complaint ("FAC") ¶ 33 (ECF No. 18) (quoting Roberts's statement that 4 "[W]e don't call [the video game engine] CryEngine anymore, we call it Star 5 Engine.").) Yet Defendants repeatedly refused to substantively provide 6 optimizations or bug fixes to Crytek. (Id. ¶¶ 42-44.) Those refusals flouted their
  259. 7 obligations: Defendants gladly accepted Crytek's technical support and discounted 8 license to use CryEngine, but breached their obligation to provide any technical 9 advances back to Crytek.
  260. 10 Second, Sections 2.2.1 and 2.2.2 of the GLA require Defendants to maintain
  261. 11 the confidentiality of Crytek's technology, forbidding Defendants from "publish[ing] 12 or distribut[ing] the CryEngine in any way, be it in source code or object code," and 13 further requiring that Defendants shall not "use CryEngine in any manner which may
  262. 14 disclose the CryEngine source code or other Crytek proprietary information to any
  263. 15 third party not otherwise authorized herein." (Id. ¶¶ 46-48.) Here, notwithstanding 16 their obligation to protect Crytek's valuable software, Defendants repeatedly publicly 17 exposed confidential CryEngine technology including source code to the general
  264. 18 public in a series of "Bugsmashers" videos posted online. (Id. ¶ 50.) This public 19 display breached Sections 2.2.1 and 2.2.2 and was also an infringing publication of 20 Crytek's copyrighted source code.
  265. 21 Third, although Section 2.6 of the GLA permits Defendants to "sub-contract 22 the development of the Game to one or more third party developer(s)," that
  266. 23 permission is expressly made "subject to prior written approval of the developer by 24 Crytek" and "execution of the necessary non-disclosure and non-competition
  267. 25 agreements by and between such developer and Crytek." Yet Defendants have partnered with third-party developer Faceware Technologies without obtaining
  268. Crytek's approval and, upon information and belief, have provided Faceware access
  269. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 11 of 30 Page ID #:255
  270.  
  271. 1 to Crytek's technology including source code. (FAC ¶ 51.) This breach of the GLA 2 also entails an infringing distribution of Crytek's copyrighted source code.
  272. 3 Defendants' Motion does not address any of these breaches of the GLA or
  273. 4 infringement of Crytek's copyrights, aside from Defendants' generalized (and
  274. 5 incorrect) arguments concerning the remedies sought by Crytek, which are addressed 6 below. For that reason alone, the Court should not dismiss either count of Crytek's 7 First Amended Complaint.
  275. 8 II. CRYTEK HAS PLEADED CLAIMS FOR BREACH OF CONTRACT
  276. 9 To state a claim for breach of contract, Crytek must allege that a contract 10 exists (here, the GLA), that Crytek performed its obligations under the GLA, that
  277. 11 Defendants breached the GLA, and that those breaches caused damages to Crytek.
  278. 12 E.g., Oasis W. Realty, LLC v. Goldman, 51 Cal. 4th 811, 821, 250 P.3d 1115, 1121
  279. 13 (2011). Crytek has alleged each and every one of those required elements. (E.g.,
  280. 14 FAC ¶¶ 53-60.) Defendants do not contest that a contract exists between Crytek and 15 CIG or that Crytek performed its obligations, but instead contend that RSI is not 16 bound by the GLA, that no breaches occurred, and that Crytek cannot recover 17 damages. All of those contentions are incorrect.
  281. 18 A. BOTH CIG AND RSI ARE BOUND BY THE GLA
  282. 19 Defendants argue that Crytek cannot maintain a claim for breach of contract 20 against CIG's subsidiary RSI because RSI is not a signatory to the main body of the 21 GLA. (Defts.' Br. at 6-7 (ECF No. 20-2).) But the First Amended Complaint alleges 22 several reasons to conclude that RSI is bound by the GLA:
  283. 23 1. RSI Is Identified As A "Licensee" In Exhibit 4 To The GLA
  284. 24 Although RSI is not listed in the signature block of the main body, RSI did
  285. 25 sign Exhibit 4 to the GLA as a "Licensee," as that term is defined in the Exhibit (GLA Ex. 4 at 24.) Exhibit 4 is an "End User Licensing Agreement Terms and
  286. Conditions" (abbreviated in the document as "ToC") that applies to "Licensee's use
  287. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 12 of 30 Page ID #:256
  288.  
  289. 1 of Autodesk Materials made available to Licensee under the license agreement 2 ('Agreement') [i.e., the GLA] between Licensee and Crytek."
  290. 3 "Licensee" is defined as "the individual or entity executing this ToC." (GLA
  291. 4 Ex. 4, § 1.4.) The ToC concludes, "Intending to be legally bound to the terms of this
  292. 5 Amendment, each of the parties has caused its duly authorized representative to 6 execute this document." (GLA Ex. 4 at 24.) Defendants' founder and CEO, Chris
  293. 7 Roberts, executed the ToC on behalf of both "Cloud Imperium Games Corporation" 8 and "Roberts Space Industries Corp." Accordingly, as of the signing of the ToC, RSI 9 was a "Licensee."
  294. 10 Defendants cannot be heard to argue that because the ToC is an exhibit, rather
  295. 11 than a section of the main body of the GLA, the Court should disregard the exhibit.
  296. 12 In the main body of the GLA, the parties "acknowledge that the exhibits to this 13 Agreement form a substantial part of this Agreement." (GLA § 10.1.) Exhibit 4 14 further provides that "[i]f any provisions of the Agreement conflict with any of the
  297. 15 provisions of these ToC, the provisions of these ToC prevail." (GLA Ex. 4 at 21)
  298. 16 Accordingly, to the extent that the signature block of the main body of the GLA 17 conflicts with the signature block of the ToC, the ToC prevails, making RSI a
  299. 18 Licensee under the GLA. Even construed most favorably to Defendants, RSI's 19 execution of the ToC would create a factual issue as to which Defendants are parties 20 to the GLA, which could not be resolved on a motion to dismiss.
  300. 21 2. RSI Accepted The Terms Of The GLA By Its Conduct
  301. 22 Even if the Court concludes that RSI's signature on Exhibit 4 of the GLA is
  302. 23 insufficient to bind RSI to that contract, Crytek alleges that RSI accepted the terms 24 of the GLA by its conduct. (FAC ¶ 54.) RSI, not CIG, made the public
  303. 25 announcements and published the content cited in the First Amended Complaint.
  304. (E.g., FAC ¶¶ 22-23, 25-26, 32, 50.) These announcements and publications include Defendants' decision to abandon CryEngine in breach of the GLA, the publication of
  305. Crytek's confidential source code in the "Bugsmashers" video series, and the
  306. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 13 of 30 Page ID #:257
  307.  
  308. 1 distribution of software both with and without Crytek's copyright notices and
  309. 2 trademarks. It is well settled that parties can manifest acceptance of a contract by
  310. 3 their conduct. E.g., Long v. Authentic Athletix LLC, No. 16-cv-03129-JSC, 2017 WL 4 6493094, at *3 (N.D. Cal. Dec. 19, 2017) (citing Russell v. Union Oil Co., 7 Cal. 5 App. 3d 110, 114 (1970) ("Acceptance of an offer . . . may be manifested by conduct 6 as well as by words . . . .")). And Defendants are also equitably estopped from
  311. 7 claiming the benefits of a contract while simultaneously attempting to avoid the 8 burdens that the contract imposes. Comer v. Micor, Inc., 436 F.3d 1098, 1101 (9th 9 Cir. 2006) (quoting Wash. Mut. Fin. Grp., LLC v. Bailey, 364 F.3d 260, 267 (5th Cir. 10 2004)). Here, RSI accepted (and exceeded) the benefits of the GLA by using and 11 publishing Crytek's technology. RSI therefore accepted the GLA and further is 12 equitably estopped from denying that it is bound by that agreement.
  312. 13 3. If RSI Is Not A Party To The GLA, Then Crytek's
  313. Claims For Copyright Infringement Are Even Stronger
  314. 14
  315. 15 Defendants' suggestion that RSI is not bound by the GLA ignores the
  316. 16 implications that holding would have for Crytek's claims of copyright infringement.
  317. 17 If the Court determines that RSI is not bound by the GLA, then RSI was not 18 authorized to obtain Crytek's code: RSI is not included on Exhibit 3 to the GLA, 19 which lists the "[a]uthorized third party developer(s)" who are entitled to receive 20 access to Crytek's technology pursuant to Section 2.6 of the GLA. (GLA Ex. 3 at 21 19.) If RSI is not a party to the GLA, then CIG had no license to distribute Crytek's 22 technology to RSI. And a fortiori, RSI had no license to (for example) publish 23 Crytek's source code through the "Bugsmashers" videos hosted on RSI's web site.
  318. 24 B. DEFENDANTS BREACHED THE GLA IN NUMEROUS WAYS
  319. 25 1. The GLA Requires Defendants To Develop
  320. Star Citizen "Exclusively" Using CryEngine
  321. Crytek began assisting the development of Star Citizen at Defendants' infancy in 2012, when Defendants lacked the resources to develop sufficiently impressive
  322.  
  323. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 14 of 30 Page ID #:258
  324.  
  325. software to attract crowdfunding backers. Crytek stepped in to aid Defendants, creating demonstrations and proofs of concept and otherwise providing technology that enabled Defendants to set crowdfunding records. (FAC ¶¶ 14, 17.)
  326. Shortly after Defendants launched their crowdfunding campaign, Crytek agreed to license CryEngine to Defendants at a below-market rate to continue supporting Defendants' efforts. (Id. ¶ 16.) In return, Defendants promised to develop Star Citizen using CryEngine exclusively. (E.g., id. ¶¶ 36-37.) Years later, beginning in December 2016, Defendants breached that promise by announcing that they intended to use an engine other than CryEngine. (Id. ¶¶ 38-39.)
  327. Defendants correctly recognize that "[t]he whole of a contract is to be taken together, so as to give effect to every part, if reasonably practicable, each clause helping to interpret the other." (Defts.' Br. at 7 (quoting Cal. Civ. Code § 1641).) Yet their argument wholly disregards that principle, relying on two related and false assertions: (1) that Crytek's claim "is based entirely on isolating the word 'exclusively' contained in Section 2.1.2"; and (2) that no other provision of the GLA precluded Defendants from abandoning CryEngine for a competitor's product.
  328. (Defts. Br. at 7-8.)
  329. Section 2.1.2 grants Defendants a license "to exclusively embed CryEngine in the Game." That grant is "[s]ubject to strict and continuous compliance with the restrictions in the Agreement." (GLA § 2.1.) If there is any doubt that Section 2.1.2 prohibits Defendants from developing the Game with engines other than CryEngine, another section of the GLA also makes Defendants' obligation clear. Section 2.4 provides:
  330. During the Term of the License, or any renewals thereof, and for a period of two years thereafter, Licensee, its principals, and Affiliates shall not directly or indirectly engage in the business of designing, developing, creating, supporting, maintaining, promoting, selling or
  331.  
  332. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 15 of 30 Page ID #:259
  333.  
  334. 1 licensing (directly or indirectly) any game engine or middleware 2 which compete with CryEngine.
  335. 3 (Emphasis added.) This section further confirms there is only one reasonable 4 construction of the GLA: that Crytek received exclusivity for Star Citizen (among 5 other things) in return for the license, technical support, and financial discounts that
  336. 6 it provided to Defendants. Thus, even if the Court were to construe Section 2.1.2 to
  337. 7 permit Defendants to abandon CryEngine in favor of another engine — and Crytek 8 respectfully submits that such a construction is inconsistent with the GLA — that
  338. 9 same abandonment and concomitant development, support, maintenance, promotion,
  339. 10 selling, and licensing of that other engine would constitute breaches of Section 2.4.
  340. 11 Indeed, Defendants promoted an alternative engine in breach of Section 2.4 in the
  341. 12 very RSI press release that Defendants themselves submitted with their brief.
  342. 13 (Goldman Decl. Ex. C (quoting Roberts's statement that an alternative engine 14 "provides ground breaking technology features for online games, including deep 15 back-end and cloud integration . . . and its social component . . . that enables us to
  343. 16 easily and instantly connect to millions of global gamers").)
  344. 17 Defendants' interpretation of the word "exclusively" in Section 2.1.2 is that 18 Crytek gave only Defendants — not some unrelated third party — the right to embed 19 CryEngine in Defendants' game Star Citizen. (Defts.' Br. at 9.) That is absurd: How
  345. 20 could Crytek license a third party to do anything at all with Defendants' software?
  346. 21 Defendants admit: "Obviously CIG could never have a document that even remotely 22 suggests Crytek could grant somebody else the right to embed the Engine in the 23 Game." (Id. (emphasis as in original).) Accordingly, Defendants' suggestion that the 24 parties added the word "exclusively" to prevent Crytek from allowing some third 25 party to develop Defendants' software is nonsense.
  347. Defendants cite cases involving other types of exclusivity, but pointedly do not contend that the GLA prohibits Crytek from licensing CryEngine to other parties for use in other games. That is the type of exclusivity at issue in cases such as
  348. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 16 of 30 Page ID #:260
  349.  
  350. 1 Minden Pictures, Inc. v. John Wiley & Sons, Inc., 795 F.3d 997, 1005 (9th Cir. 2015) 2 (describing exclusive licenses where "the copyright holder permits the licensee to 3 use the protected material for a specific use and further promises that the same 4 permission will not be given to others"). Nor could they credibly so contend, given 5 that Defendants' co-founder Ortwin Freyermuth had negotiated licensing agreements 6 on behalf of Crytek before negotiating the GLA, and thus knew full well that
  351. 7 Crytek's business model includes licensing its valuable CryEngine to multiple
  352. 8 developers simultaneously. (FAC ¶ 15.)
  353. 9 The reading of the GLA most favorable to Defendants here — and Crytek 10 submits that such a reading is not at all tenable — would be that the use of the word 11 "exclusively" in the GLA is somehow ambiguous. If that were so, Crytek's claim for 12 breach of the exclusivity provision could not be dismissed now because factual 13 development would be required to determine the parties' intent.
  354. 14 2. The GLA Is A License For Only One Game,
  355. Yet Defendants Used CryEngine To Develop Two Games
  356. 15
  357. 16 Defendants used Crytek's CryEngine to develop two separate games (Star 17 Citizen and Squadron 42) even though Section 2.1.2 of the GLA provides 18 Defendants a license to embed CryEngine in only one game — the "Game" as that 19 term is defined in Section 1.6 and Exhibit 2 of the GLA — and does not permit using 20 CryEngine for any separate standalone game. (E.g., FAC ¶¶ 19-21, 56.)
  358. 21 When the parties negotiated the GLA, Squadron 42 was to be a feature of Star 22 Citizen, not a standalone game. (FAC ¶ 20; GLA Ex. 2 (identifying Squadron 42 as 23 a "[f]eature" of Star Citizen).) Section 1.6 of the GLA states that the "Game" is "the
  359. 24 interactive software product developed and published for the certain platforms as
  360. 25 further defined in Exhibit 2." In turn, Exhibit 2 states, "For the avoidance of doubt, the Game does not include any content being sold and marketed separately, and not being accessed through the Star Citizen Game client." (GLA Ex. 2 at 18 (emphasis
  361. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 17 of 30 Page ID #:261
  362.  
  363. 1 added).) The "doubt" that the parties expressly sought to avoid when they negotiated 2 the GLA is exactly the doubt that Defendants seek to manufacture and rely on now.
  364. 3 Years after the parties entered into the GLA, Defendants chose to develop
  365. 4 Squadron 42 as a standalone game, separate from Star Citizen. (FAC ¶¶ 15, 22-23.)
  366. 5 But Defendants never obtained a license to embed CryEngine in the standalone 6 Squadron 42. (FAC ¶¶ 24-27.) Defendants' development of a standalone Squadron 7 42 with CryEngine thus exceeded the license granted by the GLA.
  367. 8 Defendants mischaracterize the GLA with their assertions that "the GLA
  368. 9 expressly defines the 'Game' as including both Star Citizen and Squadron 42."
  369. 10 (Defts.' Br. at 11; see also id. at 2, 3, 15.) The portion of the GLA that Defendants 11 quote does not provide a definition for "Game": that portion is a recital that precedes 12 the body of the GLA. (GLA at 2.) The definition of "Game" — singular, not 13 plural — set forth later, in the "Definitions" section of the GLA, utterly refutes 14 Defendants' contention that the GLA provided Defendants a license to develop two
  370. 15 separate games with CryEngine. (GLA § 1.6 & Ex. 2.)
  371. 16 Defendants urge the Court to hold that the recital "defines" the term "Game,"
  372. 17 even though there is an actual definition of that term in the GLA that conflicts with 18 Defendants' proposed definition. The GLA is clear, and even if it were not, it is well 19 settled that if a contract's prefatory recitals and the contractual provisions themselves 20 are incompatible, the contractual provisions will control. For example, in Guardian 21 Media Technologies, Ltd. v. Sears, Roebuck & Co., No. 14-cv-767 PSG (PLAx), 22 2014 WL 12588283 (C.D. Cal. July 9, 2014), the court construed a contract where 23 one party contended that prefatory recitals should control. Id. at *7. The court 24 recognized, "As California courts routinely proclaim, '[t]he law has long
  373. 25 distinguished between a "covenant" which creates legal rights and obligations, and a "mere recital" which a party inserts for his or her own reasons into a contractual instrument.'" Id. (quoting Emeryville Redevelopment Agency v. Harcros Pigments,
  374. Inc., 101 Cal. App. 4th 1083, 1101 (2002)). Accordingly, the court "refuse[d] to
  375. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 18 of 30 Page ID #:262
  376.  
  377. 1 allow the [recital at issue], or any other introductory recital, to deracinate the plain 2 meaning of the [agreement]." Id. The Emeryville court similarly noted, "Recitals are 3 given limited effect even as between the parties." 101 Cal. App. 4th at 1101.
  378. 4 Here, the GLA provided Defendants with a license to develop only one game
  379. 5 with CryEngine. When Defendants elected to split "the Game" into two games, each 6 one embedding CryEngine, they should have obtained an appropriate license. And
  380. 7 even read most favorably to Defendants — a reading that is not at all tenable —
  381. 8 Defendants have at best identified an ambiguous term in the GLA that would require 9 factual development to resolve. Crytek's claim for breach of this provision therefore 10 could not be dismissed as a matter of law in any event.
  382. 11 3. The GLA Requires Defendants To Display
  383. Crytek's Trademark and Copyright Notices
  384. 12
  385. 13 Pursuant to Sections 2.8.1, 2.8.2, and 2.8.3 of the GLA, Defendants are 14 required to prominently display Crytek's copyright notices and trademarks in Star 15 Citizen's splash screen, credits screen, documentation, packaging, and marketing 16 materials, and are required to obtain Crytek's written approval before making any
  386. 17 changes to their use of Crytek's copyright notices and trademarks. (FAC ¶¶ 28-31.)
  387. 18 Yet Defendants ceased displaying Crytek's copyright notices and trademarks without 19 seeking Crytek's approval — going so far as to claim, "We don't call [the video game 20 engine] CryEngine anymore, we call it Star Engine." (Id. ¶¶ 33-34.)
  388. 21 Defendants acknowledge that they ceased including Crytek's copyright notices
  389. 22 and trademarks but nevertheless assert that they were entitled to cease doing so after
  390. 23 they purportedly ceased using CryEngine. (Defts.' Br. at 10.) Defendants' only 24 support for that proposition is Cal. Civ. Code § 1655, which concerns "implied"
  391. 25 provisions. That statute, the relevant portion of which Defendants quote, applies only "in respect to matters concerning which the contract manifests no contrary intention." Id. The statute has no application here: Section 2.4 of the GLA, which prohibited Defendants' switch to an alternative engine in the first place, also squarely
  392.  
  393. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 19 of 30 Page ID #:263
  394.  
  395. prohibits the promotion of other engines via Star Citizen's splash screen, marketing materials, or any other medium. By its terms, Section 2.4 remains in effect for two years after the termination of the GLA (an event that has not yet occurred).
  396. Defendants assert that displaying Crytek's copyright notices and trademarks "would misrepresent reality and could mislead that CIG is using Crytek's engine when it is not." (Id.) But even if Defendants were contractually permitted to remove CryEngine from Star Citizen — they were not — Crytek's technology would remain foundational to Defendants' software. The prohibition on promoting competing game engines or middleware for two years after the expiration of the GLA, along with Crytek's contractual right to approve the "design of the splash screen, the credits screen, the documentation, the packaging and the marketing material" (GLA §§ 2.4, 2.8.3), forbid Defendants from unilaterally removing Crytek's copyright notices and trademarks as they did. (FAC ¶¶ 33-34.)
  397. C. CRYTEK IS ENTITLED TO DAMAGES FOR DEFENDANTS' BREACHES OF THE GLA
  398. 1. The GLA Does Not Preclude Contract Claims for Damages
  399. Quoting only a portion of Section 6.1.4 of the GLA, Defendants suggest that
  400. Crytek's claim for breach of contract is barred by that section. (Defts.' Br. at 12-14.) But Section 6.1.4, interpreted as a whole as it must be, does not support that construction. Cal. Civ. Code § 1641 ("The whole of a contract is to be taken together, so as to give effect to every part, if reasonably practicable, each clause helping to interpret the other."). Defendants' proposal would make other portions of the same section superfluous and, taken to its logical conclusion, would render all of the GLA's obligations illusory with no means to enforce them.
  401. In particular, Section 6.1.4 provides that intentional or grossly negligent breaches, as opposed to negligent breaches, can give rise to liability for damages in actions for breach of contract. (GLA § 6.1.4.) The section further limits Crytek's liability to Defendants, even in the event of intentional or grossly negligent breaches,
  402. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 20 of 30 Page ID #:264
  403.  
  404. to the amount Defendants paid for the license. (Id.) There is no parallel limitation on Defendants' liability to Crytek for Defendants' intentional or grossly negligent breaches. (Id.) That section, in its entirety, provides:
  405. Indemnification disclaimer. Except for intentional acts or omissions or gross negligent acts, in no event shall either party hereto be liable for any damages, including but not limited to indirect, incidental, special or consequential damages, or damages for loss of profits, revenue, data or use, incurred by either party or any third party, whether in an action in contract or tort (including negligence) or otherwise, even if the relevant party has been advised of the possibility of such damages. Crytek's maximum aggregate liability to Licensee in connection with or in any manner related to this agreement (whether in an action in contract or tort [including negligence, except gross negligence] or otherwise) will be limited to the total amount paid by or on behalf of Licensee to Crytek under this agreement. The foregoing allocation of risk is reflected in the amount of the compensation contemplated under this agreement.
  406. (Id. (emphasis added). )
  407. Defendants' argument addresses only the first sentence of Section 6.1.4. (Defts.' Br. at 12-13.) But if the parties could never bring any action for intentional breaches of contract, then the second sentence of Section 6.1.4 — which limits Crytek's maximum aggregate liability to Defendants "in connection with or in any manner related to this Agreement (whether in an action in contract or tort . . . or otherwise)" (emphasis added) — would be surplusage. Under Defendants' proposed reading, Crytek's maximum liability for contract claims would be zero, not "the total
  408.  
  409. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 21 of 30 Page ID #:265
  410.  
  411. 1 amount paid by or on behalf of licensee to Crytek under this agreement." (GLA
  412. 2 § 6.1.4.) (Again, there is no such limitation on Defendants' liability.)
  413. 3 Defendants' interpretation would also require the Court to entertain the
  414. 4 dubious assumption that the parties negotiated and executed a detailed twenty-four5 page agreement intending that no party could ever actually enforce that agreement by 6 seeking damages for breach. The Court should not accept a construction that would 7 make the entire GLA illusory.
  415. 8 Defendants cite a number of cases distinguishing generally between tort and
  416. 9 contract law, but none of those cases involve contracts, like the GLA, that
  417. 10 differentiate between remedies available for intentional or grossly negligent breaches
  418. 11 of contract, on one hand, and negligent breaches, on the other. For example, in 12 Erlich v. Menezes, the plaintiffs had contracted with the defendant, a licensed general 13 contractor, to build a "dreamhouse." 21 Cal. 4th 543, 548, 981 P.2d 978, 980-81 14 (1999). The contractor did a very bad job on the house: for example, "[t]hree decks 15 were in danger of 'catastrophic collapse.'" Id. at 549, 981 P.2d at 981. The plaintiffs 16 testified that they suffered emotional distress as a result of the defective condition of
  419. 17 the house and the defendant's botched efforts at repair, and the jury awarded them 18 damages for those tortious injuries over and above the sum awarded for breach of 19 contract. Id. The court noted that tort remedies are available for negligent breaches 20 of contract "only when the conduct in question is so clear in its deviation from 21 socially useful business practices that the effect of enforcing such tort duties will
  420. 22 be . . . to aid rather than discourage commerce." Id. at 554, 981 P.2d at 985 (citation 23 omitted). Erlich is not applicable here because Crytek does not seek tort remedies 24 for Defendants' breaches of contract.
  421. 25 Nor are any of the other cases that Defendants cite applicable — all of them 26 involve plaintiffs who sought tort remedies for contractual breaches, and none of 27 them involve contracts where the parties agreed to permit liability only for
  422. 28 intentional or grossly negligent breaches of contract. In Applied Equipment Corp. v.
  423. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 22 of 30 Page ID #:266
  424.  
  425. 1 Litton Saudi Arabia Ltd., 7 Cal. 4th 503, 869 P.2d 454 (1994), the court held that a
  426. 2 party could not be held liable in tort for conspiring to interfere with its own contract.
  427. 3 Id. at 510, 869 P.2d at 456-57. Likewise, in Foley v. Interactive Data Corp., 47 Cal. 4 3d 654, 699, 765 P.2d 373, 400-401 (1988), the court held that a plaintiff could not
  428. 5 obtain tort remedies for the breach of the implied covenant of good faith and fair
  429. 6 dealing in an employment contract. Finally, in Freeman & Mills, Inc. v. Belcher Oil
  430. 7 Co., 11 Cal. 4th 85, 102-03, 900 P.2d 669 (1995) the court held that a plaintiff could
  431. 8 not obtain tort remedies for a defendant's bad-faith denial that a contract existed.4
  432. 9 Here, Crytek does not seek tort remedies for Defendants' breaches of contract.
  433. 10 Rather, Crytek seeks to recover damages for Defendants' intentional breaches of
  434. 11 contract, just as Section 6.1.4 contemplates. The First Amended Complaint alleges 12 numerous instances of intentional breaches that give rise to Defendants' liability:
  435. 13 • On February 14, 2016, Defendants moved forward with their plan
  436. 14 for Squadron 42, notwithstanding their failure to obtain a license,
  437. 15 and began offering the video game for separate purchase.
  438. 16 Defendants are thus intentionally and willfully using CryEngine 17 without a license and in violation of copyright laws. (FAC ¶ 25.)
  439. 18 • Defendants intentionally breached the GLA by using CryEngine to 19 market, develop, and incentivize funding for more than one game, 20 thereby enriching themselves by millions of dollars without payment 21 for such use. (Id. ¶ 56.)
  440. 22 • Defendants intentionally breached the GLA by refusing to provide
  441. 23 agreed-upon bug fixes and optimizations to CryEngine. (Id. ¶ 57.)
  442. 24
  443. 25 4 Defendants rely on Justice Holmes's remark, quoted in a concurring and
  444. 26 dissenting opinion in Freeman, that entering into a contract "means a prediction that you must pay damages if you do not keep it." 11 Cal. 4th at 106. Here, Defendants
  445. 27 make the remarkable argument that notwithstanding having intentionally breached the GLA they could never be required to pay any damages at all. (Defts.' Br. at 13.)
  446. 28
  447.  
  448. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 23 of 30 Page ID #:267
  449.  
  450. • Defendants intentionally breached the GLA by, among other things, removing Crytek's trademarks and copyright notices from the Star Citizen video game and related marketing materials. (Id. ¶ 58.)
  451. • Defendants intentionally breached the GLA by breaking their promise to exclusively use CryEngine in the Star Citizen video game. (Id. ¶ 59.)
  452. Section 6.1.4 does not preclude Crytek from recovering damages for Defendants' intentional breaches — indeed, it plainly permits those claims for damages.
  453. 2. Crytek Alleged Factual Bases For Its Damages
  454. Defendants suggest that Crytek's damages are alleged in a conclusory manner that does not sufficiently demonstrate the basis for Crytek's claims. (See, e.g., Defts.' Br. at 14 & n.4 (accusing Crytek of pleading "damages referenced vaguely but repeatedly").) Defendants' misleadingly selective quotations aside, the First Amended Complaint alleges several specific forms of damages, including:
  455. (1) The up-front payment and royalty on game sales that Crytek did not receive when Defendants separated Star Citizen and Squadron 42 into two separate games (FAC ¶ 27);
  456. (2) The amount by which Crytek discounted its CryEngine license in return for Defendants' now-broken promises to include Crytek's trademarks and copyright notices on the Star Citizen video game and related marketing materials (id. ¶ 35);
  457. (3) The financial benefits of the favorable attention that the parties anticipated Crytek would receive for Defendants' exclusive use of CryEngine, which will now accrue to another engine's owner rather than to Crytek (id. ¶ 39);
  458. (4) The value of the bug fixes and optimizations to CryEngine that Defendants were obligated to provide under Section 7.3 of the
  459. GLA (id. ¶ 45); and
  460.  
  461. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 24 of 30 Page ID #:268
  462.  
  463. 1 (5) All of the gains, profits, and advantages that Defendants have 2 obtained by infringing Crytek's copyrights (id. ¶ 70).
  464. 3 Those allegations provide ample notice of the nature of Crytek's damages claim.
  465. 4 III. CRYTEK SUFFICIENTLY PLEADED
  466. ITS CLAIMS FOR COPYRIGHT INFRINGEMENT
  467. 5
  468. 6 To plead its claim for copyright infringement, Crytek has alleged "ownership
  469. 7 of a valid copyright" and "copying of constituent elements of the work that are 8 original," where the word "copying" is a shorthand for any of the copyright owner's
  470. 9 exclusive rights set forth in 17 U.S.C. § 106 (e.g., the exclusive rights to reproduce,
  471. 10 distribute, and perform the copyrighted work and to prepare derivative works).5 11 Range Road Music, Inc. v. E. Coast Foods, Inc., 668 F.3d 1148, 1153-54 (9th Cir. 12 2012). As the Ninth Circuit has observed, "[t]o recover for copyright infringement 13 based on breach of a license agreement, (1) the copying must exceed the scope of the 14 defendant's license and (2) the copyright owner's complaint must be grounded in an 15 exclusive right of copyright." MDY Indus., LLC v. Blizzard Entm't, Inc., 629 F.3d 16 928, 940 (9th Cir. 2010). Defendants' Motion fails to offer any basis on which the 17 Court might dismiss Crytek's claim for copyright infringement.6
  472. 18 First, as noted above, the operative complaint includes several allegations of 19 copyright infringement that Defendants' Motion does not address. These allegations 20 include Defendants' infringing publication of Crytek's source code and distribution of 21 CryEngine to an unauthorized third party. See supra Part I.
  473. 22
  474.  
  475. 23
  476. 5 Defendants do not dispute that Crytek owns a valid copyright in its CryEngine
  477. 24 computer program. (FAC ¶ 62.)
  478. 25 6 Defendants' Notice of Motion states that Crytek's "claims for copyright
  479. 26 infringement are so vague and ambiguous that Defendants cannot reasonably prepare a response." (ECF No. 20-1 at 1.) That argument is neither made nor developed in
  480. 27 Defendants' brief, but in any event, the First Amended Complaint contains numerous
  481. specific allegations of infringement.
  482. 28
  483.  
  484. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 25 of 30 Page ID #:269
  485.  
  486. 1 Second, Defendants reiterate their argument that the GLA authorized them to
  487. 2 develop Squadron 42 as a standalone game. It did not. See supra Part II.B.2.
  488. 3 Accordingly, Defendants' development of Squadron 42 exceeded the GLA's scope
  489. 4 and infringed, inter alia, Crytek's exclusive rights to copy, distribute, and prepare 5 derivative works with regard to CryEngine. Defendants rely on Beijing Zhongyi 6 Zhongbiao Electronic Information Technology Co. v. Microsoft Corp., No. C137 1300-MJP, 2013 WL 6979555 (W.D. Wash. Oct. 31, 2013), involving Microsoft's 8 use of certain Chinese character fonts, where a license agreement provided Microsoft
  490. 9 a "perpetual, non-exclusive, worldwide, irrevocable" license to use the fonts in any 10 Microsoft product. Id. at *6. Because Microsoft had a license to "incorporate the 11 Fonts into any operating system or product, without limitation," its use of the fonts in 12 the product at issue was licensed. Here, however, the GLA authorized the 13 Defendants to embed CryEngine in only one game, not two separate games.
  491. 14 Third, Defendants assert that having breached the GLA by embedding a
  492. 15 different engine in place of Crytek's CryEngine, they can no longer be held liable for
  493. 16 infringing Crytek's copyrights. This argument is unpersuasive for two independent 17 reasons: Even if the Court determines that Defendants were permitted to switch
  494. 18 engines and did in fact do so, Defendants' argument fails to account for the full year 19 of infringing conduct between Defendants' announcement of the separate, standalone
  495. 20 Squadron 42 on December 16, 2015, and Defendants' eventual engine switch on
  496. 21 December 23, 2016. (FAC ¶¶ 22, 38.) In any event, notwithstanding Defendants' 22 representation that they no longer use CryEngine in any way (Defts.' Br. at 15-16), 23 Crytek alleges that Defendants' use of CryEngine is ongoing. (E.g., FAC ¶¶ 25, 51, 24 66.) Crytek should be permitted to obtain discovery to test the truth of Defendants' 25 assertions that they have completely abandoned the use of CryEngine.
  497. IV. NONE OF THE REMEDIES THAT CRYTEK SEEKS ARE BARRED
  498. Defendants assert that several forms of remedies that Crytek seeks are barred.
  499. (Defts.' Br. 16-18.) That assertion is incorrect.
  500.  
  501. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 26 of 30 Page ID #:270
  502.  
  503. First, Defendants reiterate their (incorrect) argument that Section 6.1.4 of the GLA bars Crytek's claim for money damages for breach of the GLA. It does not.
  504. See supra Part II.C.1.
  505. Second, Defendants argue that Crytek cannot obtain injunctive relief for Defendants' copyright infringement. They rely first on Section 10.7 of the GLA, in which the parties both agreed that injunctive relief would be available as a remedy for certain breaches and agreed to certain limitations on the forms of equitable relief they would seek. The section, in its entirety, provides:
  506. Notwithstanding anything in this Agreement to the contrary, where a breach of certain provisions of this Agreement may cause either Party irreparable injury or may be inadequately compensable in monetary damages, either Party will be entitled to obtain equitable relief, in addition to any other remedies which may be available, provided, however, that under no circumstances shall Licensee be entitled to enjoin the exploitation of CryEngine, nor shall Crytek be entitled to enjoin the publishing or other exploitation of the Game[.]
  507. (GLA § 10.7 (emphasis added).) The section does not bar injunctive relief; rather, it expressly recognizes that such relief may be appropriate. The only limitation that Section 10.7 imposes on Crytek is that Crytek may not seek to "enjoin the publishing or other exploitation of the Game." Section 10.7 does not preclude Crytek from seeking other forms of injunctive relief, such as relief concerning Defendants' unauthorized publication and distribution of Crytek's copyrighted source code.
  508. Defendants also argue that Crytek has not pleaded facts sufficient for the Court to impose injunctive relief. Not only is that argument premature at this stage, when no motion for injunctive relief is pending, but it also ignores numerous allegations of irreparable injury, including allegations of reputational injuries and Defendants' publication of Crytek's confidential source code and distribution of
  509. Crytek's technology to unvetted third parties. (E.g., FAC ¶¶ 39, 50-52.)
  510.  
  511. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 27 of 30 Page ID #:271
  512.  
  513. 1 Third, Defendants argue that Crytek cannot obtain statutory damages or 2 attorneys' fees under the Copyright Act because Crytek's copyright registration is 3 dated December 11, 2017, after certain acts of infringement commenced. At this
  514. 4 stage, it would be premature to foreclose the availability of statutory damages. See, 5 e.g., Guillot-Vogt Assocs., Inc. v. Holly & Smith, 848 F. Supp. 682, 691-692 (E.D.
  515. 6 La. 1994) (denying motion to dismiss statutory damages claim because question 7 remained as to whether independent acts of infringement occurred after registration).
  516. 8 Fourth, Defendants argue that Crytek cannot obtain punitive damages in this
  517. 9 action for breach of contract and copyright infringement. But Defendants overstate
  518. 10 the holdings of the cases on which they rely. For example, in Slottow v. American 11 Casualty Co. of Reading, Pa., 10 F.3d 1355 (9th Cir. 1993), the Ninth Circuit noted
  519. 12 that punitive damages are available for breach of contract in limited circumstances.
  520. 13 Id. at 1361; accord Riedel v. JP Morgan Chase Bank, N.A., No. EDCV 13-0114614 VAP (SPx), 2015 WL 12657068, at *2 (C.D. Cal. Apr. 3, 2015). Separately, 15 although the Copyright Act does not provide for punitive damages, e.g., Saregama 16 India Ltd. v. Young, No. CV 0219856 RJK, 2003 WL 25769784 (C.D. Cal. Mar. 11, 17 2003), it does provide for enhanced penalties when "infringement was committed 18 willfully." 17 U.S.C. § 504(c)(2). At this preliminary stage, before Crytek has 19 obtained discovery concerning the circumstances of Defendants' unlawful conduct, 20 precluding the potential for punitive or enhanced damages would be premature.
  521. 21 V. DEFENDANTS' MOTION TO STRIKE SHOULD BE DENIED
  522. 22 Defendants aver that Crytek's initial complaint contained a "false allegation"
  523. 23 that was "modified in retreat by Crytek's counsel after being confronted with a Rule 24 11 motion." (Defts.' Br. at 1.) They now move to strike what they term "the
  524. 25 immaterial, impertinent and scandalous Offending Allegations" in paragraph 15 of the First Amended Complaint. (Id.)
  525. To avoid burdening itself and the Court with the wasteful motion practice threatened by Defendants, Crytek did delete certain allegations from its pleading.
  526.  
  527. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 28 of 30 Page ID #:272
  528.  
  529. 1 Specifically, in the First Amended Complaint, Crytek retained its allegation that 2 Freyermuth had confidential information about Crytek's licensing practices due to his 3 prior representation of Crytek in negotiations of similar license agreements with third 4 parties, but removed its allegations that Freyermuth's possession of that information 5 would unfairly advantage Defendants and that Freyermuth never resolved that
  530. 6 conflict of interest. (Compare ECF No. 1 ¶ 15 with FAC ¶ 15.)
  531. 7 Defendants assert that the latter of those allegations was "demonstrably false
  532. 8 given that Mr. Freyermuth had obtained a written conflict waiver from Crytek prior
  533. 9 to negotiating the GLA on behalf of CIG." (Defts.' Br. at 20.) Having removed that 10 allegation in an (apparently futile) effort to avoid this motion practice, Crytek will 11 refrain from addressing it at length, and will instead briefly note as follows:
  534. 12 First, the letter by which Freyermuth's firm sought Crytek's consent to his
  535. 13 adverse representation (the "Letter," which Crytek is prepared to submit if the Court 14 would find it useful) states that Freyermuth's firm received a request to represent 15 "Chris Roberts and Cloud Imperium and its various related entities ('Cloud')" in 16 negotiating the GLA. The Letter does not explain that Freyermuth had a personal 17 interest in Defendants, even though Freyermuth co-founded Defendants and thus had 18 a personal financial interest in the negotiation of the GLA. (FAC ¶ 13.)
  536. 19 Second, the Letter asserts that Freyermuth's "law firm does not believe that
  537. 20 there exists any actual or potential conflict of interest in representing Cloud with 21 respect to the Transaction and Crytek with respect to other transactions as set forth in
  538. 22 the introductory paragraph of this letter." It is unclear how this facially reassuring 23 claim that no "actual or potential conflict" exists could be true in light of 24 Freyermuth's personal interest in Defendants, which the Letter does not address.
  539. 25 Third, the Letter acknowledges that Freyermuth's firm has "information or knowledge concerning Crytek that Cloud may consider relevant to their actions and decisions," including "information concerning other unrelated transactions or even information on how the parties do business or approach adversity." Yet it promises
  540. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 29 of 30 Page ID #:273
  541.  
  542. 1 that "absent consent from the applicable client, we may not, and will not disclose 2 such information to the other." It is unclear how such disclosure could have been 3 avoided, given Freyermuth's personal involvement in both representations.
  543. 4 Notwithstanding Crytek's amendment of paragraph 15, Defendants move the 5 Court to strike two sentences of the current version of that paragraph:
  544. 6 1. "In prior years, Freyermuth had represented Crytek in negotiations of
  545. 7 similar license agreements with third parties and had confidential
  546. 8 information about Crytek's licensing practices"; and
  547. 9 2. "Jones later left Crytek and became an employee of Defendants."
  548. 10 If the Court were to hold that the GLA were ambiguous — which Crytek expressly 11 denies — any ambiguous provision would be construed in light of the extrinsic 12 evidence concerning the parties' intent and the negotiation of the GLA. Cal. Civ.
  549. 13 Code § 1647 ("A contract may be explained by reference to the circumstances under
  550. 14 which it was made, and the matter to which it relates."). One of those relevant 15 circumstances is that Freyermuth represented Defendants in that adverse 16 representation — which Defendants now claim yielded an agreement barring any 17 cause of action by Crytek for its breach. Freyermuth's prior representation of Crytek 18 and possession of Crytek's confidential information concerning its licensing practices 19 is accordingly neither immaterial, impertinent, nor scandalous. Similarly, should the 20 Court be required to consider the factual circumstances of the negotiation, it will be
  551. 21 relevant to that inquiry that the negotiators for both sides of the transaction,
  552. 22 Freyermuth and Jones, are both now associated with Defendants, which may
  553. 23 introduce bias in any present-day testimony concerning the negotiations.7
  554. 24
  555. 25 7v. Fogerty The cases on which Defendants rely are not to the contrary. , 984 F.2d 1524, 1527-29 (9th Cir. 1993) (affirming decision to strike See Fantasy, Inc. allegations related to claims barred by the statute of limitations and res judicata); In re 2TheMart.com Sec. Litig., 114 F. Supp. 2d 955, 958 (C.D. Cal. 2000) (denying motion to strike); Survivor Prods., LLC v. Fox Broad. Co., No. 01-cv-3234 LGB (SHX), 2001 WL 35829267, at *3-4 (C.D. Cal. June 12, 2001) (striking quotations
  556. (cont'd)
  557. Case 2:17-cv-08937-DMG-FFM Document 25 Filed 01/19/18 Page 30 of 30 Page ID #:274
  558.  
  559. 1 CONCLUSION
  560. 2 For the foregoing reasons, Defendants' Motion To Dismiss The First Amended 3 Complaint Or Claims For Relief Therein Or, In The Alternative, To Strike Certain 4 Portions Of The First Amended Complaint should be denied in its entirety.
  561.  
  562.  
  563. 5 Dated: January 19, 2018
  564.  
  565. 6
  566. KEVIN J. MINNICK (SBN 269620) 7 kevin.minnick@skadden.com SKADDEN, ARPS, SLATE, 8 MEAGHER & FLOM LLP
  567. 300 South Grand Avenue, Suite 3400 9 Los Angeles, CA 90071 Telephone: (213) 687-5000
  568. 10 Facsimile: (213) 687-5600
  569.  
  570. 11 P. ANTHONY SAMMI
  571. (admitted pro hac vice)
  572. 12 anthony.sammi@skadden.com
  573. KURT WM. HEMR
  574. 13 (admitted pro hac vice) kurt.hemr@skadden.com
  575. 14 SKADDEN, ARPS, SLATE,
  576. MEAGHER & FLOM LLP 15 Four Times Square New York, New York 10036 16 Telephone: (212) 735-3000 Facsimile: (212) 735-2000
  577. 17
  578. 18
  579. 19
  580. 20
  581. 21 ________________________
  582. (cont'd from previous page)
  583. Respectfully submitted,
  584.  
  585. /s/ James Y. Pak
  586. JAMES Y. PAK (SBN 304563) james.pak@skadden.com SKADDEN, ARPS, SLATE, MEAGHER & FLOM LLP
  587. 525 University Avenue, Suite 1400
  588. Palo Alto, CA 94301 (650) 470-4500
  589. (650) 470-4570
  590.  
  591. Attorneys for Plaintiff Crytek GmbH
  592.  
  593. 22 from newspaper articles that had "no possible bearing on the controversy between
  594. 23 the parties" and "[did] not assist in the Court's understanding of the parties' dispute");
  595. Gssime v. Nassau Cty., No. 09-cv-5581 (JS)(ARL), 2014 WL 810876, at *3
  596. 24 (E.D.N.Y. Feb. 28, 2014) (striking a "direct personal attack on defense counsel" that
  597. "improperly suggests the counsel committed some wrongdoing in filing the
  598. 25 Answer"); Fleischer v. A.A.P., Inc., 180 F. Supp. 717, 721-22 (S.D.N.Y. 1959) (striking allegations concerning disqualification of counsel, which was collateral to the issues to be litigated). If anything, the stricken statement in Gssime is most analogous to Defendants' repeated and baseless contentions that Crytek has sought to mislead the Court and made a "false" allegation concerning Freyermuth.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement