Community Forum

I uploaded an ALL TIME GREATS historic roster into MBLTS23 roster vault.

This roster contains 26 or more of the greatest players for each franchise.

The roster is named ALL TIME GREATS uploaded by biebig2010.

@macdonald433_PSN said in Post patch cleats:

Biebig2010 hi. Just wondering if you were still working on the nl for your alltime greats roster. Appreciate it. Thanx.

Yes I am. I'm finishing the NL Central and then onto the NL West and I'll upload a version to the vault when I'm done.

I see the same problem with the generic cleats post patch. They look aweful when playing a game.

For some strange reason you need to go to Most Recent stadiums and search for them there. Worked this way last year also.

It's a bug from last year that has resurfaced.
A couple of ideas...

1. Before saving your stadium go into Properties and change something (like seat color) and commit the changes. After committing changes save your stadium. I did this last year until they fixed the bug and have been doing it this year and haven't lost a stadium. You have to do this before the template bug bites you though.
2. I haven't tried it myself but I read that if you still have the stadium but it's a template when you open it or try and use it that you can upload it to the Stadium vault and then download it and it reverts back to all your changes. Might be worth a shot if you still have the stadium.

I agree. It's a bit frustrating because the Stadium Creator could be a fabulous piece of work if they could make a few slight changes and obviously not carry over bugs to this year's game that were already fixed last year.

I guess I could say the same thing about the whole MLBTS game in general. It's close to being a masterpiece; however, it's not because of a lack of detail, lack of focus, laziness, or whatever has been plaguing the game the last few years. The game just hasn't lived up to the standards that the original handful of versions had set.

MLBTS doesn't allow carrying over stadiums from 22 to 23 but I see it has carried over bugs from 22 to 23.

Template stadiums can and will replace your stadium and stadium files get corrupted again just like last year at launch. It's so annoying that the same bugs that were fixed last year show up again this year. Where's the quality control?

How about the ability to start a franchise, play it all year long, and then allow me to continue to use it in next year's version of the game (i.e. Y2Y saves).

@FranciseYearlysaves-_MLBTS said in Can't carry over 22 franchises into 23:

100% AGREED !!! I have bought every version since 2009... I gave MLB the benefit of doubt last year since they expanded to XBox and also the new game console generation...(with very little improvement in graphics... which is a totally different rant and not a "must have" such as year-to-year saves.) I now have NO REASON to continue purchasing from year to year if I have to start from scratch each year. How inconsiderate and disappointing to a once phenomonal experience.

It's a really strange decision on their part. If anything this decision is providing incentive to NOT buy the new version because I want to continue with what I already have. If I can use my current creations (players, rosters, stadiums, franchises, etc) in the new version then it's a slam dunk buy.

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.

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.

@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 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

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. Excellent idea.

However, once again SCEA requires everyone to rebuild ALL of their 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 players, custom rosters, or franchises from 22 to 23.

You've got to be f'n kidding. Once again, SCEA screws their customers on Y2Y saves.

Unbelievable

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.

@TEXAS10PT_PSN said in So....when is the MLB 23 cover athlete going to be revealed?:

We'll probably find out the 2nd Tuesday of next week.

Wait, there's going to be two Tuesdays next week? How will that work?

How many times are you going to post the same complaint? I see three threads on this already.

The good news is that most, if not all, of these stadiums have been created and are in the Stadium Vault. Most, if not all, of these were very well done as well.

Make sure you are searching from the Recently Created section.

There was a patch released a month or so ago that fixed a few things; however, it also resulted in stadiums consuming more space. So, if you saved a stadium pre-patch it might be say 95% and then if you open it post-patch the storage will go up to say 115%.

Because the storage for that stadium is over 100% it won't let you edit anything or add anything. You have to delete things to eventually get the storage % down below 100% before you can edit or add anything.