@Blyzz.com nice to hear!

@ardu, workl in progress bud, hopefully, I'll have a more turing complete product at some point :-)
thanks for using dizcord!

great for discord server u should consider install this if u have linux hope we will get some update on this. For a beginner user linux was kinda hard to run it its kinda hardcoded in my opinion with wher are files located so u have to change it manualy

I really love your mod - and Linux! <3

@Blyzz.com
Well, too bad there's no way to use this on Windows at the moment.
Hopefully you will be able to do it in the future!

Hi @Mihalich™, yes, that's correct, this was built using BASH with specific references to the file locations on a Linux server. But, what I might do at some point is refactor this to Python with the intention of getting it working on Windows. However, I will probably only tackle this after B42 is released.

Hi!
Am I right to understand that there is no way to run this on Windows ? Why is that ?

@B4N5TER: awesome, thanks for your input. As you can see I've made my code open-source, and available on Github. You're welcome to take whatever you like. Also If you're in the mood feel free to contribute as well. I know I'm not the best coder out there and hoping to find more people to contribute to make it better.

Also the restart command does indeed take an argument, i've set mine up to take a maximum of 5 minutes though, and if there's no argument, then it defaults to 5, sending in-game warnings to anyone that has their text chat window open every minute, then at 30s, 10s, 5,4,3,2, and 1s - might be overkill, but I kinda like the sense of urgency it creates. Also warnings to discord for the on-minute events.

I do something similar to what this does for my server. I'm also using screen.

I've briefly looked at yours after a friend sent it to me but there's a couple things I do differently. Not saying they're better but food for thought.

My shutdown script takes an argument for how many minutes and then warns the player at logical increments, e.g.
pzres 18
- "shutdown in 18 minutes"
- "shutdown in 15 minutes"
- "shutdown in 5"

Also on my list of things to do is to implement a queue system, then send commands to the queue system, because when I send commands at the same time another command is being sent to the screen sometimes it combines the output causing gibberish.

I'm currently thinking the most resilient way to do this is to have most of my commands check if the queue system is up, and if it's not up, send it directly.

I've noticed that some actions (e.g. rewhitelisting) can mess with the server ingame experience if you don't rate limit them.