In the first post, update the download location and provide up-to-date version information. Both modify the first post in the OXP thread that you created, and post a new message in the same thread.Rename the directories based on the release date of your new version, create a new zip file, and upload it. ![]() Update your readme file with a new entry to the version history.Always update the version number, no matter how small the change is.Please read The All-in-One Guide to OXZ Packaging and Distribution. At the very least, provide enough information for creating a one-liner in the OXP List.įrom Oolite v1.80 you should use the new OXZ format, which is required to appear in the in-game oxz manager.Create a wiki page for your OXP if you can, or ask around the BB for help with setting one up.Screenshots in the BB post are much appreciated.When you decide your OXP is finished, it is recommended that you change to. The title of the thread should be the name of the OXP preceded by as long as the OXP is under development. When you start work on an OXP and wish to make this known start a new thread in the Expansion Packs forum of the Oolite Bulletin Board (BB). It is free up to 5GB and does not annoy your users with advertisements. Most OXP authors use box.com for distribution nowadays. Upload the zip file to an easily accessible online storage.Otherwise, OS X specific files that are not relevant for other platforms will be included and lead to confusion. If you are working on a Mac, please use either a compression tool like YemuZip, or the "compress" command from the context menu in Finder followed by a run through ZipCleaner.While there are other, more efficient compression tools (such as rar, 7z), zip is available out-of-the-box on all operating systems that are officially supported by Oolite.Create a zip file based on the "MyNewOXP_x.y.z_yyyy-mm-dd" directory and name it "MyNewOXP_x.y.z_yyyy-mm-dd.zip".Inside the MyNewOXP_x.y.z_yyyy-mm-dd.oxp directory add the Config, Models, etc.See the Licensing OXPs thread on the Oolite Bulleting Board for information about licensing.Several OXP authors put a copy of the readme and manuals in both the main folder and the OXP folder.oxp directories are presented as packages. oxp directory then Mac users will have a harder time finding them as. If you prefix the names of the readme and license files with MyNewOXP you are making it easier for users to keep all files that belong to OXPs in one place.Make sure this directory does end with the. Inside "MyNewOXP_x.y.z_yyyy-mm-dd", add the readme, the license, and additional files, and the actual OXP directory, named MyNewOXP_x.y.z_yyyy-mm-dd.oxp.Replace yyyy-mm-dd with your OXP's new release date (yyyy: year, mm: month, dd:day), e.g.1.0.0 for the initial release, or 1.0.1 for a small follow-up bug fix release. Replace x.y.z with the version number, e.g.Make sure this directory does not end with the. Create a directory named after your OXP, e.g.These recommendations will help with distributing in that format ![]() oxp folder inside a compressed file do not. The OXZ format has very specific rules, but OXPs distributed as a. "MyOXP_MetalTexture.png" not "MetalTexture.png") Prefixing the names with the OXP name is recommended (e.g. plist files as they may lead to conflicts with other OXPs. Avoid the use of generic names for textures, models, scripts, and keys in. ![]() They make it harder for people who use the command line.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |