First off, ignore the alt business. Yes, IMO an alt cap should be in effect, but the scenario should be played according to the established rules; if you don't like them, go ahead and quit: that's your right and one that shouldn't be contested,
Umm... I have no business interfering here, seeing as how I wasn't there, but Santa did say:
what seemed to be wolf taking his ball and going home.
That is , wolf
seemed to be quitting, just as Hangtime did indeed take up his ball and go home the week before.
Now, I've flown my share of scenarios, and I've never seen a CO .eject ed. My understanding is that the .eject command is there for people who are disrupting the game, such as those who take up unauthorized aircraft and try to shoot people down; or people who willfully abuse a killshooter

ff situation.
If the CM did eject the CO (and right now all we have is Wolf's testimony), he should have at the very least informed both sides of his action. Santa's statement "seemed to take his ball and go home" implies that this was not done.
This was not an official CM crew event (in which, of course, the CM does not fly for either side). Nevertheless, these are not trivial charges.
Wolf has claimed that as CO he was unable to control the deployment and configuration of his flights within the rules of the game.
If this is the case, and if the frame did indeed start against his protest, he had every right to withhold the participation of his side.
If he was ejected for acting in this manner, then he has a valid grievance.
Frankly, I'm interested in hearing what the other parties have to say. Until then, we shouldn't take a non-response as an admission of guilt.