The steamconnection class has been made more abstract, therefore the program has been fundamentally changed across classes. For instance userhandlers no longer will store users as STEAMID's but instead as a generic User class with an identifier. Furthermore userhandlers and "application interfaces" are independent and interact via subscribing to each other's events.
To show this new structure, a consoleinterface class has been created, which simply posts each message to the console.
This has caused limitations in the way the userhandler and applicationinterfaces interact (something as simple as getting a username from a STEAMID or checking if a user is online can be much more difficult as the userhandler doesn't know which applicationinterface can give information) but it has allowed for new structures within the code (for instance, a single application interface can relay to multiple UserHandlers).
The steamconnection class has been made more abstract, therefore the program has been fundamentally changed across classes. For instance userhandlers no longer will store users as STEAMID's but instead as a generic User class with an identifier. Furthermore userhandlers and "application interfaces" are independent and interact via subscribing to each other's events.
To show this new structure, a consoleinterface class has been created, which simply posts each message to the console.
This has caused limitations in the way the userhandler and applicationinterfaces interact (something as simple as getting a username from a STEAMID or checking if a user is online can be much more difficult as the userhandler doesn't know which applicationinterface can give information) but it has allowed for new structures within the code (for instance, a single application interface can relay to multiple UserHandlers).