Multiple Teams in One World Topic

What's everyone's take on having multiple teams in one world? I just read in a conference convo that a coach has 5 teams in one world, and these teams are spread out geographically so just by normal FSS scouting (scouting states within 300 miles) he can almost cover the entire pool. By having each team spending an additional $1,000 to FSS non-300 mile states, he literally can cover all the states. 

Being a coach that recruits somewhat nationally (when the opportunity arises), I feel a little cheated since my overall pool of players to choose from is much lower, and I also miss all the initial dropdowns in non-FSS states since recruiting them w/o knowing potential is risky. Meanwhile, this coach can long distance recruit any recruit that drops down since he has every players potential. 

Thoughts, comments?
1/10/2011 8:48 PM
tiany, you read it on my cc and was my convo, but I am not the offender. And I am opposed and WIS/HD should disallow it.
1/10/2011 8:59 PM
It would seem to be a pretty clear recruiting advantage. Just this past recruiting time, I was left with only a couple hundred dollars and an open scholarship.

There was no one in my (scouted) area that I felt comfortable giving a 4-year scholarship to, so I ended up taking a walk-on. There were a half-dozen or more guys that I had "targeted" in states I didn't use FSS on that I might have been willing to give the scholarship to had I known their potentials. In this instance, it would have been a *huge* advantage to have the entire nation scouted with FSS.
1/10/2011 9:02 PM
I know you are not the offender. I knew the coach had more than 1 team but I thought he dropped it down to 1, guess that wasn't true. This actually might have affected my recruiting since one of his teams went across country and landed one of the recruits that I was about to take a couple of seasons ago. 
1/10/2011 9:03 PM
i think u should be limited to 1 team per world.  period.
1/10/2011 9:07 PM
Posted by reinsel on 1/10/2011 9:07:00 PM (view original):
i think u should be limited to 1 team per world.  period.

This is what I think as well. With this many worlds, you can have many teams without ever needing to have multiple teams in one world. The only reason I can think of is to have an unfair recruiting edge, which totally unbalances the field.

1/10/2011 10:04 PM

I disagree with you guys; I think a coach should be able to have 2 teams in the same world, but the teams should not be in the same division, they should be spread out geographically and one of the schools should go no where near the other for recruits.  I would agree 5 teams in the same world is a bit much.  Also, I have never had two schools in the same world.

 

1/10/2011 10:17 PM
i think that sharing FSS data between teams is cheating, and i don't think there is any doubt about that.

however, i think plenty of coaches have multiple teams in a world (myself included), who don't share FSS data. as long as you are careful about it, i don't see a problem with it. for example, i have a d1 and d2 team in a close geographical region. i have a lot of rival d2 schools in the area. i would never take a player off them with my d1 school, because it just isn't fair - i obviously wouldn't use my d1 school to take a guy off my d2 school, so that would be an unfair advantage. plus it just feels dirty (the other guy could feel it was intentional to screw their d2 school, on my d2 schools behalf, and then be afraid to battle me, or something).

i don't see how having one of those schools benefits the other at all - in fact, i feel it is a slight disadvantage to myself, because there are things i won't do to make sure i am playing fair, that could potentially be beneficial. so i personally don't see what is wrong with it.

1/10/2011 10:21 PM (edited)

I have two teams in Wooden.  One in D2 in Pennsylvania, one in D3 Minnesota.  I've never recruited a played from a state that I FSSed with the other.  It's a verifiable fact if WIS really wants to look into it.

I don't see what's wrong with that.  I understand the potential for cheating is there, but if I never cross paths with either FSS, and I can prove that, then I dont' see what the problem is.

1/10/2011 10:44 PM
I think if you have all those teams in one region, then it is not as bad since you won't be able to pulldown enough recruits within 300 for all those teams. But with teams spread out with 1 in CA, 1 in TX, 1 in IN, 2 in the Northeast, he won't run into a pulldown issue for any team. Then say this is a poor recruiting generating year for the TX region, he can just log into his Northeast team, see the potential of leftover players, and just recruit one for his TX team w/o ever scouting the state with his TX team. THIS is a huge advantage.
1/10/2011 10:46 PM
And there are two easy solutions which easily allows multiple teams, and prevent/or at least weaken the effect FSS sharing:

1) Make it so that the only way to recruit a player is to have scouted the player, either via a scouting report or via FSS scouting of the state. You cannot sign a player without scouting. This means even if a coach FSS shares, he still has to spend money to scout the state. Sure, a coach can still get a better idea of which state to scout by knowing who he wants, but at least let him spend the money for the state as well.

2) After recruiting is over, show which state each team has scouted via FSS. Just add an additional column to the recruiting tab. This way, we can tell which coach is recruiting his team and signing players w/o ever scouting the state. And if those unscouted players are consistently good and growing in key areas, it becomes obvious he's FSS sharing. Again, this runs into the problem of the coach avoiding detection just by scouting the state (after having shared FSS) but still, let him at least pay the scouting fee.
1/10/2011 11:06 PM
I think when the schools are close together is when it gets sketchy. It's so hard to recruit beyond 360 miles, and in D1 in some regions it's hard to recruit beyond 200 miles so having two teams that are 1k miles apart you should rarely have overlap in FSS scouting. On the occasion when I scout further than normal, I've even scouted the same state with both of my schools, since Illinois is close to my D2 team and >500 miles away from my D1 team I've purchased the FSS on both teams a couple of times, although I don't think I've ever actually signed anybody from Illinois with WVU.
1/11/2011 12:24 AM
Posted by tianyi7886 on 1/10/2011 11:06:00 PM (view original):
And there are two easy solutions which easily allows multiple teams, and prevent/or at least weaken the effect FSS sharing:

1) Make it so that the only way to recruit a player is to have scouted the player, either via a scouting report or via FSS scouting of the state. You cannot sign a player without scouting. This means even if a coach FSS shares, he still has to spend money to scout the state. Sure, a coach can still get a better idea of which state to scout by knowing who he wants, but at least let him spend the money for the state as well.

2) After recruiting is over, show which state each team has scouted via FSS. Just add an additional column to the recruiting tab. This way, we can tell which coach is recruiting his team and signing players w/o ever scouting the state. And if those unscouted players are consistently good and growing in key areas, it becomes obvious he's FSS sharing. Again, this runs into the problem of the coach avoiding detection just by scouting the state (after having shared FSS) but still, let him at least pay the scouting fee.
I think #2 is good theory but it really doesn't prove much. Last season on my Fitchburg St. D3 team I scouted an insane amount of states including Hawaii (my school is in Mass), Minnesota and Arkansas so by looking at it if I did have another team in that world one could think I was scouting for another team when that definitely wasn't the case.
1/11/2011 12:26 AM
Posted by tianyi7886 on 1/10/2011 11:06:00 PM (view original):
And there are two easy solutions which easily allows multiple teams, and prevent/or at least weaken the effect FSS sharing:

1) Make it so that the only way to recruit a player is to have scouted the player, either via a scouting report or via FSS scouting of the state. You cannot sign a player without scouting. This means even if a coach FSS shares, he still has to spend money to scout the state. Sure, a coach can still get a better idea of which state to scout by knowing who he wants, but at least let him spend the money for the state as well.

2) After recruiting is over, show which state each team has scouted via FSS. Just add an additional column to the recruiting tab. This way, we can tell which coach is recruiting his team and signing players w/o ever scouting the state. And if those unscouted players are consistently good and growing in key areas, it becomes obvious he's FSS sharing. Again, this runs into the problem of the coach avoiding detection just by scouting the state (after having shared FSS) but still, let him at least pay the scouting fee.
I don't like solution number one.

In the situation I described above, I should still have the *option* of signing a player without knowing his potential, I would just bear the risk that he ended up having a bunch of lows.
1/11/2011 12:28 AM
Posted by kmasonbx1 on 1/11/2011 12:26:00 AM (view original):
Posted by tianyi7886 on 1/10/2011 11:06:00 PM (view original):
And there are two easy solutions which easily allows multiple teams, and prevent/or at least weaken the effect FSS sharing:

1) Make it so that the only way to recruit a player is to have scouted the player, either via a scouting report or via FSS scouting of the state. You cannot sign a player without scouting. This means even if a coach FSS shares, he still has to spend money to scout the state. Sure, a coach can still get a better idea of which state to scout by knowing who he wants, but at least let him spend the money for the state as well.

2) After recruiting is over, show which state each team has scouted via FSS. Just add an additional column to the recruiting tab. This way, we can tell which coach is recruiting his team and signing players w/o ever scouting the state. And if those unscouted players are consistently good and growing in key areas, it becomes obvious he's FSS sharing. Again, this runs into the problem of the coach avoiding detection just by scouting the state (after having shared FSS) but still, let him at least pay the scouting fee.
I think #2 is good theory but it really doesn't prove much. Last season on my Fitchburg St. D3 team I scouted an insane amount of states including Hawaii (my school is in Mass), Minnesota and Arkansas so by looking at it if I did have another team in that world one could think I was scouting for another team when that definitely wasn't the case.
I scout at least 10, sometimes up to 20 states in D3 as well. I don't think scouting a bunch of states makes it look like you are sharing FFS. If you scouted 20 states, and ended up signing 2 players you didn't scout at all, that would be sketchy. Similarly, if you scouted only 3 states and signed all your players from non scouted states, that would also look extremely sketchy. 
1/11/2011 12:39 AM
123456 Next ▸
Multiple Teams in One World Topic

Search Criteria

Terms of Use Customer Support Privacy Statement

© 1999-2026 WhatIfSports.com, Inc. All rights reserved. WhatIfSports is a trademark of WhatIfSports.com, Inc. SimLeague, SimMatchup and iSimNow are trademarks or registered trademarks of Electronic Arts, Inc. Used under license. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.