|1 person marked this as a favorite.|
The vast majority of rules tell you what is allowed/what you can do. When the rules are silent on things, it is because they aren't allowed unless an exception is stated (as in using a standard action to make a move action). This is what an exception based rule set is. If they were to do it the other way (telling you what you cannot do) the game rules would literally be a collection like an encyclopedia set. Obviously that isn't a good idea for a game, for numerous reasons.
In order for an "action" or "event" to be allowed, you need to provide a rule to show you can do it. There is no such rule for using move to free or swift as a blanket statement (there might be a class ability or such that does in very narrow circumstances, I haven't looked as it isn't pertinent to the OPs question).
Basically if you want to do something you need to find the rule that allows you to do it. That is just the way the rules set is made/set up. And it is why the argument of " the rules don't tell me I can't " is so obnoxious, because once someone gets to that point you have to realize that the person saying that doesn't really understand the core fundamentals of the game mechanics/rules.
It absolutely isn't that the rules are "unclear" it is that people want something from the rules for whatever reason, and the rules don't allow it. And because there are no rules regarding it, they try to work in the action they want either with "it doesn't say I can't" or "they obviously meant to allow it and didn't say anything", when it is plain as day that the rules don't have any way to allow the action/event.