Correct. You cannot do anything to a specific player but to apply a ban.
And even that ban implementation sucks.
For instance, you have no control over the bans locally on your server.
There's one server config file that sets a ban time for all bans you apply.
The only thing you can do is apply that ban with that time you've chosen beforehand, to any player who is currently online.
The ban itself will be stored on the Master Server then - out of reach for yourself as the server operator. A pity.
So if you accidentally ban someone, you will need to unban him - which you can't.
At least not specifically that player.
If you need to unban anyone, you can only unban all players at once.
In order to somehow work around all these limitations, coconut is developing a "SturmovikServerControl" tool, but frankly it's main purpose seems to be handling dynamic campaigns and as such, it comes along as a complete overkill to us, where currently the only functionality we might want to use is the ban controller.
Probably we're gonna write our own tool to handle this issue.
The idea of coconut's "SturmovikServerControl" concerning bans is a good one: He's storing the ban locally, with quite short timeout, and the ban will simply be re-applied at the moment a banned player connects to the server.
It's an awkward workaround, but it does the trick and this is something that actually can be done from 3rd party tools by using the "Remote Console" functionality of the dedicated server, something that has been carried over straight from Rise of Flight (heck, the console client even still has ROF in it's name).
Mike