@aljeyOne item at a time.
No, I don't know how to read the preference file actually.
OK. Here's how I do it. There may be other ways.
1. In Finder, old down the option key and open the Go menu. You will see a menu choice "Library." That choice only appears when the option key is down. Select it. This will open the Library folder as a window on your Mac.
2. In the Library folder you will find a Preferences Folder. Open that.
3. In the Preferences Folder you will find com.totem.Vghd.plist . Open that. This will probably cause your Mac to install the Apple XCode package. This is a free development library that includes a plist reader. It may take a few minutes to install XCode and you will probably have to give permission more than once. You may have to open com.totem.Vghd.plist a second time after XCode is installed.
4. Once Xcode is open you will see a window showing the contents of com.totem.Vghd.plist. There are lots of interesting items there. Scroll or use the Find command to find system.ModelsPath This is the path iStripper will use to find your models folders. Note that this is a UNIX path name using /, not a Mac path name using :. iStripper allows more than one, but I only use a single path and I don't know what a multi-path entry looks like. You can edit and save this, but see below. NOTE: Some of the key's shown have no effect on the Mac.
The article on nethack.ch referred to above does not seem to be about iStripper specifically, is it?
No, it's about the way the Mac OS manages preference file data. I just read that article. I've never seen it before and it explains some things I discovered on my own.
Originally, the preference file contained live data. If you change data in the preference file it had an immediate effect on the application using that data.
At some point, probably for performance reasons, Apple changed things. Applications now copy the preference data into a cache and work with what's in the cache not what's in the file itself. This means that changes to the preference file are ignored by the running application. However, there are AppleScript changes that will update both the data in the file and in the cache. I've used them, but sometimes the results are surprising and sometimes they have no effect.
I later discovered that the cache data is not flushed when an application quits. If the application is reopened and the cached data is still present the application may ignore the preference file.
The iStripper application will update its preference file when the application closes, but never before that.
So, I only revise the iStripper preference file when iStripper is
not running at all. That means QUIT iStripper as your first step. Closing the window is not enough. Once I have saved my changes to the iStripper preference file,
I reboot my Mac. I do this because, in the past, I discovered the cached data overrode my preference file changes. This may no longer be necessary, but I always reboot just to be safe.
@Wyldanimal and
@NebalI believe that all applications since OS 10.13, Mojave must be 64 bit. I found the following at
https://developer.apple.com/news/?id=12012017a64-bit Requirement for Mac Apps
December 1, 2017
As a reminder, new apps submitted to the Mac App Store must support 64-bit starting January 2018, and Mac app updates and existing apps must support 64-bit starting June 2018. If you distribute your apps outside the Mac App Store, we highly recommend distributing 64-bit binaries to make sure your users can continue to run your apps on future versions of macOS. The last macOS release to support 32-bit apps without compromise is macOS High Sierra.
I hope this helps. I'm happy to answer questions or provide more details if needed.