It just doesnt work. Period. Shift is working as you can see im TYPING with CAPS here, see? But in game, the SHIFT key is not holding position to attack. I am forced to move. I have tried checking for updates, and verified that the files arent busted with the GoG launcher thing. Whats the deal?

I have the same problem since the newest update auto-installed. I think update causes the problem.
If someone has a solution, that would be great.

Yeah I wish I turned off Auto Updates.

Same here - shift key does not work after update.

Whats that? Where is a link for info/download? Do I need to "google it"?

Well this sucks, I guess the MPQ file that I transfer is botched too. Because shift doesnt work in DevilutionX. In fact, I cant even keybind it. I tried setting it to a different key, and even that didnt work. With left ctrl key.

EDIT: Uninstalled everything, even save files, Wasn't that far into the game. Unchecked the automatic update. Now DevilutionX seems to be working fine with the new MPQ file I have copied from a fresh install. Maybe they will have a fix in the future, but for now, this is great.

I can definitely attest to this being from today's patch. Shift-LMB (attack in place) worked fine yesterday and today it's not recognizing the combo. I never realized how much I relied on it until it broke. It's pretty rough trying to target moving creatures and having my rogue dart around like a lunatic.

Let's hope this issue gets some attention and a fix is on the horizon.

I found a way to revert to the previous installation from GOG Galaxy.

1. Go to the GOG Galaxy installation page for "Diablo + Hellfire"
2. From the options at the top of the application, select the Additional Options >> Manage Installation >> Configure...
3. In the dialog that appears, uncheck "Automatically update to newest version"
4. Select the radio button below the checkbox for the version you would like to install instead.

I chose "Version 1.09 Hellfire v2" and it downloaded from the GOG server and installed over my existing installation. It preserved my save games as well. I booted the game up and the Shift-LMB function worked as intended.

See attached images for reference.

In case anyone else needs it. It's a source port that fixes a bunch of issues with the game and adds optional QoL, like wide screen, 60fps, hold to attack and much more: https://github.com/diasurgical/devilutionX/releases/latest
(scroll down and pick 64bit Windows from the list of downloads) Unlikely the MPQ doesn't hold any logic, just sounds and graphics.

Thank you for sharing this solution. Works perfect.

GOG DX Wrapper newest builds (well for some years) come with Input wrapper along with graphics wrapper component. But seems Diablo didnt get such version of Wrapper, remain on sort of old builds where only ddraw-d3d wrapped. Seems not he case. MPQ and even open-source remade affecting by MPQ just a strangest thing, have no explanation. Save files affected?

But seems by your reports reverting to previous GOG-Galaxy build on the same save file still did fix the issue.
GOGDB no more provide per-file CRCs as it did before. Wonder which file affect this.

MPQs still can be a reason. Patch mpq maybe. Some of them include or can include after update the default input schema file. As i remember. There is some cfg files there. Or i misrember it with Warcraft 2. Can explain reverting in galaxy but can explain DevilutionX? And repeating the installation process after erasing but for same v3 build lead to another result than first install process. Seems really random.
IM personally very skeptical. Are you all here sure it is not Discord app or something take Shift key randomly and revert didnt actually fix the issue?

(input component of GOGs DX are dixi.dll - not present for galaxy build)

Steam is buggy mess for years. Steam Input is worst of its bugs because this build-in wraper actually not relate on Overlay injecting in the games after game launch. Instead Steam Input start tonwork immediately after Stea launch and overtake controls detecting inpu devices re-/plugged. Whtever device and time, in PC "idle" too. And bugs can lead to partially disabling Keyboard (only arrow keys keep working). Even when gamepad unplugged back.
So make sure Steam client are entirely close ("killed" process) and nonelse input injectors take place. Unplug input devices too. Just for a moment, for diagnostic. To exclude possible randomness.

There is no such thing as a input schema file in Diablo, no cfg files either. The only thing in the patch mpq are updated battle net graphics. Human error can sometimes explain why things don't work the first time.

The same here, it’s really not nice to play with a broken shift key…

Same problem..
Hey GOG's, we really need a reverse patch...