Module:Downloadlinks/hashes/doc
Jump to navigation
Jump to search
[refresh]
This is the documentation page. It is transcluded into Module:Downloadlinks/hashes. See Template:Documentation for more information.Explanation[edit source]
['<version>'] = {
client = '<client_hash>',
server = '<server_hash>',
windows_server = '<windows_server_hash>',
json = '<json_hash>',
json_package = '<json_package_hash>'
},
In here, <version>
is a version of Minecraft, for example 1.13.1-pre2
. The hashes are as follows (order shouldn't matter, but it is best to keep a regular order; see notes when given):
<client_hash>
- SHA-1 hash for the client JAR, e.g.
7eaeaa37e0c7642d519c39de70a630119ad4929a
.
<server_hash>
- SHA-1 hash for the server JAR, e.g.
c2a4bcf3e244c46f13c39e31e7ef6030564fb6c2
.
<windows_server_hash>
- SHA-1 hash for the Windows server EXE. It seems there's no longer a separate Windows version since 16w04a (late-1.9 development) and therefore it is not included in the example.
<json>
- SHA-1 hash for the downloaded JSON file, e.g.
4f2100e24eb32ab94447de5808b96fdade6badd3
. Pretty much only used when in the template call|force_download=
is set to1
whenjson
is used as variant parameter value.
<json_package>
- SHA-1 hash for the in-browser JSON, e.g.
1594d6f7242d2065c2b61c242397f40677e5123c
. Used whenjson
variant parameter value is set without|force_download=
set to1
or whenjson_package
itself is used as value for the variant parameter field.
Example[edit source]
Using the values from above, the 1.13.1-pre2 hash table would look like this:
['1.13.1-pre2'] = {
client = '7eaeaa37e0c7642d519c39de70a630119ad4929a',
server = 'c2a4bcf3e244c46f13c39e31e7ef6030564fb6c2',
json = '4f2100e24eb32ab94447de5808b96fdade6badd3',
json_package = '1594d6f7242d2065c2b61c242397f40677e5123c'
},
Using these hashes, the main module will create links from them.