Version 0.4

Few new updates for the latest release. Had to unfortunately remove a feature as it was never working in the first place, because of how it interacted with get5.

What's new

• A new role appeared! A Super Admin is now an administrator with more than administrator privilege. A super admin can edit any and all matches, teams, seasons, and servers. Only give this privilege to people you trust, as it does reveal server rcon passwords. Be warned! They also have the ability to send rcon commands in matches.
• Adjusted administrator privileges. Admins can no longer send rcon commands to matches. This is due to regular admins being able to see any information on the server. They can also not edit teams or seasons of other users.
• Server operators! Server operators have the ability to call any rcon command on matches that they own. This is there to allow anyone to use a public server, without the server owner really worrying about any rogue commands.
• FFW matches. Administrators and Super Admins can now call forfeit wins from the match menu. If a team fails to show, or a team is barred from the league and you need to balance out standings, you can now FFW matches against teams. It provides basic information so that leaderboards will be affected, but player stats will not.
• Private Matches! During match creation, users will be able to select a boolean that will allow users inside a team (or match, if you, the match owner, add them as a sub) to view the match stats. Users must be signed in to the match panel to allow the web panel to authenticate based on Steam ID.

What's changed

• Enforce teams gas been removed from the web panel. This feature was experimental at the very most, and has caused an array of bugs with any implementation that I've tried. Since its trying to change a config setting within get5, and not api_stats, it's hard for me to make adjustments and remotely enable get5_check_auths {BOOLEAN} for the entire match.
• Cleanup of logging - just to avoid any unnecessary clutter within the log files.
• Updated the test and prod config defaults to include super admin, and updated a few tables here and there.

Bugs, Questions?

• If there are any bugs or questions, please make an issue and I will look into it. Any other form of contact for this project will be disregarded as I'll probably forget about it. It's simply to help keep my thoughts in one place, thank you!

I think I'm confident enough to state that Release 0.4 should be a good point in time to stop implementing new features (sorry, no Toournament API yet!) and move on with creating a bare API. I like the basic look of bootstrap and all, but I believe I can make something more functional and modern. So with what being said...

What's next?

• API conversion. Going to try my hand at this again and make all calls (or replicate them) into an API that will return JSON instead of calling render_template() and using Jinja2. That way people who are more talented than me can take a stab at making something more functional in a newer language, such as react. I'll eventually find some time to work on it, but for now I will focus on making a proper API. Once that's done, I think that will be release 1.0.

Thanks to

• Everyone who uses this, and everyone who has supported development along the way. Without activity, I would have stopped doing this development some time ago. So, thank you!

🤙