AWarn 3.4 - Robust warning system

[MrPresident]

Hmm, I will have to test this when I'm fully recovered. I do all of my testing on a local listen server. I recently set up a dedi server in my room and I will start using that for final release testing.

[delagious]

You know you're supposed to be typing those on the server console or rcon, right?
Are you?

Yeah, MrPresident pointed that out to me earlier and that fixed my first issue of it not working because I was doing it wrong.
I am using server console and getting that error message but the commands still work.

[xXBryanXx]

Is there any possible way of making it like 3 warns=kick 7 warns=ban 10=permaban or something along those lines?

[JamminR]

No, but you could find compromise and use temp ban instead of kick, then permaban.
Seriously, though the code could be written to do so, if someone requires that many warnings, I don't want them on ANY server I'm playing on, and would most likely leave before they got banned.

Configurations (Note: these are server console variables. Run these from the server console)

ulx_warnkick_num [number] - this console variable will set the number of active warnings a player should be allowed to receive before being kicked.
ulx_warnkick_decayrate [number] - this console variable will set the amount of time (in minutes) before a player's warnings are reduced by 1. (note: a player must be connected for their warnings to decay)
ulx_warnkick_ban [number] - Determines if the script should tempban instead of kicking. (1 - On, 0 - Off) (Default: 0)
ulx_warnkick_bantime [number] - Time (in minutes) the script will ban players who have exceeded their threshold for warnings. (Default: 30)

[Eccid]

I don't think that the decayrate works. I have it set to decay after 4 hours, and no warnings are decaying. any suggestions?

[JamminR]

I don't think that the decayrate works. I have it set to decay after 4 hours, and no warnings are decaying. any suggestions?

Decayrate only decays while a person is connected.
A person could connect 4 days for one hour each before the decay would stop.
Are you sure you're counting only their connection time?

[Eccid]

I had a user that hadn't received a warning in over a month and is very active on my server, and he recently got warning banned for a third warning because the other hadn't decayed. It seems to happen with everyone as well.

[MrPresident]

If I recall correctly, the decay rate is a timer not in conjunction to the players play time. For example, the server decay timer is set to every 4 hours. If a player with active warnings joins 3 hours after the server starts he will receive a reduction of 1 warning after only 1 hour. It's not the most effective way to manage warnings, but it was the only solution I could come up with at the time. I will look onto making this more effective when I am out of the hospital.

So, for your players to lose a warning they may need to stay connected for up to 4 hours in a single session, as it does not roll over.

[Duke Nukem]

Invalid strings VnV whut do?

[Eccid]

If I recall correctly, the decay rate is a timer not in conjunction to the players play time. For example, the server decay timer is set to every 4 hours. If a player with active warnings joins 3 hours after the server starts he will receive a reduction of 1 warning after only 1 hour. It's not the most effective way to manage warnings, but it was the only solution I could come up with at the time. I will look onto making this more effective when I am out of the hospital.

So, for your players to lose a warning they may need to stay connected for up to 4 hours in a single session, as it does not roll over.

I'll just drop the time length for now, thanks for helping. Hope you get better soon.

[Duke Nukem]

MrPresident, when I try to warn someone, I get an "invalid strings" error, I'll edit it into the post later.

[krackalackin]

This mod would be perfect with a user available report system.

[nathan736]

Code: [Select]

--[[
        ulx.DecayWarnings()
       
        This function runs on a timer and removes 1 active warning from a players warning count. The player needs to be playing on the server
        when this is called to have a warning removed.
]]
 
function ulx.DecayWarnings()
        print("Decay timer running")
 
        for _, pl in pairs ( player.GetAll() ) do
        if pl.timewarned == 0 then pl.timewarned = 1 end -- prevents the line bellow from being 0 ever
            if pl:TimeConnected( ) <= GetConVarNumber( "ulx_warnkick_decayrate" ) * 60 * pl.timewarned then continue end
                if pl.warntable == nil then continue end
                if pl.warntable["wcount"] == nil then continue end
                if pl.warntable["wcount"] <= 0 then continue end
               
                pl.warntable["wcount"] = pl.warntable["wcount"] - 1
                ulx.WarningSave( pl )
        pl.timewarned = pl.timewarned + 1
                ULib.tsayColor(pl, Color(0,0,0,255), "AWarn: " , Color(255,255,255,255), "Your total warning count has been reduced by ", Color(255,0,0,255), "1")
       
        end
        timer.Create( "ULX_DecayTimer", 60, 1, ulx.DecayWarnings )
        --timer.Create( "ULX_DecayTimer", GetConVarNumber( "ulx_warnkick_decayrate" ) * 60, 1, ulx.DecayWarnings ) -- keeping as a backup
end
timer.Create( "ULX_DecayTimer", 1, 1, ulx.DecayWarnings )
http://maurits.tv/data/garrysmod/wiki/wiki.garrysmod.com/index85a1.html
martus link for player time connected
http://ideone.com/WqnGdD
link for full code
i modifyed the decay timer code to update and check if the players connected time was higher then the time you set multiplied by the times he has already been decayed during that connection (because changing the code to player connect time required this) this should solve the derpy decay code that was there assuming i did not break anything

[MrPresident]

The code you suggest would remove 1 warning from the player every 60 seconds assuming they'd been connected longer than the decay rate. This gives me an idea though.

[Eccid]

Yeah, warnings aren't decaying at all on my server. I know you've got stuff going on so it's no rush. Just reporting it.