Jump to content
  • GFLBans


    Aurora
    • Start Date: 07/27/2018
      Completion Date: 01/02/1970
      Expected Completion Date: 08/18/2018
     Share

    GFLBans is going to be a full replacement for sourcebans that replicates much of its functionality while improving upon areas where sourcebans falls short.

     

    Specific Improvements that I plan to implement

     

    • Speed improvements, currently it takes a few seconds to load the bans/comms list. With caching and better-designed tables (possibly better web code too), we can make huge improvements in this area.
    • Multiple permission models: Better handling of admin ranks for games that aren't sourcemod based (GMOD, Minecraft, rust, unturned)
    • Support games that don't use steamid. (Maybe)
    • Additional methods of detecting ban evasion
    • Bans are submitted and queried through an API instead of a database connection. It's easy to do a lot of damage in a short amount of time with direct database connections. (DROP TABLE bans; DROP TABLE admins;)
    • Integration of Admin applications with the ban system
    • The ability for a server to still use the ban system, while ignoring other servers' bans/comms (I.E. wanna be able to use web comms, but don't want other servers' commbans affecting a particular server)
    • Ability for admins to issue server specific bans. (Say GFL opens a serious rp server and the punishments are kinda harsh; we could restrict bans made on that server to only that server. Wouldn't apply to hacking/really bad offenses)
    • Using steamid64 (community id) over steamid32. (Due to it being a number instead of a String, we can do more efficient sorting in database, resulting in faster lookup times) Also, admins can worry less about all that hassle about the first bit being 1 for some games, and 0 for others.
    • Ability for admins to set 'fallback passwords'. The use of these would be that admins could still access sourcebans even if steam's openid is broken/down. (Passwords would have security requirements, obviously, and to prevent/make it harder for admins to give their passwords out, 2FA would be required.)
    • (Maybe) For certain types of bans (rdm on ttt/breach), automatically attach the relevant logs to the ban so that admins don't have to worry about getting proof for those type of bans.

    I don't know when this will be complete, so I'm setting it's expected completion date to some crazy ass guess.

     

    Feel free to comment on this if there is anything you'd like to see in this.

    Edited by Xy


    Leader: Aurora Members - Aurora
    Progress - 100%
     Share


    User Feedback

    Recommended Comments

    Sounds good!

     

    I know you don't want to hear it @Xy, but what do you think about IPS 4 integration in the future? I mean, imagine if all we had to do was add an admin to the Server Admin group through the website and select the servers they should be admin for?

     

    It's a long shot but I do believe it should be done at some point in the future.

     

    Looking forward to this though!

     

    Thanks.

    Link to comment
    Share on other sites
    6 hours ago, Roy said:

    I know you don't want to hear it @Xy, but what do you think about IPS 4 integration in the future? I mean, imagine if all we had to do was add an admin to the Server Admin group through the website and select the servers they should be admin for?

    The API should allow for something like that.

    Link to comment
    Share on other sites

×
×
  • Create New...