# HG changeset patch
# User Wuzzy
# Date 1531164747 -3600
# Node ID 6579d83e42c4c52a71384395b73ef862ab5738ba
# Parent  1a8cc20ce16cb2c38482aca22594dfbc03b23e34
HWPFormat: Versioning update

diff -r 1a8cc20ce16c -r 6579d83e42c4 HWPFormat.wiki
--- a/HWPFormat.wiki	Mon Jul 09 20:23:38 2018 +0100
+++ b/HWPFormat.wiki	Mon Jul 09 20:32:27 2018 +0100
@@ -112,7 +112,7 @@
 This section has a couple of conventions which are considered to be best practices when creating HWP files. They are not mandatory, just recommendations.
 
 === Versioning ===
-A naming convention is suggested to include a simple versioning into the file name. The syntax of this convention is this:
+For maps, themes, forts and any scripted content, we suggest to use a naming convention. The convention for those is to include a simple versioning into the file name. The syntax of this convention is this:
 
 <code>FileName_v<number>.hwp</code>
 
@@ -125,6 +125,8 @@
  * `MyAwesomePack_v3.hwp`
  * and so on …
 
+Don't worry, the appended version number is generally understood to be *not* part of the real name. It's just an useful convention to help resolving possible conflicts in online play.
+
 == Possible problems, conflicts and security risks ==
 Using HWP is not without problems.