Release Final 1.0

No large updates for the 1.0 Release. However, it is much more stable and normalized in the database!

What's new

• The database is more normalized! Match spectators, teams, and the like that was stored with PickleType has now been normalized and would be compatible with anything that can convert rows of data to JSON! For example.

• Minimum players ready! Match creators can now define how many players need to be ready before the match begins vetoes. Resolves #128 128

What's changed

• Fixed issue #166 where users were not able to see the "Total Matches" count in the "Your Seasons" tab.
• A bunch of super admin issues and admin issues were fixed. Thanks @TandelK for fixing those and pointing them out.
• Server redirection was fixed as well, whenever a super admin edited a server that was not their own, it would not direct back to the correct page, resulting in a 404.
• Issue #172 was resolved as well. Now only admins/super admins/season creators can see and add matches to their own seasons. This is probably for the best as you wouldn't want random users adding in matches to a season, as it could skew scoreboard results!

Bugs, Questions?

• Please create an Issue. This is definitely a good project to become a starter in Flask and Python, as it encompasses a lot. I won't put this repository into read-only for the foreseeable future, so feel free to leave issues, create PRs, etc.

What's next?

• Nothing! This webpanel has gotten my small (but actually growing) league through seasons. From 5 teams to 15 now, it still records stats as needed. Servers respond well, and even running on a raspberry pi, this project holds its own fairly well.

Thanks to

• Absolutely everyone who has helped me, everyone who has used this panel, and everyone who has interacted with me. Maybe one day I'll see this panel in use in somewhere where I wasn't involved. It's been an awesome experience, and the amount of things I learned has been great.

-Phlex

🤙

Release 0.6

Few new updates for the latest release. Made some minor changes and hack fixes until issues are resolved in the plugin.

What's new

• No new features implemented.

What's changed

• Removed compression from the System2 portion of the api_stats, as we are not quite using it as intended. Will need to revisit implementation at a later date. Resolves #142
• Team leaderboard was not getting proper data for matches. Included a better query to ensure there are winners on matches. Resolves #145
• SuperAdmins and Admins can now see anyone's matches. Changes were made in the check to better verify if the user was an administrator or higher. Resolves #147
• Some more explanation was put in the configs, so it's a bit more explanatory as to what is required in the Admin and Super Admin sections of the configs. Resolves #149 (thanks @Mikkeldk!)

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!

What's next?

• Converting System2 to maybe use cURL library instead, as it would be a bit lighter-weight and more documented than System2.

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!

🤙

Release 0.5

Few new updates for the latest release. Made some minor changes and hack fixes until issues are resolved in the plugin.

What's new

• Literally nothing! Just some changes to existing features!

What's changed

• Enforce teams has been added back. We're going to try changing maps now, in order to have the enforce_teams to go into effect.
• Match dates and season names are now on the match page. Resolves issue #129.
• Total matches are now shown on the /seasons page for every season. Resolves issue #132.
• Bugs squashed from match backups, divisions by zero, and seasons not being edited properly.

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!

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!

🤙

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!

🤙

Version 0.3

Made a few large scale changes with this release, also with some hidden features that may not be seen easily, so here they are! Please run the pip install under your virtualenv as well, since the Flask version was upgraded.

Version 0.3

What's new?

• Seasons now have a max limit defined in config
• Safe delete cancelled matches on your match page (/mymatches).
• Define spectators for matches. Constant spectators can be in the config, and comma separated lists can go in the match creation page.
• Player leaderboard and Season wise player leaderboard now shows player stats based on the platform.
• Stats download: A user can now navigate to the match ID via url and download the stats in CSV format. For example /match/<int:matchid>/map/<int:mapid>/csv will download the player stats of a map in a series.
• You can now enable and disable knife rounds in the match page.

What's fixed?

• Check auths on match creation now works properly. Be sure to have get5_check_auths 0 in your get5 config!
• Leaderboard was aligned and data tables were added.
• Deleting a server no longer breaks match page as it isn't needed to view the match.
• Fixed APIstats logic in order to compress files. Has yet to be tested.
• Screenshots updated.

TODO:

• Toournament API features
• Convert all tables to datatables to make everything sortable.

Special thanks:
All of you who reported bugs and was giving me reason to fix and improve the web panel!

Attached will be the compiled version of 0.3 of get5_apistats, but I have yet to test, so if you are having troubles, please use version 0.2 and report any bugs.

Version 0.2

I've decided to change the version convention, as I think these are major changes, but I don't think I'm ready for a full release just yet. So this is a release for 0.2 which is on a stable build. I also wanted to draft some of the current features that are in place. Everything in here should be ready for use by everyone and stable enough to run on majority of systems!

Release 0.2

What's new?

• /teams now presents all public teams.
• Teams can upload logos to the server.
  • Logos MUST be 64x64 and less than 16kB in size, in either SVG or PNG.
• Dependencies have been updated
  • No more known vulnerabilities on the project, yay!
• MAXPLAYERS is now a dynamic variable.
  • This means that you can set how many players per team you want before you start the application. It is recommended to set this once and leave it, however. As if you add in more, and then reduce, there will be existing players on teams, unless you remove them before shrinking team sizes.
• Audit tables exist. Track which user does what! Really useful for matches, we now log every call that is made on an rcon command, and team edits are now stored to show who edited a team.
• Optional Player name assignment on teams.
  • Just like the pro leagues, we can use get5 to use keyvalue pairs and load names from a file. This is to prevent having people change steam names and not knowing who they are throughout seasons.
• Automagic FTP Demo Uploads.
  • The new API stats plugin generates a config file where you can adjust a few values, like FTP address, port, username, and password, as well as whether you want to compress your demos. This features requires System2. Note this feature has not been widely tested, so bug reports are welcome.
• Site header is now within the config file. So you can change the site header to be whatever you want!
• seasons links are now based on ID. If you wish to view a users seasons it can be found via /seasons/user/{user.id}.

What is on the TODO List:

• Toornament API Integration

Attached to this release is 0.2 of the get5_apistats. I've mainly added in the logic for demo uploads under a call, and sent off a request to the database, and when the demo uploads there should be a download button on the web. Also there is currently a forfeit bug, but I'm not entirely sold on it being an API mistake, but could be a get5 mistake.

Special Thanks To

@Mikkeldk For doing various testing, much appreciated!
@TandelK for fixing a few mobile layout issues
You, for supporting this application!

Version 0.11

Small hotfix which includes showing the stats on the matchpage for each user, as well as updating the readme.

I think with these feature completions, I can now rightfully state that this is the 1.0 release of the modified get5-webpanel on my end. I don't think there was any other features and fixes I wanted in this release as it would take extensively longer to finish. Right now, Seasons and stats have been implemented, as well as a JSON API call to get the stats of matches. As I continue development into this panel, I'll probably be more open to features once the ones I want to finish are completed, such as audit tables and more background-work, than new features. I would rather have something that is more complete and secure for larger organization use, than one person running the show on the website.

Included in the zip is a compiled get5_apistats.smx which allows users to see the results of vetoes on the webpage as well, the source is included for this, too. Some very minor changes that won't break anything in the current build of get5. Hopefully.

Version 0.1

Merge pull request #58 from PhlexPlexico/development

Release 1.0