Forgotten Tales

So many players are complaining about the device input - many like the joystick and many like the tap to move. Some of us like both at the same time. However, players that are dedicated to the joystick HATE the tap to move feature also being on. Especially in clan maps, they may tap to target, but it also causes the player to move, which usually means they die because it makes the player walk into a hostile area.

QUESTION: can tap to move be an option to turn on/off just as the joystick is?

You can toggle the tap to move as well currently (discovered recently since I've been back) however the problem is that you can still autowalk with tap to move off.

Even with tap to move "off" when you "tap" to access a building that's unfinished, you will "walk" to go start completing the building.

I've not discovered the exact source yet but sometimes at spawn I'll get stuck trying to "autowalk" somewhere. I usually just relog to clear it.


Edit: when you are set to "autowalk" it does not matter where it's at or how long you wait, your character HAS to "touch" whatever is making you autowalk before you can walk normally again.

Only way to stop that is to relog atm, or touch whatever you're walking at.

Both autowalk (intentional) and STOP (because of this bug) buttons added as ideas in my GUI post

viewtopic.php?f=8&t=14729

Cashew wrote: Edit: when you are set to "autowalk" it does not matter where it's at or how long you wait, your character HAS to "touch" whatever is making you autowalk before you can walk normally again.

Only way to stop that is to relog atm, or touch whatever you're walking at.

I have found that tapping a different building (allied, incomplete, or a usable gate) will redirect your autowalk. It doesn't stop it, but it can prevent a tower getting you in a hostile situation.