Created logic for AutoUpdateSession on login / session into it's own class and registered on the service bus to utilise subscriptions such as onGameTick.
Explanation:
When the user logs into Runelite, it'll now automatically track there stats at the start of the session. There is some logic which is applied in order to ensure that this is the first login for the user and / or the start of a new "session".
Check if the player has already been tracked, if the player has not been tracked then a request will be sent and the player / next time that a session can commence.
If the player has already been tracked it checks the following criteria before running:
Is the player logged in.
Is the player name defined in the plugin (WomUtilsPlugin)
Is it currently performing an update.
Has the player already been tracked during the current session.
Features:
Tracks a player on first login.
Allows for multiple players to be updated for the current session for example:
Log in as Arv Cork and play for 2 hours.
Log out of Arv Cork and play as Zezima -> Zezima will get updated now.
Logout of Zezima and log into Arv Cork again, before the 24 hours session is completed (player will not be updated) due to it being classed as the same "session" + this will automatically get updated on logout anyway from my understanding so save resources.
Re: #27
Changes:
AutoUpdateSessionon login / session into it's own class and registered on the service bus to utilise subscriptions such asonGameTick.Explanation: When the user logs into Runelite, it'll now automatically track there stats at the start of the session. There is some logic which is applied in order to ensure that this is the first login for the user and / or the start of a new "session".
Check if the player has already been tracked, if the player has not been tracked then a request will be sent and the player / next time that a session can commence.
If the player has already been tracked it checks the following criteria before running:
WomUtilsPlugin)Features: