It's a relic from the start of the project where actions would have their own object, but a network action object still has a "NetworkActionType" to specialize the action. It makes little sense now to have this double up of methods to dispatch actions within Procon.Net
NetworkActions should remain in place of Commands, as they should really be renamed to "Intents" since they may fail from the protocol not support an action, but it's all asynchronous so you don't get immediate feedback.
Anyway, NetworkActions should remain but the individual objects "Ban", "Move", "Raw" should just be combined into the single (currently abstract) class "NetworkAction" and the only way of dispatching done by looking at the NetworkActionType.
If this is done then Core can then dispatch the command using the name within NetworkActionType and permissions can therefore be setup on each NetworkActionType, allowing for greater fine tuning of permission sets.