---
# System prepended metadata

title: Untitled

---

Hello @Justin,

Answering your questions:

** New Target Window **

Seems totally reasonable to be 100% sure about optimizations and loading time improvements

** New Proposed Plan **

1.3.0 as Day 1 Patch seems ok, but it doesn't necessarily means that we should do only one patch. 

Let me explain. We can do a patch with 1.2.2 and later make a patch with 1.3.0. It's even safer to do this way, as we can find submissions problems that lay on 1.2.x only and could be detected in advance. In this way, we could also detect possible new performance issues from the latest versions.

** Loose Ends to Tie Up **

Yes, that works for us. Also, consider on your side the two patches scheme. 

About the agreement. Yes. Let's evaluate it in early June.

About the dates regarding new content for us to work with, we would say end of May/first week of June. New skuls means new translations and that could take time to check all of them and fix potential nomenclature problems. Our desired submission window would be 2nd week of June latest.

----

By the way, we will start QA on the XB1 build shortly and we expect to submit asap (next week, probably)

Is it 1.2.2 code available to merge? (we saw it's been released today)


