GD Item Assistant on Linux

Item Assistant is a Windows program. On Linux it runs under Wine, in the same Proton prefix as Grim Dawn.

Everything on this page gets installed into that prefix. Item Assistant loads a helper into the running game, and that only works when both are in the same prefix. Installed anywhere else, Item Assistant starts up fine but never finds your game.

What you need

Grim Dawn installed through Steam with Proton, and started at least once. Starting it once is what creates the prefix.
protontricks, from your distro's packages or as a Flatpak:
```
flatpak install com.github.Matoking.protontricks
```

Grim Dawn's Steam app ID is 219990. You need it for every command below.

Using the Flatpak? Replace protontricks-launch in every command with flatpak run --command=protontricks-launch com.github.Matoking.protontricks. If your games are not in the default Steam folder, give it access to yours:

flatpak override --user --filesystem=/path/to/your/steam/library com.github.Matoking.protontricks

Download all three installers below normally, on the Linux side. Then run each one with protontricks-launch, so it lands in the prefix.

Step 1: .NET Desktop Runtime

Get the Windows x64 Desktop Runtime from dotnet.microsoft.com. Not the SDK, and not the plain runtime.

protontricks-launch --appid 219990 windowsdesktop-runtime-10.0.x-win-x64.exe

Step 2: WebView2 runtime

This draws the item list. Get the Evergreen Standalone Installer (x64) from Microsoft.

protontricks-launch --appid 219990 MicrosoftEdgeWebView2Setup.exe

Installing WebView2 on the Linux side, or in another prefix, will not work. This one catches people out.

Step 3: Item Assistant

protontricks-launch --appid 219990 GDItemAssistant.exe

It normally installs to:

<steam library>/steamapps/compatdata/219990/pfx/drive_c/users/steamuser/AppData/Local/IAGD/

If it is not there, check .../pfx/drive_c/Program Files/IAGD/ instead.

To find your Steam library:

find ~ -type d -name 219990 -path '*compatdata*' 2>/dev/null

Starting it

protontricks-launch --appid 219990 ~/.steam/steam/steamapps/compatdata/219990/pfx/drive_c/users/steamuser/AppData/Local/IAGD/IAGrim.exe

Change the path if your Steam library is somewhere else. Save it as a script or a desktop shortcut, you will need it every time.

Then start Grim Dawn normally. Item Assistant finds the game on its own.

Item Assistant attaches to the game about 45 seconds after it starts. Attaching earlier can crash the game, so it waits. You will not miss any items.

Checking that it works

Run Item Assistant with --diagnose:

protontricks-launch --appid 219990 ~/.steam/steam/.../IAGD/IAGrim.exe --diagnose

This writes iagd-diagnostics.txt next to your settings file and opens it. It works while Item Assistant is already running, and also when it will not start properly.

These lines tell you whether the install is healthy:

Line	Should say
`Running under Wine`	yes
`Launched by Proton`	yes
`Game folder (Proton)`	a path ending in `steamapps\common\Grim Dawn`
`Runtime version` (WebView2)	a version number, not `(none)`
`ItemAssistantHook_x64.dll`	`present, version ...`
`Install #1`	your Grim Dawn folder, `database present`
`isRunningInWine`	`True`

The same report goes into the log every time Item Assistant starts, so it is already there if you send a log file.

If something goes wrong

Run --diagnose first. Most of these show up in the report.

Item Assistant does not start, or closes straight away

The .NET Desktop Runtime is probably missing from the prefix. Do step 1 again, and check you got the Desktop runtime for x64.

A message says the WebView2 runtime is missing

Do step 2 again with protontricks-launch. If you installed WebView2 some other way, it went somewhere Item Assistant cannot see.

The window opens but the item list is empty

WebView2 is installed but did not start. The error message gives you its cache folder. Delete that folder and start Item Assistant again.

No items are picked up

Check these lines in the report, in this order:

isRunningInWine should be True. If it says not set, start Item Assistant once and close it.
ItemAssistantHook_x64.dll should be present. If it says MISSING, reinstall.
Install #1 should show your Grim Dawn folder. If it says none, set the folder yourself on the Settings tab.
Injection markers should be 1 while the game is running. If it is 0, wait a full minute after starting the game and check again.
Aborted attaches going up is normal while the game is loading or while you are on the character screen. It is not an error.

A message says the install is corrupted

The game helper is older than Item Assistant expects, usually because an update could not overwrite it. Close Grim Dawn, reinstall Item Assistant, then start the game.

Good to know

Proton updates and "verify integrity of game files" can reset the prefix. That removes the .NET and WebView2 runtimes, so redo steps 1 and 2 if things stop working after a Steam update.
Only Steam with Proton has been tested. GOG and Lutris installs should work the same way, as long as Item Assistant ends up in the same prefix as the game.
Linux support is much newer than the Windows version. If something does not work, say so, and attach the --diagnose output.

Running Item Assistant on Linux