* Update data-logger to 1.2.0
Updated data-logger to 1.2.0
- Reorganized directories used
- Added supply tracker
- Additional values tracked during Colosseum trials
- Added discord webhook
- Added various dataviewers / utility panels in the sidepanel
- Restructured and expanded ItemLogger
- See CHANGELOG for a more detailed list
* Removed new Gson
Removed new Gson
* Removed system i/o call
Removed system i/o call
* Minor fixes+changes
Fixed an issue with the scrollbar in the items viewer panel
Ensured the combobox in the UtilitiesModePanel is disabled on startup
Updated icons
Set sidebar ordering priority to 10
* Resized icon
Resized icon to 48x48
* Added data-logger
* Thanks for catching the reflection issues. To address the "Use of reflection is not allowed" feedback properly and avoid any hacky workarounds, I realized the plugin's core architecture needed a refactor.
Here is what I've updated:
Removed Dynamic Class Loading: Overhauled the UI routing by removing the reflection-based panel instantiation and replacing it with explicit Guice bindings and a safe switch statement in DataLoggerPanel.
Removed Gson TypeToken Reflection: Removed the dynamic TypeToken reflection in FileIOService, replacing it with standard Java function parsing via the LogType enum.
Removed Method Invocation: Replaced the reflective invoke call with a direct client.getAccountHash() API call in the new AbstractLogger base class.
Let me know if everything looks good to go!
* To address the "Use of reflection is not allowed" feedback properly and avoid any hacky workarounds, I realized the plugin's core architecture needed a refactor.
I have made the following changes;
Removed Dynamic Class Loading: Overhauled the UI routing by removing the reflection-based panel instantiation and replacing it with explicit Guice bindings and a safe switch statement in DataLoggerPanel.
Removed Gson TypeToken Reflection: Removed the dynamic TypeToken reflection in FileIOService, replacing it with standard Java function parsing via the LogType enum.
Removed Method Invocation: Replaced the reflective invoke call with a direct client.getAccountHash() API call in the new AbstractLogger base class.
Let me know if everything looks good to go!
* Update data-logger to 1.1
Added Colosseum attempt logger
Added Colosseum gamestate logger
Added Colosseum screenshot logger
Added Item Storage logger
Extended Grand Exchange Logger
* PR revision based on feedback
Shifted nearly all IO operations to FileIOService
Updated README
Removed poorly defined toString() method of ColosseumWave
* Small ExchangeLogger changes; fixed totalTimeTaken
Disabled submission of new offers via the History parser
Added offer submission logic before an offer collection event fires
Defined totalTimeTaken in ColosseumAttemptLogger
* Unregister itemVaultLogger on shutdown
The Plugin now unregisters the itemVaultLogger on shutdown
* Update commit reference in data-logger plugin
Substituted log.info calls with log.debug calls
* Updated hash to correct hash
* Substituted java.awt.Desktop calls with RuneLite LinkBrowser calls
* Added data-logger
* Thanks for catching the reflection issues. To address the "Use of reflection is not allowed" feedback properly and avoid any hacky workarounds, I realized the plugin's core architecture needed a refactor.
Here is what I've updated:
Removed Dynamic Class Loading: Overhauled the UI routing by removing the reflection-based panel instantiation and replacing it with explicit Guice bindings and a safe switch statement in DataLoggerPanel.
Removed Gson TypeToken Reflection: Removed the dynamic TypeToken reflection in FileIOService, replacing it with standard Java function parsing via the LogType enum.
Removed Method Invocation: Replaced the reflective invoke call with a direct client.getAccountHash() API call in the new AbstractLogger base class.
Let me know if everything looks good to go!
* To address the "Use of reflection is not allowed" feedback properly and avoid any hacky workarounds, I realized the plugin's core architecture needed a refactor.
I have made the following changes;
Removed Dynamic Class Loading: Overhauled the UI routing by removing the reflection-based panel instantiation and replacing it with explicit Guice bindings and a safe switch statement in DataLoggerPanel.
Removed Gson TypeToken Reflection: Removed the dynamic TypeToken reflection in FileIOService, replacing it with standard Java function parsing via the LogType enum.
Removed Method Invocation: Replaced the reflective invoke call with a direct client.getAccountHash() API call in the new AbstractLogger base class.
Let me know if everything looks good to go!
