Quoting: JT_Miller
Since we are ignoring NMC's for trades are we also doing that for the Expansion Draft or since they are technically waived when traded, would we only ignore traded players NMC's for expansion? Because that could change a lot of teams' protection plans.
The rule in place is to ignore for trades, but they have to be protected in expansion, unless you think they would be willing to waive IRL, which is honestly kind of vague and open to interpretation, unless we waited for the real protection lists or some kind of news was released by a player or his team. Everything else is speculative.
If I were to ask Vegas if there was an age or cap limitation to what players they would select (of their own free choice, not a side deal), I'd expect a number somewhere in the 32+ and $5M range, and I'd suggest players that are above that line would waive their NMC's for the purpose of this game. Not a perfect method, as I could see Vegas selecting Bobby Ryan if he were made available (as an example), and he might not be okay with that IRL, though I'm sure his team would.
Another possibility that comes to mind is to have anonymous voting among the GMs as to who would reasonably agree to waive their NMC.
One more possible method, and perhaps the simplest, is that only players who remain on their original teams may be expected to waive their NMC's for expansion purposes. Players who are recently traded have usually already waived their NTC's. We could "pretend/assume" that a player with both an NTC and NMC, would only be willing to waive one or the other. If he agrees to a trade, it is probably because he doesn't want to agree to risk exposure to Vegas. This is probably the easiest to implement and track for our purposes.
1. Player has NMC: He can be assumed to waive it for expansion purposes, but not to be sent to the minors
2. Player has NTC: He can be assumed to waive it, but not for the purpose of being bought out or sent to the minors by another team
3. Player has both NMC and NTC: He will waive one or the other, but only for his original team. So you can either expose him to expansion or trade him, but once he is on another team, he will no longer waive either.
Now this rule would have worked better if we had it in place from the beginning, as it's possible such players have already been moved multiple times, so we could set it to 1 additional time so those with such a player (full disclosure, I have one myself, although I plan to keep him) aren't currently left without options and ignore the previous movements.
Just some ideas that might help.
CapFriendly
CapFriendly