HapticScape v2.3.0
HapticScape 2.3.0
Version 2.3.0 expands post-session settings locks, improves Remote Play usability, and restructures several internal systems for easier maintenance.
Granular settings locks
Controllers can now select individual settings or complete settings blocks for post-session locking.
Available lock targets include:
- Haptic and click toggles for each skill.
- The complete Feedback settings block.
- The XP settings block for each individual skill.
- The complete Generic Alerts block.
- A separate settings block for each specific alert type.
- The complete Click Settings block.
- Individual phrase-click rules.
Lock targets are selected from the Subject workspace during an active Remote Play session.
- Shift-click a checkbox to select that individual setting.
- Shift-click a block padlock to select the complete block.
- Shift-click a phrase-click entry to select that individual rule.
- Shift-click a selected target again to remove it.
Open padlocks indicate selectable blocks. Closed orange padlocks indicate targets selected for locking.
Parent and child targets cannot overlap in the same proposal. Selecting a complete block replaces any individually selected settings inside that block.
Phrase-click rule locking
Phrase-click rules now have stable internal identifiers, allowing individual rules to remain lockable when edited or reordered.
Remote Play interface improvements
- Moved the Remote Play button to the top of the main HapticScape panel.
- Changed the default remote buzz duration from 50 ms to 500 ms.
- Remote buzz intensity now defaults to the participant’s configured maximum.
- Prevented Emergency Off state updates from resetting the visible panel position.
- Improved six-tab sidebar sizing to prevent lower controls from being clipped.
- Added fixed-size lock indicators throughout the settings interface.
- Added hover instructions for block and individual lock controls.
Internal refactoring
- Split remote-session responsibilities into more focused lifecycle, settings, permissions, lock, action, and live-control components.
- Reduced direct protocol handling inside the main remote-session coordinator.
- Preserved existing encrypted transport and participant-side safety enforcement.
- Improved separation between RuneLite event handling, feedback coordination, and plugin lifecycle behavior.