Are there any plans to stream line the patch sizes? I am on the road a lot and use my cellular data to update Star Citizen, the updates ear up a lot of gigs right now especially when there are multiple patches.asked by Starripper

So yes absolutely. We have a plan, in fact I sat down earlier this week which would be the previous week to you seeing this as we're recording this on a Friday and you're going to watch this on a Monday. But yeah I think we have a really cool plan that's very configured to our new development paradigm.Not saying new for us, but the new paradigm of what we're doing which is constantly building, testing, deploying both internally and then externally to, you guys in the community at first level the Public Test Universe the PTU then of course to live and so we needed a solution that we can can be building rapidly and iterating rapidly and getting it to you as efficiently as possible. And our current one is not the best because it has these big monolithic PAK files and each PAK file is two gigs and there's quite a few of them and if one file changes in it, you have to rebuild the whole PAK file and the way our build system works with all the data is we have to rebuild all the data into the PAK files right now, which essentially means we spend about three hours if we do a full build about an hour if we just do a code build.But that's a huge amount, so it's problematic in terms of getting that done and then testing it instead of there's an issue then you have to go back. So we want a solution that's much more flexible and iterative and we also want one that means we're not saturating everyone's bandwidth. Cause it's not just on you guys side but it's also on our side. Every byte we push costs us money 'cause it's coming off the Amazon CDN that we're using. So we have a plan that I think is much cooler, smarter one that is all built all around incremental builds of both data and code as soon as it's assimilated into the code base and all the individual files are tagged and held in a huge object store and the patch will know what to pull down and what changed.So even if you've changed a couple of files no longer will we be pulling down a whole new two gig object PAK or something like that. It will just be pulling down the specific files, it will also allow them to version back and forth between them. So there's a really really cool plan it's going to be done by combination of DevOps team in Austin and the folks in the Frankfurt office and Turbulent are all putting this together and building and it's going to be super cool!Not going to be deployed tomorrow. I just signed off on the whole design, we've laid a lot of the groundwork but a lot of it is going to take some time and testing but when it comes online it's going to make a massive difference for our ability to turn around builds for you guys quickly and also to reduce the amount of data that we saturate both our CDN and you guys on your bandwidth limits. So i'm pretty excited by that it will just allow us to be more flexible and more nimble which is good.