📋 Summary

When importing Windows games into LaunchBox by dragging and dropping desktop shortcuts (.lnk files), LaunchBox currently stores the shortcut file path itself instead of the actual executable the shortcut points to. This request proposes adding an option to automatically resolve .lnk files to their target executable paths during import.

❗ Problem

Dragging .lnk files into LaunchBox is a convenient way to add manually installed Windows games. However:

• LaunchBox saves the path to the .lnk file (e.g. C:\Users\...\Desktop\Game.lnk) instead of the resolved target (e.g. C:\Games\Game\Game.exe).

• If the shortcut is moved, renamed, or deleted, the LaunchBox entry breaks.

• This creates fragility compared to directly tracking the executable.

💡 Proposal

Add an optional checkbox during import (or in import settings):

“Resolve shortcut target (.lnk) to executable path”

When enabled:

• LaunchBox reads the .lnk file and stores the resolved target executable path.

• The working directory and arguments from the shortcut could also be preserved where applicable.

When disabled:

• LaunchBox retains the current behavior, using the .lnk file path directly.

🧩 Use Cases

• Users adding DRM-free or manually installed Windows games via desktop shortcuts.

• Users cleaning up their desktop without breaking LaunchBox entries.

• Advanced users who do want to keep .lnk files intact (e.g. for admin flags, compatibility modes, or custom arguments) can simply leave the option unchecked.

📦 Benefits

• More robust Windows game entries that don’t break when shortcuts change.

• Maintains flexibility for advanced shortcut-based setups.

• Improves the drag-and-drop Windows game import experience without changing default behavior.