* 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!
* Add GEX plugin
* Fix repository URL to end with .git
* Update to commit with Gson fix
* Apply suggestion from @riktenx
---------
Co-authored-by: riktenx <riktenx@gmail.com>
* Update tutor timer to V1.2.0
Fixes issues with stale last claimed statuses, and increases startup reliability.
* Update commit reference in tutor-timer plugin
* Update commit hash for Tutor-Timer repository
Updated to use configManager.unsetConfiguration(...)
guarded by a configManager != null check where appropriate rather than complicated custom methods
* Create upper-case-transformer
* Update upper-case-transformer
Pinned JUnit back to 4.12 in build.gradle to match the expected RuneLite plugin template baseline and avoid accidental IDE-driven version drift.
* Create rune-calculator
Create rune-calculator file in plugins directory and add the repository URL and latest commit hash
* Update rune-calculator commit hash
Update commit hash to reflect removal of enabledByDefault=false from the plugin descriptor