FOSS gamedev and creative worlds

Hi,
how can I (can I at all?) allow or restrict login to my server? Is there any players list I can manage? Like add somebody's nickname and password?
I saw files auth.txt, ipban.txt, env_meta.txt and map_meta.txt, can anybody explain it to me pls?
Thank you.

auth.txt is users list, with their rights (in format name:passhash:rights)
If you wanna to create a whitelist-server, feel free to use my commits:
first to disable automatic registration
and second for "/white nickname" command that sets random password for new or existing user

xyz wrote:auth.txt is users list, with their rights (in format name:passhash:rights)
If you wanna to create a whitelist-server, feel free to use my commits:
first to disable automatic registration
and second for "/white nickname" command that sets random password for new or existing user

So it means forking?

No, editing them will give the desired effect, e.g. User: 1337 = banned, no build, User: xyz = build and so on.

Ip ban bans peeps from joing from one Ip address. E.g. 10.20.30.40 = user 1337 and xyz. It stops them from joining from the same pc. Even though it was the same guy.
E.G. 1337 griefs. 1337 creates xyz, griefs again. 1337 and xyz banned by auth.txt, same guy makes comrade, griefs again, bans ip, that guy can't join no more.

@xyz, sorry for using your name, I just had to.

env_meta and map_meta are for the map storage and seed. Seed is the landscape you see. I think. And, no forking.

Jordach wrote:No, editing them will give the desired effect, e.g. User: 1337 = banned, no build, User: xyz = build and so on.

Ip ban bans peeps from joing from one Ip address. E.g. 10.20.30.40 = user 1337 and xyz. It stops them from joining from the same pc. Even though it was the same guy.
E.G. 1337 griefs. 1337 creates xyz, griefs again. 1337 and xyz banned by auth.txt, same guy makes comrade, griefs again, bans ip, that guy can't join no more.

@xyz, sorry for using your name, I just had to.

env_meta and map_meta are for the map storage and seed. Seed is the landscape you see. I think. And, no forking.

Thank you, but I meant that links to disable automatic registration and whitelist...
And I run Windows.

I clearly see how auth.txt and ipban.txt work.
I try it from the other side. Instead of editing source code for disable automatic registration etc. can I make auth.txt file READ ONLY and prevent automatic registration (login) by doing this?

My guess is that making auth.txt read only will not prevent new players from logging in, because auth.txt isn't re-read as long as the server is running.

Once (and if) my patch setpassword is included, you can set default_password in minetest.conf and new users will only be able to log in if they know this password.

In the meantime you can set default_privs = shout (instead of the standard default_privs = build, shout) so new players can't place or remove blocks. You can then give individual users build rights with the server command

kahrl wrote:My guess is that making auth.txt read only will not prevent new players from logging in, because auth.txt isn't re-read as long as the server is running.

Once (and if) my patch setpassword is included, you can set default_password in minetest.conf and new users will only be able to log in if they know this password.

In the meantime you can set default_privs = shout (instead of the standard default_privs = build, shout) so new players can't place or remove blocks. You can then give individual users build rights with the server command

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

/grant <username> build

Great, at least something. THX!
BTW: I hope your patch will be included in future, at least in some kind of mod.