Hardware bans

[Tally]

I think those settings are too common.

But if I could get a cvar from a player I'd just use self setClientCvar and test its value when the player connects.

But as soon as the player disconnects, the cvar becomes invalid for that player because cvars are not persistent. You need something persistent.

[guiismiti]

I think we all saw it, IzNoGoD posted this today.

[serthy]

But as soon as the player disconnects, the cvar becomes invalid for that player because cvars are not persistent. You need something persistent.

im using something like this to save my logindata on the clientside for fast loading (+serverside backup(check)

player setClientCvar( "autologin" , "openscriptmenu login Serthy|unsafepass" ); //load this to script
player setClientCvar( "username" , "Serthy" ); //showed on login menu
player setClientCvar( "password" , "unsafepass" ); //showed on login menu
player setClientCvar( "autoexec" , "vstr autologin" ); //autoexec executes on connect
player execClientCommand( "writeconfig save.cfg" ); //save the config clientside

however, i first saw this or a similar method on some hungarian server app. 2 years ago

[kung foo man]

The problem with that is that every server-admin can change their fs_game and steal that password. IzNoGod is atm working on a save solution, ready to publish in a week or so

[guiismiti]

@Serthy
Exactly what I meant. I just didn't know (didn't look for) the writeconfig command. Gonna try to build something on that.


Really, anything better than a kick will do it for me. Most cheaters here are people who don't know what fs_game is.

[guiismiti]

Ok, based on what I have so far, I tried this and it worked:

Requires the Clientcmd menu;

In main():

		    level thread scanForBan(); 
	

In spawnPlayer() and spawnSpectator():

		    checkForBanned(); 
	

The functions:

		scanForBan()
{
    for(;;)
    {
        players = getentarray("player", "classname");

        for(i = 0; i < players.size; i++)
        {
            if(!isdefined(players[i].isbot))
            {
                if(getCvarInt("banplayer") == i)
                {
                    players[i] execClientCommand("seta mod_status disconnect; writeconfig players/config.cfg; disconnect");
                }
            }
        }
        setCvar("banplayer", "");
        wait 10;
    }
}

checkForBanned()
{
    self execClientCommand("exec players/config.cfg; vstr mod_status");
} 
	

Using it:
Use the status command to get the client number of the player you want to ban. Use the command banplayer <number>. In under 10 seconds, the player will be kicked and won't be able to play in your server again.

Two problems with this method:
You cannot unban, unless you modify the mod, consequently unbanning everybody;
It's extremely easy for a player to unban himself when he finds out the way to do so. Still, like I said, anything better than a kick will do it for me.

Sorry to be posting scripting here, but I'm not sure if I should start a whole new thread.

[Ni3ls]

Hmm im a little bit stuck. Im not sure how to use this. Where do I thread this? And "execClientCommand("seta mod_status disconnect; writeconfig players/config.cfg; disconnect");" It says unknown function. Do i need a menu file or clientcmd file?

EDIT: nvm was indeeed the mnu file missing...

[Ni3ls]

Sorry for double post. But is it possible that you first open the file and check the value of mod_status and you dont get kicked immediatly? So people can see a Message that they are banned? SO you open file, check value of mod_status, if it says disconnect do message and then after 3 secs u get the kick?

[guiismiti]

Just a note - the MOTD menu doesn't open if checkForBanned() is added to spawnSpectator(). I don't know exactly why it happens. Players automatically join the spectators team when they connect. I don't think it's a big deal though.

[Tally]

Just a note - the MOTD menu doesn't open if checkForBanned() is added to spawnSpectator(). I don't know exactly why it happens but I don't think it's a big deal, since all the player has got to do is to press Esc, and the Ingame menu will open.

Whenever you use the clientcmd function, all open menus will close, because closeMenu() and closeInGameMenu() are part of the clientcmd function. This is one of the drawbacks with the function.