User Tools

Site Tools


arma:howtorelease

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
arma:howtorelease [2009-04-29 15:33]
snakeman major upgrade to howtorelease page.
arma:howtorelease [2017-10-13 19:59] (current)
snakeman http to https switch.
Line 55: Line 55:
   * Addons needed, as stated above the addons you want to use but should not add to the release package.   * Addons needed, as stated above the addons you want to use but should not add to the release package.
   * Installation instructions. This should include clear and specific install instructions.   * Installation instructions. This should include clear and specific install instructions.
 +  * Credits. Credit all the people who have helped you or who's work you have used (with permissions),​ it goes long way when you show your gratitude like this.
   * 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.
  
Line 82: Line 83:
  
 When you name it like this, anyone seeing that file months from now in some directory, immediately knows that ah-ha, its PMC's Iraqi Terrain 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 Iraqi Terrain the first version.
 +
 +
 +====== Signature Key File ======
 +
 +You should be using the BIS signature key files for your addon, BinPBO does this automatically for you if you tick the "​Create Signature"​ part. Signature is the <​addon_name>​.<​key_name>​.bisign file.
 +
 +For the release you must add your public key, which you used to create all the individual pbo addon keys. Place this public key into some directory like "​Keys/"​ for example. Simple as that.
 +
 +Its important not to forget to add this file, as any multiplayer servers require the public key so your addons are properly signed for the session.
  
  
Line 123: Line 133:
  
 Its very unlikely that you get any trouble with permissions from anyone else than the author, sometimes some lamers in forum stir trouble by accusing you of releasing addons without permissions,​ but usually its enough if you say that you have permission or perhaps the author himself corrects these false claims. There is no chance of the author himself starting to cause trouble of permissions... since he already granted them. But in any case, screenshot "​proof"​ of the granting of permissions is rock solid way to keep your back covered in any situation that might come up later. Its very unlikely that you get any trouble with permissions from anyone else than the author, sometimes some lamers in forum stir trouble by accusing you of releasing addons without permissions,​ but usually its enough if you say that you have permission or perhaps the author himself corrects these false claims. There is no chance of the author himself starting to cause trouble of permissions... since he already granted them. But in any case, screenshot "​proof"​ of the granting of permissions is rock solid way to keep your back covered in any situation that might come up later.
 +
 +
 +====== Publicity ======
 +
 +Publicity is nice to have and even though a real addon maker mostly makes addon for themselves, surely its very gratifying to see users out there enjoying your work. Over hyping your work was mentioned in the [[arma:​howto_be_mod_maker#​public_relations|how to be a mod maker]] article, so just don't do it.
 +
 +However when you are in final stages of releasing your addon, basically you are just wrapping it up and unless you suddenly die the addon gets released... its perfectly fine to post some teaser screenshots or video clips about the mod. Just don't get caught in the hyping frenzy, but keep it cool.
 +
 +Its perfectly fine to let users in the community know what you're working... just don't lie, don't make empty promises. Its a tricky business to know what you can say and what to keep to yourself until you are packing the mod to a release packet.
 +
 +Community has been let down too many times already, how about you **not** doing it next?
  
  
Line 128: Line 149:
  
 This article has been written with experience of editing since 2000 and after witnessing / inspecting hundreds of lame addons and releases. This article has been written with experience of editing since 2000 and after witnessing / inspecting hundreds of lame addons and releases.
- 
arma/howtorelease.1241019198.txt.gz ยท Last modified: 2009-04-29 15:33 by snakeman