falcon4:howtorelease
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| falcon4:howtorelease [2009/05/14 18:00] – added mostly EXE installer tips. snakeman | falcon4:howtorelease [2024/07/31 11:12] (current) – links added. snakeman | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Falcon 4: How to Release ====== | + | ====== Falcon 4 How to Release ====== |
| - | **How to release your addon / theater** by Snake Man, PMC. | + | [[https:// |
| + | |||
| + | **Falcon 4 How to release your addon / theater** by Snake Man, PMC. | ||
| This general overview of releasing your productions will give you the final edge on making things right on a released product. | This general overview of releasing your productions will give you the final edge on making things right on a released product. | ||
| Line 19: | Line 21: | ||
| It is very very important that you include decent readme.txt into your addon release. This text file should be written with notepad or similar text editor that any kind of editor can open and read. | It is very very important that you include decent readme.txt into your addon release. This text file should be written with notepad or similar text editor that any kind of editor can open and read. | ||
| - | Basic readme should clearly state these following things; | + | Basic readme should clearly state these following things; |
| * Common release name | * Common release name | ||
| Line 25: | Line 27: | ||
| * Contact information listed at the bottom of the readme, authors name and the web site where to contact him if not direct email. Maybe you don't get much feedback or questions, but it would be decent to have contact information and if you have web site, its link there. Always nicer to know that the author of an addon is reachable by some means, if not else than just to check new versions or fixes. | * Contact information listed at the bottom of the readme, authors name and the web site where to contact him if not direct email. Maybe you don't get much feedback or questions, but it would be decent to have contact information and if you have web site, its link there. Always nicer to know that the author of an addon is reachable by some means, if not else than just to check new versions or fixes. | ||
| - | With that stuff you should have covered all the basic information what possible addon looking users are interested to know. Add the readme inside the rar packet but also if possible make it available on forum post or a web page. | + | With that stuff you should have covered all the basic information what possible addon looking users are interested to know. Add the readme inside the 7-zip (.7z) packet but also if possible make it available on forum post or a web page. |
| You know a good release is half of the addon quality and word spreads quickly over the internet if certain release has been goofed up. Make the effort to give your addon a good quality all around, not just the addon itself. It's worth it on the long run. | You know a good release is half of the addon quality and word spreads quickly over the internet if certain release has been goofed up. Make the effort to give your addon a good quality all around, not just the addon itself. It's worth it on the long run. | ||
| Line 34: | Line 36: | ||
| First of all, **do not never ever use spaces in file names**. | First of all, **do not never ever use spaces in file names**. | ||
| - | Please give the release a file name which itself describes the released product. Do not release " | + | Please give the release a file name which itself describes the released product. Do not release " |
| - | < | + | < |
| - | PMC_Taiwan_Theater_v0.1.rar | + | PMC_Taiwan_Theater_v0.1.7z |
| When you name it like this, anyone seeing that file months from now in some directory, immediately knows that ah-ha, its PMC's Taiwan Theater the first version. | When you name it like this, anyone seeing that file months from now in some directory, immediately knows that ah-ha, its PMC's Taiwan Theater the first version. | ||
| Line 48: | Line 50: | ||
| - | ====== RAR, ZIP or EXE ====== | + | ====== RAR, ZIP, EXE or 7-Zip ====== |
| - | When your addon is ready for release, package it up with a [[http://www.rarlabs.com/|RAR]], do not use zip anymore as its so outdated. | + | When your addon is ready for release, package it up with a [[https://www.7-zip.org/|7-Zip]], do not use PkZip (zip) or RAR anymore as those programs are so outdated. |
| - | If you're releasing a theater, its mostly done with [[falcon4: | + | If you're releasing a theater, its mostly done with [[falcon4: |
| Why EXE installer for Falcon 4 theaters but not OFP/ArmA series? Well they are like completely different things, while the OFP/ArmA installing is just putting X number of pbo files in a dir, in F4 we have to do million things with batch files for example like running terrain rebuilder, recreate tiles, modify .lst file, you name it... try to do that without EXE installer and you are a true wizard :) | Why EXE installer for Falcon 4 theaters but not OFP/ArmA series? Well they are like completely different things, while the OFP/ArmA installing is just putting X number of pbo files in a dir, in F4 we have to do million things with batch files for example like running terrain rebuilder, recreate tiles, modify .lst file, you name it... try to do that without EXE installer and you are a true wizard :) | ||
| Line 72: | Line 74: | ||
| It is very embarrassing to submit a news and forum posts and then few hours/days later discover that users start to report something very obvious bugs which should have been discovered. Trust beta testing, it helps. | It is very embarrassing to submit a news and forum posts and then few hours/days later discover that users start to report something very obvious bugs which should have been discovered. Trust beta testing, it helps. | ||
| + | |||
falcon4/howtorelease.1242324005.txt.gz · Last modified: 2009/05/14 18:00 (external edit)