Indeed it is!
You have YOUR_AD_HERE.oxp, taken from YOUR_AD_HERE v 4.1.4
You have to get the sets from Yaw_V4, so that YOUR_AD_HERE_set_A.oxp resides in the AddOns folder as another oxp.
Then you replace the shipdata.plist in YOUR_AD_HERE_set_A.oxp with the one from YOUR_AD_HERE_set_A414_upd.oxp (which you download with YOUR_AD_HERE v 4.1.4).
All as per the installations files and the read-me.
In my system, you cannot leave YOUR_AD_HERE_set_A.oxp and YOUR_AD_HERE_set_A414_upd.oxp in the AddOns folder, as my system does not upload oxps in alphabetical order, therefore, you get some updated sets, and some non-updated sets, leading to things like two beacons - one in the buoy and one in the constore. As can be read
here, this was a change made for 4.1.4. Also, if I leave them, there vast majority of the stores are Pi-42, but there are a few very occasional Star constores as well. So clearly just leaving the updates and the original sets side by side doesn't work on my system, as the shipdata.plist in the updates is supposed to override the one in the original set, and since they don't necessarily load in that order, that doesn't happen.
Therefore, according to the readme in the updates, I replaced the plists. Then I noticed that while I didn't have the thing with two beacons any more,
all the stores were Pi-42. Hence the looking around in the file.