Tree of Savior Forum

Mouse Mode: Sub Weapon Not Working

Update:

Ohhhh, I found it out. I had several mappings to the same key (some other hotkey). Cleared the doubled mapping and it is working. Thank you nizdir for making me look closer and finding this out.

So I guess the real issue here comes down that if you map a key that has been mapped, it should delete the old mapping I Suppose.

Original Post:
Heyo,

I think mouse mode works almost fine apart from the more known issues when it comes to targeting stuff. However, there are some essential combat features that are outright unusable/not accessible if you are using mouse mode.

One of these features that you can’t use in mouse mode is using sub weapon. It just will not work on mouse mode.

Bug Description :
In Keyboard mode you press C to sub-weapon. In Mouse mode, this feature is not workingt at all. It would be nice having it work.

Steps to reproduce the issue :

  1. Switch to mouse mode
  2. Try using sub weapon attack
  3. will not work under any circumstances

Why does it need to be fixed?
The usecase for melee characters should be clear without further explanation. However as an example to use mouse mode on Cryomancer, which as a ranged class is definitely more comfy to play with in mouse mode:

Striking ice walls with a staff only works using the sub weapon feature. Which means any mouse mode user can not use this combo which is essential for any cryo/linker wanting to play in mouse mode.

Please make it so that pressing C (or whatever button you map it to) just triggers the sub weapon attack. I understand that mapping it to mouse2 or anything would not be possible due to UI mechanics, But when pressing a keyboard button it should work like any skill and just trigger the attack in the direction you are looking at, just like it does on keyboard mode.

Bonus Fix/Feature
It probalby also comes down why in mouse mode you can not use a blind auto-attack (meaning auto attacking without having a target) like you’d be able to in keyboard mode. So why not use the shift-key functionality that locks you on place to trigger this behavior in mouse mode. Meaning shift + mouse 1 should just shoot autoshot like pressing attack in keyboard mode.

works perfectly fine for me. Both “C” and its remapped version on Mouse5. Check your keybindings in game options or Hotkey_mousemode_user.xml in game’s release folder.

If you are using Rods - they dont have alternative attack, only 2-h staves do. If you want to strike ice walls while using rod - get yourself a dagger (any).

[quote=“martin2, post:1, topic:212936”]
It probalby also comes down why in mouse mode you can not use a blind auto-attack (meaning auto attacking without having a target) like you’d be able to in keyboard mode. So why not use the shift-key functionality that locks you on place to trigger this behavior in mouse mode. Meaning shift + mouse 1 should just shoot autoshot like pressing attack in keyboard mode.
[/quote]You can use “Z” for “blind auto attack” or you could rebind it elsewhere.

works perfectly fine for me. Both "C" and its remapped version on Mouse5. Check your keybindings in game options or Hotkey_mousemode_user.xml in game's release folder.

When I use a staff and press “c” (or “x”, mapped it to that), in mouse mode, it does absolutely nothing. Can you explain what you do to have it working?

If you are using Rods - they dont have alternative attack, only 2-h staves do

Yeah, I know. This is why I wrote “striking ice walls with a staff”. I am aware of that.

i just press “C” or “Mouse5”

check if you have
<HotKey ID="LHand" Name="왼손/UI 선택 모드 : 휠다운" DownScp="None" UpScp="None" Key="C" UseShift="NO" UseAlt="NO" UseCtrl="NO" OnEdit="NO" Category="Battle"/>

in your Hotey_mousemode_user.xml

Note: you have to close client before making any changes in .xml files or else your changes may get overwritten by game.

Ohhhh, I found it out. I had several mappings to the same key (some other hotkey). Cleared the doubled mapping and it is working. Thank you nizdir for making me look closer and finding this out.

So I guess the real issue here comes down that if you map a key that has been mapped, it should delete the old mapping I Suppose.