equal
deleted
inserted
replaced
110 |
110 |
111 == Best practices == |
111 == Best practices == |
112 This section has a couple of conventions which are considered to be best practices when creating HWP files. They are not mandatory, just recommendations. |
112 This section has a couple of conventions which are considered to be best practices when creating HWP files. They are not mandatory, just recommendations. |
113 |
113 |
114 === Versioning === |
114 === Versioning === |
115 A naming convention is suggested to include a simple versioning into the file name. The syntax of this convention is this: |
115 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: |
116 |
116 |
117 <code>FileName_v<number>.hwp</code> |
117 <code>FileName_v<number>.hwp</code> |
118 |
118 |
119 Where `<number>` is replaced with an integer for the version number, starting by 1. For each subsequent version, this number would be increased. |
119 Where `<number>` is replaced with an integer for the version number, starting by 1. For each subsequent version, this number would be increased. |
120 |
120 |
122 |
122 |
123 * `MyAwesomePack_v1.hwp` |
123 * `MyAwesomePack_v1.hwp` |
124 * `MyAwesomePack_v2.hwp` |
124 * `MyAwesomePack_v2.hwp` |
125 * `MyAwesomePack_v3.hwp` |
125 * `MyAwesomePack_v3.hwp` |
126 * and so on … |
126 * and so on … |
|
127 |
|
128 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. |
127 |
129 |
128 == Possible problems, conflicts and security risks == |
130 == Possible problems, conflicts and security risks == |
129 Using HWP is not without problems. |
131 Using HWP is not without problems. |
130 |
132 |
131 === Security risks === |
133 === Security risks === |