Posted by cburton23 on 2/4/2016 12:08:00 PM (view original):
Posted by gillispie1 on 2/3/2016 6:39:00 PM (view original):
Posted by cburton23 on 2/3/2016 6:23:00 PM (view original):
This does bring up another issue that has been discussed before and that is the inability sometimes to get a player to stop considering you. Even if it is not a battle you may not want to look over extended. This happens especially with internationals. You send a few SVs find out the guy is a bum, but 2 SVs and he is in love with your school. Now, without ever offering a scholly you hit redshirt and the kid says no problem. So he is stuck on your list and there is nothing you can do. There really needs to be a "Get Lost Button."
thats my point. there ISNT nothing you can do. re-read the original post.
Sometimes there is nothing you can do is my point. If I have never offered a scholly, have informed of redshirt and the guy wont leave I am stuck until somebody else comes after him.
It should be simple, there should be an option that tells the recruit to get lost.
there is never nothing you can do. sometimes, it just is prohibitively expensive or you are broke, but in the cases you are talking about, you DO have an option. here's how it works:
you can always, assuming the funds exist, go through cycles of, offer scholarship, pull scholarship. this can be done multiple times in the same HD recruiting cycle. this generates a net negative!
i have used this frequently in the exact situation you describe. frankly, i think i have ONLY used it in the situation you describe. coincidentally, i most recently used this technique to get off an international (who i redshirted, who i had never offered a ship to in the first place) yesterday. it worked. it always works. now, if you are like 50k into a battle, tied with a guy... i would not recommend this strategy :) but for pesky internationals, for 100-200 bucks, its worth it. just think of it as the cost of crafting a well-worded "get lost" message.
edit: sorry i just replied last time with the crappy "re-read the first post" message. i was tired. i should have just explained this again right then, but hopefully it works out the same in the end :)
2/4/2016 12:32 PM (edited)