* Update Creators-Kit to v1.5.4
- FolderTree, CreatorTreeModel, CreatorTreeTransferHandler refactored to ManagerTree, ManagerTreeModel, and ManagerTreeTransferHandler, respectively
- ManagerTree now uses Characters directly as nodes instead of ObjectPanels, and new Folder class for folder nodes
- TimeTree added which links the ManagerTree to the Timesheet
- Switch buttons removed in favour of managing Objects via Tree Drag/Drop
- Help button added to CreatorPanel to link to youtube tutorial
- Setup saving/loading updated to handle new ManagerTree
WIP
- TimeSheetPanel tab added to Toolkit. WIP, temporarily hidden
- Various UI elements worked on to support TimeSheetPanel
- TimeTree correlates of ManagerTree created for TimeSheetPanel
* Update creators-kit
Bugfix: loading Setups wouldn't properly revalidate side panel
* Update creators-kit
Bugfix: adding objects to Manager or duplicating objects in Manager wouldn't properly resetObjectHolder
* Update creators-kit
System.out removed
* Update clue-details to 2.0.3
Small fixes to improve clue despawn diff comparisons, fix some clue text for beginner/master clues, and reduces amount of processing done on menus appearing.
* Reverted incorrect clue text change in clue-details
* Create onlyree
* Update onlyree
* Update onlyree
- Adds XP Bonuses for HueyCoatl and Amoxiatl
- Adds a toggle option to prevent AoE attacks from triggering the plugin sound effect
- Fixes not loading the XP bonuses
- Prevents a ruby bolt spec from triggering the plugin sound effect
* Update onlyree
fix: Moves BufferedReader into try-with resources to automatically close it.
* Update onlyree
Fixes a bug where ignoring a previous sound effect triggering would cause the next hit to always trigger the sound effect.
Fixes handling fake xp drops so multihitting weapons can trigger the sound effect.
* Create red-clicks-only plugin
Adds the Red Clicks Only plugin, which removes the function of the "Walk here" option
* Update commit hash
Fix package name
* Update Embargo plugin (bug fix + version bump)
- Only call API route once every 3 minutes instead of on tick
- Bump version from 1.0 to 1.1
- Change description
* Embargo Plugin Update - Update side panel, bump ver, change desc
* Add check for profile type in collectionlog unlock route
* Fix for bad var name
* Update Embargo to 1.2.1
- Addresses an issue with the clientThread hanging when the GameState is set to LOADING
- Bump version to 1.2.1
* Update Embargo Plugin
* feat: Add minigame completion tracking
New:
- Update readme to include new feature information, including a disclaimer that we do not store IP address
- Bump version to 1.3.0
- Add minigame completion tracking
Fix:
- Only send STANDARD profile raid/minigame completions
- Abstract logic to keep raid/minigame completion logic in a single function, `handleActivityCompletion`
- Rename `getRaidMembers()` to `getSurroundingPlayers()` to better describe what the function does
* Remove e.printStackTrace() calls
* Update clue-details to 2.0.0
Adds beginner and master clue tracking
- This tracks them once read in your inventory, on the floor, and in the bank. Edge-cases such as dying with a clue will likely result in the tracking failing.
Add new Varlamore clues
Changes the sidebar to render more efficiently
- more clues meant more processing in the sidebar, meant a bit of chugging sometimes. This should be noticably improved.
Adds a reset button for customised tags
* removed gson instantiations from clue-details
* fix: remove deptricated widget usage in clue-details
* Update ban-list-export
Now possible to export to a google sheet and import from a google sheet.
Guides are available in the readme.
* Update ban-list-export
* Create timers-ca
* Update timers-ca
Grotesque Guardians added and Vardorvis timer now correct track the time on resets
* Update timers-ca
More bossees added and fix a problem with stopping the timer at over 1k kc
* Create monster-monitor
Tracks NPC kills and allows setting kill limits
* Update monster-monitor
Updated runelite-plugin.properties
* Update monster-monitor
Few minor updates, a few more tests. no functional changes
* Update monster-monitor
- Fixed issue with double notifications for NPC kills with a set limit.
- Ensured notifications play correctly for NPCs with unknown death animations.
- Adjusted the MonsterMonitorPanel to push NPCs added from UnknownDeathAnimations to the top of the panel, similar to normal NPCs.
- Refined the logic for handling and sorting NPCs in the panel to ensure consistent behavior.
- Ensured that the MonsterMonitorLogger handles unknown animations and logs them consistently with regular NPCs.
* Update monster-monitor
forgot to uncomment a few lines in DeathAnimationIDS after some tests.
* Update monster-monitor
* Update monster-monitor
Fix runelite-plugin.properties again
* Update monster-monitor
Enhance Monster Monitor Plugin with Interaction Timer, Duplicate Logging Prevention, and Prioritization of Last Killed NPC
Interaction Timer: Implemented a 4-second interaction timeout to ensure that NPC kills are accurately tracked during combat, especially for ranged and magic attacks where interactions may briefly pause.
Immediate Logging After Health Reaches Zero: Introduced a mechanism to capture and log the last valid animation immediately after an NPC's health reaches zero. This ensures that all NPC deaths, especially those with complex animations, are logged accurately and on time.
Duplicate Logging Prevention: Refined and optimized the logging logic to prevent duplicate entries of NPC deaths. The cleanup of NPC tracking data is now delayed until the NPC has fully despawned, preventing premature data clearing and missed logs.
Prioritization of Last Killed NPC: Updated the UI panel and overlay to prioritize the display of the most recently killed NPC at the top, regardless of whether the death animation is known or unknown. This change ensures that the most recent activity is always immediately visible to the user.
Refactor and Code Cleanup: Consolidated and cleaned up the codebase for better consistency and reliability across various NPC types and combat scenarios. The plugin has been fine-tuned to function correctly in both continuous and intermittent interactions.
Bug Fixes: Addressed issues where the plugin would stop logging kills after the first kill or fail to log certain NPC deaths. These fixes ensure that all NPC kills are tracked and displayed as expected.
This update significantly improves the reliability, accuracy, and user experience of the Monster Monitor Plugin, making it more robust in handling various edge cases and ensuring comprehensive NPC kill tracking and display.
* Update monster-monitor
Improve redundancy and accuracy in capturing NPC death animations
- Implemented immediate health check to start tracking NPCs as awaiting death animation when their health drops to zero.
- Added aggressive death animation tracking with multiple attempts to capture or log death animations.
- Enhanced despawn logging to ensure the last valid animation is logged or marked as unknown if missed.
- Updated NPC tracking methods to improve reliability and prevent unnecessary logging.
- Added Another Unknown DeathAnimationIDs
* Update monster-monitor
* Update monster-monitor
Add NpcAnimationTracker for improved NPC interaction tracking and logging
- Introduced `NpcAnimationTracker.java`, a new class dedicated to tracking NPC animations and interactions, significantly improving how the plugin monitors NPC behavior.
- `NpcAnimationTracker` registers for several in-game events, including `InteractingChanged`, `NpcDespawned`, `GameTick`, and `HitsplatApplied`, to accurately track when the player interacts with NPCs.
- Added logic to buffer unique NPC animations, enabling the plugin to distinguish between different types of animations, such as death animations, and ensuring accurate logging of relevant events.
- Implemented a grace period mechanism within `NpcAnimationTracker` to handle NPCs that despawn shortly after interaction, ensuring that the last known animations are accurately recorded and logged.
- Updated the handling of interaction timeouts, allowing the plugin to clear out expired interactions and prevent stale data from affecting ongoing tracking.
- Integrated `NpcAnimationTracker` with the existing logging mechanisms in `MonsterMonitorPlugin`, ensuring that all tracked interactions and animations are logged with precise timing and context.
- Provided detailed comments and documentation within `NpcAnimationTracker.java` to explain the purpose of each method and how the class contributes to the overall functionality of the plugin.
- Refactored parts of `MonsterMonitorPlugin` and related classes to utilize `NpcAnimationTracker` for more granular and accurate tracking, enhancing the plugin's ability to monitor NPC kills and associated events.
- Ensured that the new tracking system remains performant and reliable, even during high-intensity gameplay, by carefully managing resources and minimizing unnecessary processing.
* Update monster-monitor
Update build.gradle for Monster Monitor plugin
- Added Gson dependency for JSON handling, enabling serialization and deserialization in MonsterMonitorLogger.
- Included Lombok dependency and annotation processor to support annotations like @Getter, @Setter, @NoArgsConstructor, etc., used throughout the plugin.
- Maintained existing dependencies for RuneLite client compatibility.
* Update monster-monitor
Forgot to upload the NpcAnimationTracker.java
* Update monster-monitor
Bug fixes and improved UI/Panel visual - Refine UI and add MonsterMonitorBox for enhanced NPC tracking - Added more config options
- Improved the design and layout of MonsterMonitorPanel.
- Created MonsterMonitorBox to handle individual NPC tracking, including setting kill limits and notifications.
- Fixed bug where the last killed NPC was not being correctly displayed at the top of the NPC panel.
- Updated MonsterMonitorOverlay to maintain design consistency with the panel and improve user readability.
- Retained all existing functionality while enhancing the visual and interactive elements of the plugin.
- Added configuration options to MonsterMonitorConfig for default kill limits, chat notifications, custom notification messages, unknown death animation notifications, and sound alerts.
- Enhanced MonsterMonitorPlugin to listen for ConfigChanged events and apply configuration updates immediately.
- Ensured that sound alerts and chat notifications are toggled based on user preferences, providing immediate feedback without requiring plugin restart.
* Update monster-monitor
Fix layout issues in MonsterMonitorPanel and MonsterMonitorBox, Added config option functionality :
- Implemented dynamic resizing for NPCListPanel using GridBagLayout, ensuring proper layout adjustments as NPCs are added or removed.
- Removed redundant JScrollPane nesting, allowing the ScrollPane to fill the available space within PluginPanel and improving scrolling performance.
- Introduced a dynamic filler panel at the bottom of the NPCListPanel that adjusts its height based on the number of NPCs, ensuring proper vertical expansion and contraction.
- Added dropdown persistence in MonsterMonitorBox to maintain the expanded/collapsed state of NPC dropdowns during panel refresh.
- Ensured the title panel remains static at the top while enabling smooth scrolling for the NPC list in the ScrollPane.
- Configurations now control kill limit notifications, sound alerts, and chat notifications for NPC kills and unknown death animations, with logic to notify only once per unknown death animation.
* Update monster-monitor
fix: replace deprecated OverlayPriority usage with integer-based priority system
- Updated setPriority(OverlayPriority.HIGH) to setPriority(50) to adhere to the integer-based priority system.
* Update monster-monitor
Update verification-metadata.xml with updated dependency checksums
* Update monster-monitor
Update Gson version to 2.8.5 and update verification-metadata with new checksums
* Update monster-monitor
fix: Inject client's Gson instance instead of creating a new one
- Removed the direct instantiation of Gson in MonsterMonitorLogger.
- Injected the client's Gson instance using @Inject annotation.
* Update monster-monitor
Update Monster Monitor: Refactor to use DeathTracker, handle multi-phase NPCs, improve death logging logic
- Replaced NpcAnimationTracker with DeathTracker to log deaths based on interactions.
- Included final phase IDs for multi-phase bosses such as Verzik, Vorkath, Zulrah, and others.
- Removed animation-based logic and unknown death animation notifications.
- Added interaction validation to ensure only relevant NPC deaths are logged.
- Cleaned up code, removed unused methods, and optimized NPC tracking.
* Update monster-monitor
Improve NPC engagement tracking and proper EventBus unregistration
- Added `wasNpcEngaged` map to track whether an NPC has been engaged through hitsplats or damage, ensuring that only NPCs that have been properly interacted with are logged upon despawn.
- Updated `onInteractingChanged` method to reset engagement status when a new interaction with an NPC starts, ensuring accurate tracking.
- Updated `onHitsplatApplied` to mark NPCs as engaged when a hitsplat is applied, indicating active combat engagement.
- Refined `onNpcDespawned` to only log NPCs as dead if they were actively engaged in combat before despawning, avoiding false positives from mere clicks.
- Ensured cleanup of engagement status and related states after logging to maintain memory efficiency and avoid stale data.
- Added proper unregistration of the `EventBus` in the `unregister` method to ensure clean shutdown of the plugin, preventing potential memory leaks and ensuring a smooth disable process.
* Update monster-monitor
Fix: Inject EventBus into MonsterMonitorPlugin for proper event registration
- Added EventBus injection to MonsterMonitorPlugin to enable registration and unregistration of DeathTracker during plugin startUp and shutDown.
- Ensured proper lifecycle management of DeathTracker events to maintain consistency when the plugin is restarted.
* Update monster-monitor
fix: move scrollbar UI updates to Swing thread
Used SwingUtilities.invokeLater() for setting up the custom scrollbar UI to make sure it's done on the correct thread.
* Update monster-monitor
refactor: use logger.error() instead of printStackTrace()
- Swapped out all instances of e.printStackTrace() with logger.error() for better logging.
- This should make errors easier to track in the RuneLite logs and keep things cleaner.
