What is SEAS?
Seas is an administration mod developed by me for Garry's Mod. It's a simple-to-use and customizable administration system that allows you to take control of the players on your servers. At the moment, it requires the use of MySQLOO to run however, I plan on making it be able to use the servers local database for singular servers and possibly extend SQL to use the tmysql4 module. Therefore, you will see a few areas with "if (SEAS.MISC.UseSQL) then" which are there for when I eventually get around to adding support for SQLite.
I decided to release this publicly for free as I didn't feel like it was worth selling something like an admin mod on GModstore especially considering there are alternatives out there already such as Moderator, ASSMod and ULX. I thought why not try and release an admin mod that's different than the rest and easy to use so here we are now.
Features
SEAS comes with a handful of helpful handy commands (20+ by default) which you can either add to or remove yourself in sv_commands.lua.
Comes with 3 main methods of executing commands:
A defined IN_KEY in sh_config.lua to open up a dmenu for quick commands.
At the moment, if you add any new commands you have to manually add them in yourself; shouldn't be too difficult I have commented where appropriate.
An admin panel accessible via /admin to manage players in a quick and easy list and button format.
Simply click on a player on the left and click on the button to manage them.
Quick commands will issue instantly, other commands will issue with the submit button depending on arguments.
A chat command system for those that prefer to let the typing do the work.
A help command brings up a list of commands available to your usergroup.
Player targeted commands are as follows: /<command> <playername> <args>
Duration targeted commands can be executed like so:
Default: /ban Doubleedge. 60 Disrupting gameplay.
Identifiers. Example: /ban Doubleedge. 1y2m3w4d5h Because I don't like him.
You can also specify identifiers in any order or on their own such as w for weeks and so on.
You can do double digits too such as 10y but anything higher than 2 digits won't work.
Ability to change the look of the derma menus for warnings and admin management panels via sh_config.lua.
Ability to issue timed punishments for player chatting via text or voice as well as the normal ban.
Highly customizable sh_config.lua file for managing things such as immunity.
Server logger to log events that occur on your servers.
These can be viewed via the logs command.
Planned Features
Add support for SQLite server databases for singular servers.
Add ability to target all players connected.
Log the following:
Player connections.
Player disconnects.
Add admin tags. Currently SEAS.Chat.Tags is unused.
Save a record of punishments issued to a player.
Ability to import bans from ULX.
Media
https://files.facepunch.com/forum/upload/294834/9f7bce63-9b8b-4ea6-95f9-acbab9564a89/gm_construct 2018-9-7 22-32-48.webm
(Please note that for some reason, DMenus don't show in gm_video so you won't be able to see the demonstration of the menu, there are images below to compensate for this)
https://files.facepunch.com/forum/upload/294834/00871f18-1558-4100-bcc1-92786b844cc1/image.png
https://files.facepunch.com/forum/upload/294834/d6c1cd53-0e58-4440-a60a-154f8e9325a1/image.png
Download
Please follow the readme provided on the github page on how to install this on your servers and how to set it up.
https://github.com/doubleedger1/SEAS
FAQ
I have an issue to report, where should I post this?
You can report an issue here: Issues · doubleedger1/SEAS · GitHub
Make sure you title your issue with [BUG/ISSUE].
You can also report issues here if you wish however I cannot guarantee I'll see it in a reasonable amount of time.
I have a suggestion, where should I post this?
As with issues, you can suggest here: Issues · doubleedger1/SEAS · GitHub
Make sure you title your suggestion with [SUGGESTION/IDEA]
How often will you be working on this?
At the moment I am putting a few hours in every day here and there. However, updates, additions and removals will be slower once I begin completing my masters at university and my new job.
Why am I required to use MySQLOO in order to use the addon?
At the moment you are forced to use MySQLOO to use this as I haven't incorporated support for SQLite. The config line is there in preparation for when I eventually do so and then you will no longer require the use of the MySQLOO module. I also have plans to use tmysql4 in the future but have no confirmed time frame of when that will be.
I want something done custom, could you do this for me?
Depending on what you want done I may be able to do it for you. However, if you want this doing specifically for yourself instead of everyone else I may ask you for a fee to do so as you are asking both for a private feature and for my time outside of the time I am giving to the public project.
A new update has caused a problem with my database, how can I fix this?
If I've changed something to do with SQL queries you will often find that I've either added a new table for the database for a new feature or changed a table to accommodate for a new feature. This is because I only check if there is more than 0 tables and if there is I do nothing to prevent overwriting. If there isn't, SEAS creates the tables in your database for you. You can try ripping out the individual SQL codes in the SEAS:CreateTables() function and using it alongside lua_run in console to manually do it as that should fix the problem.
Assmod nostalgia
You really should be using CAMI, all the other major admin mods do and it's better for compatibility. GitHub
Added it to my to-do list.
Really cool idea and easy to use interface. Good luck with this!
Sorry, you need to Log In to post a reply to this thread.
