If you have trouble running VASSAL on MacOSX (11.7 and possibly later) - I.e., you can install by downloading the DMG from the site, but when you try to run it, then MacOSX complains that it won’t run the app because it was downloaded via Chrome/FireFox/… - do not despair - here’s how to get around it.
Open up a Terminal (Finder->Applications->Utilities->Terminal)
An inability to open/mount a disk image because it was downloaded by Chrome/Firefox is a new one to me–I’ve been using VASSAL successfully on MacOS since at least that OS version and likely much longer. Gatekeeper blocking the actual app from running because it’s not signed is a well-known issue, but first time hearing of this one! Note that the command line won’t be of any help to Apple Silicon users who might run into this–they’d have to modify the URL to get the right build for that architecture.
That’s pretty amusing–and good to know–that downloading with curl evades Gatekeeper. Still, if you look at the sweep of history and the kinds of installation difficulties and troubleshooting questions users tend to post, I don’t have much confidence that there will be more than a handful of users savvy enough to use this method. I might, though! You should add your method to that wiki page.
My point about the command line example given was not that the technique wouldn’t work for other builds as long as you modified the URL target (as you later expanded on)–just that the specific one in the OP would not work for Mac users who don’t have Intel architecture.