I've been seeing that lately with my Launcher. It happens when your game folder is in the root directory, like in /Applications. Move your game to a user folder (like ~/Applications) and it doesn't happen.
Moved game dir into /Users/you/Desktop, trying to launch setup-mymod.app, still the same issue. It appears that it's a new security model for Mojave.
.command files get around that, I guess simply by not havinjg a ".app" at the end of their names... but I'd still like to see more effort put into them. Like, why can't the .command script do something like:
- check if Weidu exists in the game folder
- if not, download it there
- check the name of itself (i.e. "_______.command")
- invoke Weidu with ________.tp2
Then every mod wouldn't need to supply the Weidu source in addition to the .command script. Players would only need the script and the mod folder.
A variant which doesn't require macOS WeiDU to be included, doesn't require 'setup-' and still keep "double-click install" for players
#!/bin/bash
cd "${0%/*}"
ScriptName="${0##*/}"
BaseName="${ScriptName%.*}"
ID="${BaseName/setup-/}"
if ! [ -f weidu ] ; then
# the direct link to macOS WeiDU executable
wget 'https://onedrive.live.com/download?cid=E5A3B6F0BF342ED6&resid=E5A3B6F0BF342ED6%21607968&authkey=%21AKnUrPdUG2hcAR8' -O weidu -q
chmod +x weidu
fi
# --no-exit-pause prevets 'double Enter' for macOS
./weidu ${ID}/${ID}.tp2 --no-exit-pause --log "${ID}.debug"
...and then puts the results into a list in a UI box. A .command script could do the same thing quite easily - the only hitch is that I personally don't know how to do it.
That's GUI level. The proper solution for this kind of stuff is a mod manager.
This is part of the nature of modern OSes. It's not as bad as Windows, where Weidu mods might not even work if the game is in /Program Files... but it's still annoying.
This problem is solved with new weidu version, it was simply a lack of care from weidu side of how to do 'windows app security' correctly.
I received feedback regarding this tool: the initial requirements and setup process of this tool are complicated and setup instructions are not good. I could spend a lot of time in order to create extensive instructions with video tutorial but in the end, I spent the time to create a much better solution, which is trivial to setup and use: Infinity Auto Packager
In order to avoid duplication of the functionality, the "package generation and upload" feature is now removed from this tool. The main purpose of this tool: the ability to create GitHub release from the commandline instead of the webpage is kept intact, with all other benefits.
The good news is that you can now combine these two tools
- if you want to publish new GitHub release from the commandline instead of the webpage, use this tool
- if you want automatically generate Infinity Engine mod packages and adds them to release when you publish it, use Infinity Auto Packager
If you want to combine these two tools, please update this tool to latest version.
Comments
This is exactly what my proposed solution do.
That's GUI level. The proper solution for this kind of stuff is a mod manager.
This problem is solved with new weidu version, it was simply a lack of care from weidu side of how to do 'windows app security' correctly.
In order to avoid duplication of the functionality, the "package generation and upload" feature is now removed from this tool. The main purpose of this tool: the ability to create GitHub release from the commandline instead of the webpage is kept intact, with all other benefits.
The good news is that you can now combine these two tools
- if you want to publish new GitHub release from the commandline instead of the webpage, use this tool
- if you want automatically generate Infinity Engine mod packages and adds them to release when you publish it, use Infinity Auto Packager
If you want to combine these two tools, please update this tool to latest version.