Can't carry over players, rosters, or stadiums from MLBTS22 to MLBTS23
-
So SCEA gives us an editor to create awesome custom players, and allows us to add these awesome customer players to custom rosters, and allows us to create franchises using these new custom rosters with the custom players. They also give us a stadium editor to create awesome custom stadiums. Excellent idea.
However, once again SCEA requires everyone to rebuild ALL of their custom stadiums, and custom players, and custom rosters and restart all of their franchises in MLBTS 23 because they won't allow us to carry over the 22 custom stadiums, custom players, custom rosters, or franchises from MLBTS 22 to MLBTS 23.
You've got to be f'n kidding. Once again, SCEA screws their customers on Y2Y saves.
Unbelievable
-
I mean stadiums make sense imo. There is likely new features in stadium creator that make the old ones incompatible
-
@the_dragon1912 said in Can't carry over players, rosters, or stadiums from MLBTS22 to MLBTS23:
I mean stadiums make sense imo. There is likely new features in stadium creator that make the old ones incompatible
Only if there are some massive changes to the stadium creator and they've stored the data in a new format and it's just impossible to export / import data from one format to another.
I don't understand why they give us the ability to customize stadiums, customize players, customize rosters, customize franchises, and then require us to throw it all away when a new version is released. It's just mind boggling.
What if I created a few thousand MS Word documents and then when the new version of MS Word comes out none of those documents can be read or edited in the new version. It would be 100% completely unacceptable. Yet, somehow SCEA continues to do stupid things like this that completely screw over their custom community.
-
@biebig2010_PSN said in Can't carry over players, rosters, or stadiums from MLBTS22 to MLBTS23:
@the_dragon1912 said in Can't carry over players, rosters, or stadiums from MLBTS22 to MLBTS23:
I mean stadiums make sense imo. There is likely new features in stadium creator that make the old ones incompatible
Only if there are some massive changes to the stadium creator and they've stored the data in a new format and it's just impossible to export / import data from one format to another.
I don't understand why they give us the ability to customize stadiums, customize players, customize rosters, customize franchises, and then require us to throw it all away when a new version is released. It's just mind boggling.
What if I created a few thousand MS Word documents and then when the new version of MS Word comes out none of those documents can be read or edited in the new version. It would be 100% completely unacceptable. Yet, somehow SCEA continues to do stupid things like this that completely screw over their custom community.
So you are saying if hypothetically they removed being able to change the altitude that you should just be able to import a stadium with max elevation from the last game(I'm not saying thats going to happen but its reasonably possible)
-
Absolutely.
When migrating data from one version to the next if there are fields that aren't in the old version that are in the new version, or are variable in the old version but not editable in the new version, then you simply provide a default value that makes sense and use it.
If the user wants to go in and edit one or two new fields to something other than the default after they've migrated from old version to new version then it's not a problem. Simply open the stadium on the new version and adjust whatever value was set as the default to whatever the user wants. This assumes the field is editable in the new version. If it's not editable then the user gets the default.
This is data migration 101 type of stuff. Very easy to do.
