Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
help:how_to_package_and_release_a_file [2020/02/20 17:40] – Early autumn - Single Player map human[rus] | help:how_to_package_and_release_a_file [2023/02/14 16:47] (current) – [Hosting] Spirit | ||
---|---|---|---|
Line 1: | Line 1: | ||
===== How to package and release a file ===== | ===== How to package and release a file ===== | ||
+ | |||
+ | dumptruck_ds made a [[https:// | ||
==== Naming ==== | ==== Naming ==== | ||
- | Early autumn | ||
- | === Map === | ||
- | | ||
- | http:// | + | === Maps === |
+ | Pick a good filename for your .bsp file. People commonly use their nicknames and a counter or try to find a good short word describing the map. Adding a " | ||
+ | |||
+ | Alternatively just name it after the map's actual name. | ||
+ | |||
+ | Don't forget to set the title field in the .bsp file to something useful. | ||
+ | |||
+ | === Mods === | ||
+ | For mods the standard seems to be a more descriptive filename. Usually it is a short form of the mod's title. If it is a mod just supporting one map (so it's more of a map than a mod) the map naming suggestions above apply though. | ||
+ | |||
+ | === Examples of good naming schemes === | ||
+ | * efdatsp1.bsp - The Place of Dismay by efdat, full nickname since it is short & sp & number | ||
+ | * chessp1.bsp - Shrine of Skank by cheshire, abbreviated nickname & sp & number | ||
+ | * ikspq1.bsp - Before Nightfall by Iikka " | ||
+ | * ac.bsp - Adamantine Cruelty by Vondur, acronym of the level title | ||
+ | * ant.bsp - Antediluvian by metlslime, abbreviated title | ||
+ | * cogs.bsp - Cogs Of Conflict by spd, a single prominent word from the title | ||
+ | |||
+ | === General considerations === | ||
+ | Be aware that filenames longer than 8 characters will be a pain to use on DOS. So if you are a nice person, find a short one. It will also be nicer to type (if the user's engine does not support tab completion). | ||
+ | |||
+ | Avoid any characters that are not a-z or 0-9. A single dash - might be ok. Quake engines do not handle international keyboard layouts well. Do not use uppercase characters for any files. | ||
+ | |||
+ | Before you settle, search the web for the name and make sure it is not already used. | ||
- | {{: | ||
==== Text file ==== | ==== Text file ==== | ||
- | You must add a text file to your release, documenting at least the title of the work and your (nick)name. You should also include a release name, the intended purpose, contact details, release date and the like. Without this, your file(s) might be lost in "who on earth made this and when and why?!" limbo. | + | You should |
Best practice would be using the good old base.txt template: [[/ | Best practice would be using the good old base.txt template: [[/ | ||
Line 30: | Line 51: | ||
==== Hosting ==== | ==== Hosting ==== | ||
- | If it is a finished work, you can contact | + | Upload the final archive to https:// |
+ | |||
+ | Do not use services that do not support direct download links. And please do not use volatile hosts like Dropbox, Google Drive or any ad-ridden | ||
- | If that is not an option, if it is a work-in-progress, | + | ==== Quaddicted' |
+ | The database of singleplayer Quake maps (and some mods) at https://www.quaddicted.com/reviews/ was designed on a per-file level. Each entry or page available | ||
- | For permanent hosting | + | This means that e.g. three different versions of a thing become three separate entries in the database. This allows external tools like the [[tools: |
- | Do not use services that do not support direct download links. And please do not use volatile hosts like Dropbox, Google Drive or any ad-financed free hosting providers. | + | [[/ |