About: Version Check   Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : dbkwik.org associated with source dataset(s)

This file is used to verify that clients are the same version they claim to be and to tag certain versions for autoupgrades (see autoupdate.conf). Every combination of archtag/clienttag/version/equation/mpqfile needs to be listed seperately. Each combination has a unique checksum. Note: if you use multiple equations/mpqfiles be sure to put entries with corresponding checksum for each archtag/clienttag Do not include "/" in any of the file names.

AttributesValues
rdfs:label
  • Version Check
rdfs:comment
  • This file is used to verify that clients are the same version they claim to be and to tag certain versions for autoupgrades (see autoupdate.conf). Every combination of archtag/clienttag/version/equation/mpqfile needs to be listed seperately. Each combination has a unique checksum. Note: if you use multiple equations/mpqfiles be sure to put entries with corresponding checksum for each archtag/clienttag Do not include "/" in any of the file names.
dcterms:subject
dbkwik:pvpgn/prope...iPageUsesTemplate
abstract
  • This file is used to verify that clients are the same version they claim to be and to tag certain versions for autoupgrades (see autoupdate.conf). Every combination of archtag/clienttag/version/equation/mpqfile needs to be listed seperately. Each combination has a unique checksum. If the exeinfo field is "NULL" then the string comparison will be disabled for that entry. If the checksum field is 0 then the checksum verification is disabled for that entry. If the versionid is 0 then the verification of versionid is disabled for that entry, the versiontag is optional. It is used to identify a particular version even when the version number is identical to another (e.g. 109c and 109d are both version 1.0.9.0). These tags can be used in the autoupdate file allowing it to know the difference because of the different checksums. Multiple matching: exeinfo = NULL will match all client exeinfos exeinfo = "war3.exe ??/??/?? ??:??:?? 1568211" will match war3.exe with filesize 1568211 but won't care about the file's date/time versionid = 0x0 will match all client versionids gameversion = 0.0.0.0 will match all client's versions checksum = 0x0 will match all client checksums Note: if you use multiple equations/mpqfiles be sure to put entries with corresponding checksum for each archtag/clienttag versioncheck entries work like a firewall chains, bnetd will match the first entry, then is safe to use entries in descending order, so if we find a bad version, it will be tagged with the tag of entry with the lower version. Last line can be used to match all version unmatched so far Do not include "/" in any of the file names. The version number can be in two forms. If it does not contain a period then 123 is assumed to mean 1.2.3.0. Otherwise it may contain up to three periods. If fewer than four parts are present, the latter ones will be assumed to be zero. For example, 1.8 would be interpreted as 1.8.0.0. Sections will overflow if they are greater than 255. Typically Blizzard will add a 1 in the fourth position to signify an expansion pack and 10 to signify "b" versions. So Brood War 1.08b would have a version of 1.0.8.11. - - - - - - - - - - - - - -equation- - - - - - - - - - - - - - \ - -mpqfile- - \ archtag \ clienttag \ - - - - - - - - -exeinfo- - - - - - - - - \ versionid- \ --verstr-- \ -checksum- \ -versiontag-
Alternative Linked Data Views: ODE     Raw Data in: CXML | CSV | RDF ( N-Triples N3/Turtle JSON XML ) | OData ( Atom JSON ) | Microdata ( JSON HTML) | JSON-LD    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software