Stadiums not transfering to MLBTS 23
-
So SCEA gives us a great editor to create really cool stadiums but once again requires everyone to rebuild ALL of their stadiums in MLBTS 23 because they won't allow us to carry over the 22 stadiums to 23.
You've got to be f'n kidding. Once again, SCEA screws their customers on Y2Y saves.
Unbelievable.
-
I'd imagine created stadiums take up quite a bit of resources, more then logos and such. Now not carrying over RTTS or Franchise isn't acceptable
-
I'm not even talking about the stadium vault carrying over what's in it. I'm talking about simply allowing us to take a custom stadium built in MLBTS 22 and opening it and saving it in MLBTS 23. A simple transformer of data from MLBTS 22 to MLBTS 23 is all it would take.
Unless they have completely overhauled the stadium creator this is a relatively simple task that a junior computer science major can do. It's not that difficult and doesn't take a lot of time or resources to accomplish. Almost all companies that sell commercial software do this when a new version of their product is released.
-
If they've changed the SC as they did last year, the programming probably wouldn't be compatible. Yeah, I'd love to carry some over, but I think I can replicate a couple of them.
