"The deliverables to be delivered by the Developer to SEL pursuant to the Milestone Schedule and the Specification ..."
"... only approval given in writing by the Project Producer shall constitute the acceptance by SEL [that is the defendant] of any Deliverable."
"[13.1] Upon termination of this Agreement by SEL pursuant to Clause 12.1, the Developer shall be entitled to the following amounts as its sole and exclusive remedy for any damage that the Developer may suffer as a result of such termination: SEL shall pay the Developer within thirty (30) days of termination: (a) any and all Milestone Payments that have bene approved by SEL but for which SEL has not made payment to the Developer under the terms and conditions of this Agreement; and (b) an amount equating to the Milestone Payment for the Milestone being developed at the date of termination (if not already paid by SEL) and (c) an amount equating to the Milestone Payment for the next Milestone due for development after the current Milestone. Notwithstanding the foregoing it is acknowledged and agreed by the parties that Milestones 6 and 10 (respectively “Greenlight 2: First Playable” and “Greenlight 3: Vertical Slice” Milestones) shall be key Milestones to be evaluated by the SEL board to determine if SEL shall proceed with the Product. On evaluation of each of these Milestones SEL shall be entitled within thirty (30) days following receipt of the relevant Milestone to terminate this Agreement in its sole and absolute discretion without further liability to the Developer and Developer shall be entitled to the following amounts as its sole and exclusive remedy for any damages that Developer may suffer as a result of such termination: within thirty (30) days of termination SEL shall pay the Developer for any and all Milestones that have been approved by SEL but for which SEL has not made payment to the Developer per the terms and conditions of this agreement, such payment it include the sum due on approval of the relevant Greenlight Milestone Provided That it was acceptable by SEL acting reasonably in Accordance with the terms of this Agreement prior to the termination by SEL…"
"No waiver or modification of any provision of this Agreement shall be effective unless in writing and signed by the party against whom such waiver or modification is sought to be enforced."
"After GDD is finalised the parties agree that an updated and mutually agreed GDD, TDD and Milestone Schedule should be inserted into this Agreement as an addendum."
"A decision was taken at the last min to pull the game from the full European GL and have the game GL in Japan with the SQEX board. Our studio GM and both COO’s have been reviewing the materials and are happy to send them to Japan. The build has already gone to Japan along with build notes and a play through video and a producer there will be familiarizing themselves with the way to play the game before the meeting. I will also be present (via video conference). Also I want to say thank you for to you and your team for all the hard work you’ve put in ahead of this, and it’s by no means wasted work as the materials are all just as needed for a GL in Japan."
"Milestone 7 is on our FTP. Contents include ..."
"... look forward to hearing from you tomorrow regarding the Japanese presentation."
"I will speak with our production team and see where things are regarding resourcing now and ongoing. AvP team members are working on the game [and] have been since the beginning."
"I know materials have been delivered for MS7, but this seems a bit premature given that we not had the meeting and feedback from Japan yet. In anticipation of this, Matt did ask Steve to hold fire on [that settlement] until after Japanese review of MS6 to ensure that everyone was happy with the direction before moving forward and to avoid wasted work (and Steve was told that the schedule postMS6 would be re-worked to accommodate). MS6 is an important milestone, we need to get all the feedback from Japan, take stock of where we are and take on-board any feedback to clarify the next steps. And part of MS6 is signing off the schedule, resourcing plan and deliverables for the rest of the project, and until all this is approved, it does not seem terribly efficient to produce and create and deliver assets that may be going in the wrong direction and may be wasted."
“With regard to the MS deliverables I’s hard for us to accept them as a MS as we will need to approve the full project plan before we can move on. It is of course still much valid for us as an update.”
"Following on from the GL meeting and the review of the code and documents we feel that we would like to push the design and scope further to realise the full potential of the design pillars and maximise our sale potential."
"We understand that any change in design emphasis may have an impact on how the remaining budget is allocated, and may also impact on the final release date, so we need to spend this month planning what can be done, and have various budget, schedule and design options that can be proposed, in respect had been proposed. The areas of the design we would like you to look at are listed below with some bullet points so your team can start looking at these and thinking of ideas and planning."
"Ask them outright what is required of us to get the greenlight signed off and paid."
"MOD23. As per our discussions after the meeting and e-mail called 'Rift Greenlight Deliverables - MS6.1'."
"[19.] The parties met at the Claimant's offices on14 January 2010 to discuss feedback on the Deliverables for Milestone 6. At the meeting, the Defendant sought to amend the Game, with development to be “refocused” in a different creative direction. This request did not comply with clause 3 of the Agreement on “Change Procedures”. The parties discussed what additional work the Defendant wished the Claimant to carry out as part of this “refocus”. The amended Game differed from the Game originally specified in the Agreement and so required the parties to amend the Agreement by means of clause 3. [20.] Although clause 3 of the Agreement was not complied with, and the Agreement therefore remained unamended for the purpose of defining the parties' legal rights and obligations, the Claimant was prepared to provide a “refocused” milestone in respect of the amended Game. This milestone is variously referred to as Milestone 6, 6.1 and 6.2 in the contemporaneous documents. The Claimant circulated a written summary of proposed revised requirements for this milestone shortly after the meeting on14 January 2010 ."
"See attached for what we intend to deliver to draw the first green light to a close."
"Following yesterday’s feedback from SEL [the defendant], in order to get the first greenlight milestone signed off, Rebellion proposes to deliver the following ..."
"Documentation showing Rebellion’s latest refocus efforts."
"NOTE: all documentation is pending final sign off from senior management at Rebellion."
"I thought I’d also send you the latest invoice - see attached."
"Hello Steve, I am writing to formally advise you that Rift Milestone 6.2 delivery received on Friday February 5th, 2010, is currently Non-Approved. Areas of non-approval are: Design Rift_Refocus_High_Level Production DLC option Preliminary_Rift_Refocus_Costs, Rift_Pre_Production_Goals Rift_Risk_Register. I’ve attached two documents to this email with our feedback on the above…"
"Please digest the documents and advise when you may be able to resend."
"Thank you for your email of the 25th February. We have discussed this internally and it does appear that there is a very important difference of opinion as to where we are in this project. We submitted milestone 6 in November and this met all of the agreed requirements for Milestone 6. However, following receipt of Milestone 6, Square Enix asked us to undertake additional work as you wanted us to change the direction of the project, in particular by shifting attention onto a more multiplayer focussed solution, whilst also concentrating on Rift’s key USPs of Capture and Summon, and incorporating a new ‘Trading’ feature. This was discussed during our meeting on 14th January, following which we agreed a list of ‘Green-light Deliverables’ (set out in my email of the 15th January). The principal objective of this list was to set out an alternative creative vision for the project, as you required. We then delivered all of the work described in that document during February and accordingly we do not accept the reasons given for failing the Milestone. We have looked through the reasons you sent to us in your email of the 25th February and our position on each of these is set out in the attached document. In relation to the feedback inserted into the Refocus document, we should stress again that the agreed objective of the Refocus document was not to create a final, fully detailed design document. Instead, the objective was to outline a “refocus” of the project in a different direction, as you had specifically asked us to do. However, notes added into to the Refocus document appear to request far more detail than was ever envisaged at this particular stage. For instance, it was agreed that we would provide a summary document addressing the multiplayer feature, and we did exactly that. However, the response to our proposals for the multiplayer feature demand far more detail from us than we agreed, or than is required to meet the objective of this document. Having said this, we have tried in the attached documents (Rift_MS6.2_Extended.zip) to provide as much additional information as possible within the available time. Ultimately, though, we are in a position where we have not been paid anything since11th December 2009 and it is imperative that we address this problem immediately. This will require a separate discussion on existing financial exposure, but also a rapid conclusion of Milestone 6. (We also need to discuss simplifying and streamlining communications between both companies). May I suggest that we meet up in person or on conference call with Roger, Jason and Chris as soon as possible (ideally this week) to progress this further. Please let me know when would be convenient to you."
"Further to your discussions with Roger Cheung, I understand that you and Roger have agreed that the date of delivering the Deliverables for Milestone 6 shall be5 February 2010 instead of the15 November 2009 date agreed in the Side Letter. We therefore look forward to receiving the Deliverables by close of play tomorrow. If you anticipate any difficulties in meeting this deadline please let Roger know. All terms not otherwise defined in this letter shall be as per the Development Agreement and this letter shall be governed and construed in accordance with English Law. I should be grateful if you would confirm the acceptance of the contents of this letter and the revised Milestone 6 delivery date by kindly signing and returning the enclosed copy of this letter to me at the address below."
"The first sentence of the Letter, which was addressed to Chris Kingsley of Rebellion, is “Further to your discussions with Roger Cheung [of SEL], I understand that you and Roger have agreed [...]”. This was raised in my firm’s letter of24 November 2015 ... and SEL have to date been silent as to what these discussions were, save to say that they are not relevant to the Application. No notes or emails (or any other document) around these discussions have been disclosed by either party; Rebellion has searched for relevant material and can confirm that there is none in its control. I am informed by Mr Kingsley that he has no recollection of conversations with Mr Cheung about this letter. Given that the Letter explicitly refers to these discussions (about a third of the length of this short letter is spent in mentioning them), and given also the very serious consequences that SEL allege the Letter to have for Rebellion, the discussions are highly relevant as part of the factual matrix underlying the Letter, and it is not satisfactory for this not to be properly scrutinised."
"The4 February 2010 letter did not refer to changed specification for the Game. Nor did it in any way extinguish, waive or modify, any liabilities to make payments or breach of contract which had accrued prior to the date of the agreement."
"The Defendant applies underCPR r.24.2 for summary judgment in relation to the Claimant's claims in respect of Milestones 7, 8 and 9 (as defined in the Particulars of Claim). It is common ground that the parties agreed by the4 February 2010 Letter to reschedule the Milestone 6 delivery date for5 February 2010 . The Defendant's position is that the4 February 2010 Letter extinguished any existing claims in respect of the previous submission of the Milestone 6 or 7 deliverables: it is wholly inconsistent with the idea that the requirements of those Milestones had already been met. Further, since the Agreement was terminated by the Defendant upon consideration of what were agreed to be the Milestone 6 deliverables, the relevant termination provision was the second part of clause 13.1, and there is therefore no entitlement to any payment in respect of Milestones 7 to 9. The Defendant believes the above matters are suitable for summary determination."
"Which witnesses of fact do you intend to call at the trial or final hearing including, if appropriate, yourself?"
"a. The letter [of4 February 2010 ] constituted a clear and binding agreement by which the parties agreed that the date for the delivery of the Milestone 6 deliverables was rescheduled to5 February 2010 . b. That is inconsistent with any claim to payment in reliance on the idea that the Milestone 6 deliverables had already been submitted. The only meaning which the Letter could have conveyed to a reasonable reader is that the parties agreed that they were still working towards Milestone 6 and that the deadline for the submission of the Milestone 6 deliverables would be5 February 2010 . c. In entering into that agreement, the Claimant waived any right to claim any sum from the Defendant on the grounds that the Milestone 6 deliverables (or any subsequent set of deliverables) had already been delivered prior to5 February 2010 and/or it became estopped from asserting that they had been so delivered for the purpose of maintaining such a claim. d. At the very least, the effect of the Letter was that the Defendant's termination on4 March 2010 was within 30 days of the receipt of the Milestone 6 deliverables, such that the enhanced termination provisions in clause 13.1 applied and there could be no claim in respect of Milestones 8 or 9. e. The result is that, subject to an argument as to whether the Claimant is entitled under clause 13.1 to be paid the sum in respect of Milestone 6 itself - which the Defendant accepts cannot be resolved at this hearing - the Claimant is entitled to no other payment."
"As to your letter of 11 November dealing with the application itself [that is the application for summary judgment] and seeking our comments, our view is that the application as you propose it is misconceived and will fail. As you will appreciate, it is difficult to address the matter in great detail without sight of an actual application, but even so it appears to us that the point to be decided is not as simple as merely the construction of the4 February 2010 letter. The factual background to the letter has not been established - for example, what was discussed or agreed between Chris Kingsley and Roger Cheung, as referred to in the letter? There is relevant context to the letter that may need to form part of disclosure prior to any application being heard, which will increase costs and complexity, making it less suitable for a summary judgment application. We have tried to give an accurate costs estimate in our budget, but this may need to be amended once we have had sight of the application and as matters progress. Also, even if your client were to succeed in the application it would not ‘leave our case in tatters’ as you suggest ... Given this, we do not accept that this is suitable for summary judgment, as too many issues would remain live to make it worthwhile."
"2. When D terminated the Agreement, C had long since submitted the deliverables in respect of Milestones 6 and 7 and was working on Milestone 8 as it was contractually obliged to do. C argues that D was by that time plainly in breach of contract by failing to test and approve Deliverables 6 and 7 as required under the Agreement, and that, upon termination by D, C was entitled to be paid certain specified sums for Milestones 6-9 in accordance with the terms of the Agreement. C also alternatively makes claims to damages or sums due by way of quantum meruit. 3. D would have the Court find that by signing an extremely brief letter dated4 Feb 2010 ... which mentions none of these things, C lost its ability to make any claim for payment in respect of Milestones 7 and 8 and agreed to extinguish any existing claims against D for breach of contract. C's case is that the Letter -- with hindsight a shameless device put forward by D in an attempt to liberate D from the Agreement at reduced costs -- achieved neither of these things. 4. On the current application, D asks the Court to summarily dismiss C’s ‘claims for payment in respect of Milestones 7, 8 and 9 (as defined in the Particulars of Claim)’ (draft order 1 1/6/50), ie it does not relate to the damages or quantum meruit claim. The application should be rejected as the claim has substantial prospects of success and is in any case not suitable for summary disposal. 5. There are also compelling reasons why the claim should be disposed of at trial. As mentioned above C makes an alternative claim for a quantum meruit in respect of the work done on Milestones 6-8. D has not applied to strike out or dismiss this alternative claim, meaning that the factual investigation into these milestones and whether D would be justified in not accepting them will have to be undertaken regardless of whether this application is successful. D's application will accordingly not result in any tangible savings in terms of time or costs."
"Also I want to say thank you for to you and your team for all the hard work you’ve put in ahead of this, and it’s by no means wasted work as the materials are all just as needed for a GL in Japan."