Force Move assignment no longer functional after update. -v1.2.0.0
Force Move disables non-move actions, ie. you can’t accidentally click interactive objects or monsters while moving, are you confusing it with the Move keybind?
No, I mean it doesn’t do anything. Before it would still move my character without interfacing with the environment. Now it’s non-reactive when I press the assigned key.
That is not how force move ever worked. You can roll back to the v1.1.9.8 branch to compare.
Does the game offer a built-in means to do so? I’d rather not tamper with the game files if it means manually adjusting the data.
I’m confused about what force move is supposed to do in this game then; my experience with other arpg’s has force move work as I explained. Do you mean it’s a toggle in this game? I don’t really understand why it’s listed under the same subsection as Move without a modifier clarification (i.e. Force Move[Toggle])
I’m not going to say my memory is perfect, but the entire reason I know about force move in this title is because I discovered it in another arpg and was happy to find it worked similarly here. I checked back with that game and force move works how I thought it does.
Allow me to ask this as a means to dispel my confusion: If nothing exists on the field, is there a difference in function from Move and Force Move? Will the character move from point “A” to “B” in both functions?
When you hold Force Move, clicking to move with the mouse will ignore any other inputs (ie. normally hovering over a monster will move you to attack it).
The Move command may be what you’re looking for. It makes the character move to the cursor’s position and ignore other interactions.
great way to highlight the difference is when actually attacking with a skill capable of indirect attacks such as guns
because when you hold force move, the game ignores other inputs, it will mean you will attack exactly where your cursor is, if holding attack+forcemove,
^whis is highly noticeable when using ex guns or lazer beams or other attacks you dont’ want “snapping” to enemy hitbox
if you used actual move command, you’d stop attacking and start running, where in the above scenario it then becomes a “force attack here” if you will
The names are kinda confusing when you have experience in other games. I’d rename Move to Force Move and Force Move to… Free Aim 
or like “force action” or something, and rename “move to” to “move command”
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.