A lot of the big-ticket future things, the buzzwords, are things like iCache, persistence and Server Meshing. When developing for today's game, which doesn't have those features implemented, how much of a focus is placed on future-proofing for when those things come online? Do we build today knowing that's coming later on, or is this all going to be reworked later down the line?

No, no, no. In fact, for example, every single team had to redo certain aspects of their code for Server Meshing, just to make sure things worked. But those were pretty small tasks. And I think at least my teams blasted through them in, I would say, about a week, so it wasn't like a huge painstaking thing. But with iCache or the other aspects, let's say we know we're going to be redoing something. We'll wait until iCache is done, and then we'll redo it. In some cases, we'll live with the pain, where we look at a system and we know we want it redone. But if we're working on a system now, we know what iCache is going to be doing, we know what Server Meshing is going to be doing, and we're making sure of that when we're building these systems, and they should work when that switch is flipped.