1.4.2 Vortex Deployment Issue Still There

[Jirow13]

Keep getting the following on v.0.1.0-rc9

error: failed to install symlink err=EINVAL: invalid argument, symlink '<path>\AppData\Roaming\Vortex\mountandblade2bannerlord\mods\Community Patch - e1.4.2 and up-186-v0-1-0-rc9-1592274894\Modules\CommunityPatch\src\CommunityPatch\.idea\.idea.CommunityPatch\.idea\runConfigurations\GeneratePatchTargetHashes__No_Build_.xml' -> '<path>\steamapps\common\Mount & Blade II Bannerlord\Modules\CommunityPatch\src\CommunityPatch\.idea\.idea.CommunityPatch\.idea\runConfigurations\GeneratePatchTargetHashes__No_Build_.xml'

Troubleshooting Steps:

1. Disable all mods and try to install again. (Same issue)
2. Manually copy he problem file to destination. (Deploy still fails, mod not seen as active by Vortex)
3. Manual install of Vortex version. (Same issue).

When I can, I'll download an IDE and see if I can build it from GH, but thought I'd post this just in case it's an easy fix.

[Jirow13]

My guess is that the path is too long for Windows to handle.

This works: (253 Chars)
Get-Item 'C:\Users\xxxxxxxxxx\AppData\Roaming\Vortex\mountandblade2bannerlord\mods\Community Patch - e1.4.2 and up-186-v0-1-0-rc9-1592274894\Modules\CommunityPatch\src\CommunityPatch\.idea\.idea.CommunityPatch\.idea\runConfigurations\GeneratePatchTargetHashes.xml'

This fails: (264 Chars)
'C:\Users\xxxxxxxxxx\AppData\Roaming\Vortex\mountandblade2bannerlord\mods\Community Patch - e1.4.2 and up-186-v0-1-0-rc9-1592274894\Modules\CommunityPatch\src\CommunityPatch\.idea\.idea.CommunityPatch\.idea\runConfigurations\GeneratePatchTargetHashes__No_Build_.xml'

[AmericanGeezus]

Windows hard limit is 260, so that is a good suspect.

Just to see if it works, try prepending your failing case path with the verylongpath designator.
\\?\<your_long_path_Including_DriveColonBackSlash>

'\\?\C:\Users\xxxxxxxxxx\AppData\Roaming\Vortex\mountandblade2bannerlord\mods\Community Patch - e1.4.2 and up-186-v0-1-0-rc9-1592274894\Modules\CommunityPatch\src\CommunityPatch.idea.idea.CommunityPatch.idea\runConfigurations\GeneratePatchTargetHashes__No_Build_.xml'

It might be an easier fix if that works vs. finding a way to reduce path length.

[Jirow13]

Great idea. I can confirm that I can create that failing Symlink using the long-path designator using a PowerShell command.