I see. Sorry for being a PITA.Knotty wrote:It is a proper oxp, I played it safe by taking an existing oxp, renaming it, removing what wasn't needed, putting in my plist, zipping it up and uploading.
I've tested it by downloading it and replacing the oxp in my addons folder
I'm not sure what's happening with Duggan, I've only used OoLite on the Mac so don't know how other OS handle the files.
It's fine with all OSs. However, as you know, on Mac OS X the OXP shows up as a package, which looks like a single file. Not every Mac user knows that they can open that package. Therefore they'll never see the readMe. Especially for Mac users it is better practice to not include the readMe inside the OXP. Instead, create a parent folder and put the OXP and its readMe in that one. Then give the instruction to place only the OXP in the AddOns folder, not its parent folder. (Download any of my OXPs as an example.)
For Windows and Linux users packages don't exist. For them the OXP is an ordinary folder which has to be placed inside AddOns.
Switeck's advice is also an important one. Please include a license statement in your OXP's readMe. Strictly speaking, if you don't do that, you're saying that nobody is allowed to download, install, or use the OXP. We're not very formal here, but giving a license that states what a user is allowed to do with your work is a good practice. There is a thread here in the Expansion Packs forum with helpful hints about licensing stuff.