"Stepping in" to their code/work is not a pragmatic solution at all. Listing the obvious reasons would not be worth the time.
Rest assured that on the QA/quality front, we have been involved along the way... and when appropriate, we have absolutely had our guys in touch with theirs on the code front.
I have seen a lot of questions about "world size" of late, so gonna leave this in both threads as my current understanding (from the last time these same questions were asked back in May
). If I am mistaken, I'm sure someone from PW can correct me:
There has been some talk that older console worlds were smaller than their PC counterparts (I tried to find some mention of this on the wiki, but cannot - let's just assume that is the case, likely for old gen-created worlds) and subsequent concern about what that meant for the new console build. For newly generated worlds in the new codebase, world size (small/medium/large) will match their PC counterparts. For existing worlds that may - if this is indeed the case - be smaller than their PC counterparts, they will load just fine in the new code, but will remain at their current size - whatever that may be.
I have seen a lot of questions about "world size" of late, so gonna leave this in both threads as my current understanding (from the last time these same questions were asked back in May
There has been some talk that older console worlds were smaller than their PC counterparts (I tried to find some mention of this on the wiki, but cannot - let's just assume that is the case, likely for old gen-created worlds) and subsequent concern about what that meant for the new console build. For newly generated worlds in the new codebase, world size (small/medium/large) will match their PC counterparts. For existing worlds that may - if this is indeed the case - be smaller than their PC counterparts, they will load just fine in the new code, but will remain at their current size - whatever that may be.