I still didn't receive any notification about your reply. Any comment on that? Should I open a new bug report? Is it related to the same bug when I created my account that I posted in discord (like 1+ month(s) ago) and I think it was eventually shown the notification/email system was having issues?
I'm still running 'SkylordsRebornUpdater.exe' like I have from the very beginning (noted in my OP).
As you can see from my "ls" output in my reply above, all 5 files are extracted (including the new (or renamed) Patcher.exe) into the BF folder.
I will say, your comment about a "*separate folder" led me to try something else...
From a different command line path, I had been running SkylordsRebornUpdater by explicitly typing out the BF wine path (~/.wine.../BattleForge/...).
Just now, I went INTO the BF folder and ran 'wine SkylordsRebornUpdater.exe" and it didn't come up with that prompt... HOWEVER, it still seems to be hung up at the loading window ("Skylords Reborn - Patcher") which doesn't even render, but takes on the remnants of windows that are moved across it. I'm thinking some call is being made to an exe from an exe expecting it to be in the caller path. Change that so you are calling that other exe using the expanded path of the original exe.
OK, so it seems it's not even fully hung. After waiting several minutes, more wine info flew by, then another "hang" for several more minutes and tons more wine info. I don't know if you want that debug output (if you aren't even looking at the debug info I already posted), but it's not something you want me including in a Quote markup, but maybe an attachment.
There is no cpu% being used right now for BF and it's only taking 134M of RAM.
OK, multiple attempts at various things later, I get a prompt to "Detect Settings" which I do, though I got a wine crash before that prompt (showing BF still was running? super odd), and another wine crash window after.
Whoof!... Trying to re-run the command by varying parameters and even repeating previous commands are not resulting in the the further progression as before. Yeesh...
The latest output IS different:
Note the network messages. But really, if the rendering part isn't being addressed, then nothing else is going to matter. Has any effort been put into dealing with the rendering issue?