Thanks to everyone for reporting this issue. We've passed it on to the right team, and we'll look into it to make sure everything is working properly in this regard.
@EA_PulsarPlease note this seems to be multi-faceted issue. Not only does the Teambuilder custom team end up in Alabama (as others noted here) BUT for recruiting purposes the team actually takes on the location of the real team it was swapped with.
For example, lets say you create a custom team and import them into a dynasty. 3 issues happen:
1. on the custom schedules screen the team is located in Alabama
2. for recruiting the team seems to be located wherever the real team you replaced was located (based on pipeline and proximity to home ratings)
3. also, the custom team takes on the stars/prestige of the team in replaced
Exact same things I’ve noticed. Completely screws up my recruiting pipeline. Couldn’t figure out why kids from Kansas City thought a 1 hour drive was “too far from home”. My prestige and pipeline came from UMass, and my stadium is in Alabama, not Lake of the Ozarks. Pretty frustrating. Hoping for a resolution soon, since it’s been a known issue for a while.
