Chronicon did WASD first, and I believe they used the simple movement scheme. Where you stop if you attack. It works totally fine.
I think click to move should always be the main control scheme. The game should be balanced around it. I wouldn’t mind the basic WASD as an option. I don’t want a situation where WASD is better than click to move.
I was going to say “don’t bother”, but perhaps it’s not too long to implement if you listen to the keyboard and send a fake “hold left click” away from the character at 0° / 45° / 90° / … when W / WD / D / … are pressed. That being said, I would not advertise it.
Get over WASD and think about it for GD II. PoE II or V Rising play great on WASD simply because the games were designed for such control from the beginning. The important thing is that you added dodging and that’s enough. It’s a waste of time…
I think it would be best if they didn’t do it, many people will start complaining that it’s not the same as POE2 and it will end up causing more problems. It’s better to focus more on finishing the expansion.
That’s exactly why I didn’t reply myself.
… wait, I did now.
Sorry…
… may be team implement non-englisg Vinque font sets instead?
I don’t want that for this Game, thank you…
Victor Vran came out 4 days before Chronicon 
VV nailed the WASD movement scheme for me personally. No run&gun though, attacks are stationary (except a very short dash forward when melee attacking).
As for WASD in GD, I personally wouldn’t use it. Even though I enjoyed it in VV I don’t think it’s a very good fit for GD. I think dev time would be better spent somewhere else but if it isn’t that big of a deal to implement, go for it.
I know. But that’s not what I was talking about, quite the opposite. People with carpal tunnel or tendinitis have both hands, but would actually benefit from not having to concentrate most commands to the mouse hand (movement + aim and attack).
How hard would it be to implement this change? Would it hinder the launch of the third expansion? I don’t know much about programming, but if you could make it work for joystick players, would it be that harder to adapt it to keyboard and mouse?
Grim Dawn is fine like it is, that’s why many players still play this game and come back to it, due to it’s basics. Sorry, WASD is for race games and FPS lol
I don’t understand why at this point you’d want to spend time on this. You’re not going to compete with games that are designed with this kind of movement in mind from the beginning. It’s going to take a lot of time and you’re going to have to fight the old engine to do it. Doesn’t sound like a business decision I’d make, but then again I’m not in game dev.
Agree! they should scrap this idea…
The game, as it is now, is finely balanced in my opinion and the amount of time you invested (and still invest) to get there is extensive. So I think you should stick to the classic mouse-movement and postpone the controller-based WASD movement until GD2. All you get, if you implement it now, is a small number of finally satisfied players and a lot of rebalancing work. The majority of the players love it the way it is.
Never heard of anyone playing racing games with WASD. Maybe left-handed players do, idk. But you usually use the arrow keys for steering, and some keys on the left side of the keyboard to shift gears and look to the left, right and rear.
For right-handers, WASD only makes sense for games where you also use the mouse. So FPS games and yes, ARPGs.
Real pros use AZ and <> 
As always, people are misinterpreting, thinking crate would implement this as default and not a feature for people that want/need it.
I used TAB xd
The thing is that there are very few people who need WASD, and with an expansion in development, that would only delay its release even further.
Actually, real pros laugh at players who use a keyboard in racing games 
Analog controllers are much better for precise steering, accelerating and braking, even for shifting gears with manual clutch. But we’re getting off-topic here I guess…
I tend to agree, maybe it would be better to think about it after FoA is out… unless the programmer has an easy way to implement it. I mean if DPyes has already done it…