Master Server

[tempest]

If I leave out the IP, or set it to my external IP, it tells me it fails to create a socket.

You're right, I confused it with the Sauerbraten master server, which sets the IP automatically if you don't set it. In this case, your internal IP should work.

and I don't know the exact syntax for these in master.cfg.

[SELECT ALL] Code:

ban 1.2.3.4

bans that IP (in this case 1.2.3.4) from accessing the master server, same for servban (bans that IP from registering a server) and gban (bans that IP from game servers)

[SELECT ALL] Code:

clearbans

removes all bans

[SELECT ALL] Code:

adduser name pubkey

adds an auth user with that name and public key (generated with /genauthkey), can then be used to auth on servers using /auth

[SELECT ALL] Code:

clearusers

Clears all previously defined users

Hmm, the only thing being logged for me is failure to run and successful runs. Any idea why this might be?

Because I told you some nonsense up there. I confused to-server output with logging... You're right, it only logs master startup, auth attempts and log reloading.

the logfile only updates after I stop the master server.

That's probably an issue with output buffering. What OS?

Any way to make it log to the terminal/command prompt?

Not without source modification. Except tail -f master.log, of course.

Sorry if these questions are ridiculous, but it would be easier if there were docs.

They're not ridiculous. But re docs: I think you're the first who ever asked about this stuff. It just wouldn't pay off to write docs :P

I'm also wondering about the compatibility with v1.0, how could I make this work with previous versions? Or if there was a different type of master server for 1.0, how can I run that? I read the README.txt in the 1.0 CubeMS directory and it says you need some knowledge of IIS 5+, MSSQL and ASP.NET to make any use of it, and I don't know about those things. Any help to get that setup

"IIS 5+, MSSQL and ASP.NET"... I won't (and can't) help you with that. :P
The old master system was based on HTTP. You could either write your own master for that (using e.g. an FCGI application, a self-contained server or even a PHP+MySQL combination), or adapt the new master server to accept HTTP requests.