|
Quote: |
|
|
|
|
Originally Posted by OhMrHanky |
|
|
|
|
|
|
|
|
Dude, I play with the falcons exclusively every year. In M18 this past year in franchise, I tried signing Ryan during the season a few times and think I was offering him appropriate money and contract length. He absolutely refused all attempts! Lol. I couldn’t believe it. He won 2 SBs for me at that point. I couldn’t believe it. I actually had to sort of scramble and draft a QB in the next draft. I hadn’t planned on that at all. I couldn’t believe he dipped out. He went to KC, and I beat him in the next SB with my rookie qb, or maybe I had a 1 year above avg guy I had picked up for a roster spot the previous year. So, actually, I think I was lucky to have picked a decent guy the year before in the 2nd or 3rd round. I then saw Ryan on the ravens as well.
And yeah, it just killed me. I truly don’t expect to see Ryan ever play for anyone else. He’s a stand up guy. He’s tried to win here in atl. I think he really just wouldn’t want the change. That being said, maybe if he’s still playing at 38-40, maybe the falcons would draft his replacement and whatnot. But, it was still shocking he left my franchise when he did. Lol.
Sent from my iPhone using Tapatalk
|
|
|
|
|
|
Feel like it wouldn't be THAT hard to layer in some pretty basic negotiation design into the design they already have in place:
- Display what the player is asking for. This is a higher # than the lowest they'll accept (which is of course never shown). If you offer what they are asking for, they accept 100% of the time. How much higher their asking price is above their lowest acceptable offer is would depend on a fairly basic calculation, including # of years tenured with team, the predictable trait that is already in the game, perhaps a positional modifier (e.g. franchise QBs typically don't walk).
- Display a general 'avg salary' of players at the same position near their OVR. This is probably a low #, because salaries increase over time. But is a starting point for the team to benchmark against & determine if the player is asking for a pie-in-the-sky contract. AND this is used for "lowball" refusal logic, e.g. if a player is asking for $20M/yr and the avg salary for an elite player is $15M... the team comes in offering $8M, that can piss off the player and he has a chance to shut down negotiations. The team comes in offering $15M and he says no but the conversation continues. Perhaps the next week you could even have the player lower his asking price... or not, depending.
- And that's all you'd need. Some basic logic around showing what the player wants, a hidden value of what he'd accept, and some kind of benchmark for what the avg salary of similar players are to prevent well-intentioned GMs from accidentally lowballing & pissing off a guy because they truly don't know what qualifies as a lowball offer.