As I'm writing the GUI, I realize it may be a good thing to start preparing the GUI for i18n elements. I have to learn how to use the gettext library and replace text with locale elements.

Print_commentary is not an appropriate name. Refactor to get_commentary.

Reasons: this function will not print commentaries. It will only get them. It's not its job.

The match_live handler should then notify the observer if a new commentary came up, and then should print it.

• Refactor get_commentary
• Implement Observer
• Implement Notifier
• Make observer-notifier work

Create the game's first logo and desktop icon.

• Implement Picks and Bans with a GUI for the user to choose the proper Bans.
• Implement an AI to pick and ban champions as well, based on player's specialty

• Enhance Team Generator
• Enhance Player Generator
• Enhance champion generators

Create a Team Logo Generator to generate the team logos automatically based on random parameters and patterns. Should follow the generator patterns that are established in #29

• Title page
• New Game Screen
• Load Game Screen
• Create Manager
• Team Management Screen
• Match Live Screen

Implement a Database Editor to edit:

• Teams
• Players
• eSport-related features, such as champions, races, or any other important feature
• Championships
• Patches

It might be a separate app that can access the db. It's not a priority for alpha release, though.

• Implement locale
• pt-BR translations

Related to #40

An observer should watch for commentaries, and a notify will post updates when a new commentary becomes available.

• Organize database in categories
• Find a better alternative than JSON or XML files
• Expand player, team, champions and championship databases

• Implement Championships
• Generate Championship names

• Date of Birth
• Preferred Champions
• Store Champion Skill Lvl
• Improve Player Name Generation
• Expand Player Nationality

• Document the code (PARTIALLY DONE)
• How to play
• Wiki
• Edit README with info about the game and in-game screenshots

Create general mockups and diagrams to illustrate how the game will be played out.

Production of a GDD defining all elements and features of the game, possible implementations and diagrams that will compose the final product.

At this point in development, I think it would be nice to have a clear idea of what needs to be implemented in some releases. Coming up with a Roadmap will be a motivation to implement the missing features, and will give me an idea of what needs to be done at certain points, focusing my attention on these points.

• Add config file with definitions
• Make it comply with the Settings menu
• Make it easier to scale fonts

I feel like to achieve what I'm trying to accomplish, I have to implement sort of an MVC architecture, to decouple rules and logic from the GUI representations.

Picks and Bans heavily rely on UI interaction to function, so I need some sort of MVC architecture to avoid implementing all logic from P&B into actual UI code.

This will help me out later on when experimenting with new UI ideas, instead of just PySimpleGUI prototype.

• Team Logo generation

• Implement game logic
• Calculate results based on player's and champion's skills
• Probability calculations and RNG
• Implement basic game events
• Implement Live Commentary
• Implement events, event generation

Match tester must show skill lvls after the game, and the skill lvl average.

Find a way to implement a match series, which means:

• Match is a best of one
• Match is a best of three
• Match is a best of five

etc...

Then we could play multiple matches in sequence.

Introduction

eSports Manager is exactly what the name implies: an eSports manager game. Based on famous franchises, such as Football Manager and the now deceased Championship Manager. This game was born out of a dissatisfaction with the current available options on the market that concern eSports.

The idea is to bring the gameplay experience you would find in these legendary manager games, without any of the limitations that the other alternatives present to the player:

• You don't need to be connected to the internet to play this game
• You don't need to create an account on a website
• You don't need to wait hours to get to play a match
• You don't need to set up a hundred different things for each player of your roster to get them to play better each game
• You don't need to buy packs of cards to have the chance of getting a good player
• No lootboxes, no pay-to-win
• No license fees
• No restrictions to what you can do with this game whatsoever
• There's no over-complicated game mechanic: most things should be self-explanatory and pretty much straightforward

Also, you should find in this game every aspect that makes each eSport unique: patch changes are going to affect competitive matches, your pick/ban choices are going to affect each match and player, each player has strengths and weaknesses that you have to explore in every match.

And yes, in this game, you may choose which eSport you want to focus on: RTS, FPS and MOBA. It is still not clear if we are going to make three separate products from this core concept, but the initial idea is to give the player the ability to choose an eSport to focus on, just in one client. If this idea does not hold up to the test of time, we may separate them in different products in the future, but the core eSports Manager will stay the same, as I believe they will all benefit from the same core.

Gameplay Overview

How will it be played?

Following the standard of manager games, the game relies on the mouse to be played, with screens and buttons to be clicked on.

New Game

First of all we will have a menu screen with basic options: "New Game", "Load Game", "Settings", "Editor", "Credits", "Exit Game". Pretty standard for most games. Nothing more that I can think of. Names are self-explanatory, except for:

• "Editor": In this editor you are going to find a database editor. You may edit eSports Teams (Logo, Names, Financial Status, League, Region, etc.) and their players. Also, you may edit the eSport itself, adding champions/races/guns or whatever component is part of the eSport. It should be a very good modding tool.
• "Settings": Configure game settings such as Screen Size, Graphics, Amount of Text during Match Live, and etc.

Clicking on "New Game" will show an option to select the desired eSport. After that, you can start choosing the Region of the Team, with the option of selecting an existing team in the database, or creating a new team from scratch. You can also choose when you want to start the season, and if the game will follow a random history, or if it will retrieve database history. If it follows a random history, random team results are going to be generated, and certain teams will carry the title of Champions of past seasons, which may also affect players' morale. If it follows a history from the database, the past seasons champions will be the same as in the database, and the game will not generate random data from other games.

After that, you can choose your manager's name and details. And then you are in the game. The main UI will feature a dashboard with information about your team, latest championship news, information on the next match, information about patches, a brief calendar, and there will be a menu that allows for navigation.

Main Dashboard

In this menu, you will find the Advance Time button, that will advance to the next day or to a defined date or even until an important event comes up (it's up to you), which might be some sort of interaction with other teams, or when the next match is close. When your team has a match coming up, the button shifts to Next Match.

Playing a Match

When playing a Match, you should define the team's formation and enter the essential pick/ban phase (for MOBAs, not clear how this would play out in RTS or FPS), and it's up to you to choose the heroes/champions used by your players.

The Match will pop up with info about the players and their champions. That's when Match Live Commentary comes up: every now and then the teams will perform an action, and their actions will show up on the user's screen, just as if there is someone shoutcasting this game.

At the end of the match, all data will be updated with KDA, performance ratings, which will affect player's performances and form later on. This means that if you're team is on a winning streak, they're going to get hyped up for next games, and this is going to increase the chances of winning other matches. Going on a losing streak, on the other hand, will demotivate your players and will increase your chances of getting fired.

Hiring players

Hiring new players depends on your financial situation. You can either approach other teams to hire them, or find new talents in the SoloQueue/Ladder. These prospects will have potential skills that can be explored, and if you practice a lot with them, they might reach their peak.

Patch changes

Every now and then the game generates patch changes that are going to affect in-game choices, more specifically picks and bans. Champions/heroes will get nerfed or buffed, and its up to you to identify that. Your players have to be prepared for these potential changes, and you have to keep practising with different champions to improve their skill lvls to avoid stalling out behind.

Sponsors

Sponsors provide ways to get financial and performance boosts. Each season you will get approached by sponsors to sign contracts, depending on the relevance of your team. If your team is very strong, bigger sponsors will offer very significant contracts. Your sponsorship depends on your team's performance, and the financial boost might come with specific requests ("get 14 kills in a match", "win against your rival", "win 3 games in a row", or so on and so forth). Every so often the sponsor will provide items that might boost players' performances temporarily or permanently. It's up to you to choose what's best for your team at certain points.

Practice

Your team has to practice regularly, so teams are going to approach you for scrims, or you can approach them to set up a calendar of scrims. You can either relegate practice sessions to an auto-manager, or you can play it as a normal set of matches and watch every step of the way. They will have Match Live Commentary as well. The other way to practice is to let your players play their usual SoloQueue/Ladder, which provide less points to your players individually, but can be fired more often than scrims.

Major championships

Winning a league might qualify your team for major championships, such as World Championship or other International Competitions. Winning these championships will provide a major financial boost and will make your name desirable for other teams.

These are right now the main aspects planned for the 1.0.0 release of the game. Further details are going to be found on a future Game Design Document.

Development

The game is developed using Python 3 (currently 3.8.3), using a Pipenv. You will find all the project's requirements in the Pipfile. You may find specifics in the CONTRIBUTING file as soon as it's ready for Contributing. You will also find every information needed to get this project running on your machine, and the code style used in this project. Please, also follow the Code Of Conduct described there, so any contributor that does not follow our Code of Conduct will be dismissed.

License

The license is GPLv3. Defined on the License document and on Readme as well.

• Following the Calendar implementation (#51) add auto match scheduling.
• Add the match dates to the Match class

Some of the ideas I had was to make player reputations (international or national). But based on that idea, I thought about of making some sort of Player Impact Factor.

Players with high impact factor influence positively on the team's win probability. One way to do that is instead of making a simple average (total of players skill level and points divided by the number of players on the team) we could use a weighted average. Thus, players with high impact factor would have higher weights.

I thought about making weights range from 1 to 5.

I'm currently very unhappy on how difficult it is to maintain the GUI event handler. Researching ways to make it less daunting.

I'm currently working on a complete rewrite of most of the game's generators, and soon I will work on the match implementation. I found that it will be much better to encapsulate most of the code in classes, so I'll be doing that from now on. All of the work will be on a 'rewrite' branch, and soon I will merge it to 'develop'.

However, rewriting everything will break all the tests. I need to take the time to rewrite all the tests as well.

Currently we are using unittest, but I'm also thinking about switching to Pytest.

Implement Save & Load feature

• Implement the roster function properly

It's important to start thinking about CI/CD, I'm still writing tests and studying a bit about it to get everything ready for a CI/CD.

• Implement player attributes
• Implement player portraits
• Champion Multipliers should be only to some champions (see #5)

Implement a Match Tester with a GUI

Describe the bug
There's a bug in the match live simulation: if a team has no lane towers but the inhibitor has not been destroyed and the EventHandler generates a tower event trying to destroy this team's towers, the game bugs out because the list of available towers is empty (None). Match does not progress, and you can't reset the match.

To Reproduce
Steps to reproduce the behavior:

1. Set a team's lane towers to all 0.
2. Set all the inhibitors up.
3. Generate a tower event trying to destroy this team's towers.

Expected behavior
The game shouldn't generate tower events for that.

Screenshots
No screenshots available.

Desktop (please complete the following information):

• Windows 10

Additional context
It's a rare bug to replicate and generate. I should come up with ways to try to prevent this, but I guess once this game is released this will become much more common. So it is a critical bug to solve.

• I feel like most of the code is already decoupled, but I think we could improve on decoupling a lot of things, such as player, teams and champion classes, so they can be reused later. As the goal for this project is to support several eSports, code reuse should be crucial.
• I also plan on reusing most of the code on another open source management game, so this should be a priority here.

• Add nationalities file which will be composed of a dictionary of regions and nationalities. Each nationality will have a sigma and a mu, which will be used to calculate the average skill of the players from that nat.
• Refactor generator methods to apply to the GeneratorInterface
• Generate a unified file for game data
• Make IDs consistent
• Decouple places that use generators

• Add a calendar table
• Refactor usages of datetime.now() to use the calendar dates
• Refactor the Settings generation
• Implement Seasons (which season you want to start? available options: 2015, 2016, 2017, 2018, ....)

• Studying TDD to apply it to this development

• Implement new Champion Name generation
• Implement Champion Release date
• Implement Champion Patch Changes
• Improve Champion Skill Lvl generator
• Champion Portraits
• Champion Counters
• Champion Lanes
• Champion Types

• Graph results of match testing, getting relevant data from tests
• Output a stats file

I got a bunch of new names for teams and players. I just have to add that to the project. Also, I think I made a fallback in case I end up scraping the .txt files.

I want to get a sense of how often double, triple, quadra and penta kills will happen in the games.

Add tox automation to test this project in multiple virtualenvs. Currently, I think this project only works on Python 3.8 and above, I have not tested it on other Python versions, but I think it will not work well in 3.7. With tox we can effectively test that and see exactly what is needed to run this project.

Create an Avatar Generator to apply to players. Could be based on this https://github.com/draftbit/avatar-generator

• Implement Match Scheduling

Create a method to play an entire championship at once, and print outcomes.

Match tester should be able to customize the teams and skill lvls.

So I can test if a fully packed team can easily swipe a very bad team.

Implement multiple simultaneous match testings in Match Tester.

• I'm studying rewriting Match Live to follow an object oriented approach, and I think we could approach use some objects here and there.
• For that I'm also studying a Design Patterns and how to apply it to this project.

I'll look different ways to reimplement the match live event handler, it looks too bloated.