Team Tags: users can tag teams with their status in the league, such as 'rebuilding', 'buying', 'selling', 'contending', etc. This would then dictate the way that the CPU conducts itself when handling the roster. A team tagged 'rebuilding' won't be trading their top prospect at the deadline or paying big money in FA. A team tagged 'contending' would be more willing to trade for a high OVR player on an expiring deal. Etc.
Player tags: users can tag players with their status on the team, such as 'untouchable', 'core', 'starter', 'on the block', etc. This would then dictate the way that CPU teams engage with those players. A player tagged 'untouchable' will not be traded for anything. A player tagged 'on the block' will almost definitely be traded at the deadline. Etc.
If, as a user, you want to go through the entire league and tag every player, you can. If you'd prefer to just tag a couple of teams or players that you want to behave in a particular way, you can. If you want to ignore the feature completely and let the CPU have at it, you can do that too. Seems like a pretty simple way to give the logic a hand whilst allowing users some flexibility.
I'd probably tag all teams and update them as the standings change, I'd probably tag the 2-3 players on each team that are truly untouchable, and I'd probably tag the top 10 or so prospects in the league. Wouldn't take long, but the transactions would probably be way more realistic and I wouldn't have to micromanage every single one.
I know nothing about coding or game design but it also seems like it should be pretty easy to implement too.
Thoughts?
Comment