About: Auto Update   Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

This is a list of client tags and their equivalent autoupdate files and version information. This file will be ignored for certain clients if skip_versioncheck is enabled in the bnetd.conf file. Only the first matching line is used. If no lines match then no upgrade will be attempted and the client will remain at its current version. Note: if you want to use the autoupdate wildcard entries, you'll also need to uncomment the corresponding wildcard entries in versioncheck.conf. Do not include "/" in any of the filenames. Example: With the following line: IX86 W3XP W3XP_107A W3XP_IX86_1xx_111A.mpq

AttributesValues
rdfs:label
  • Auto Update
  • Auto update
rdfs:comment
  • This is a list of client tags and their equivalent autoupdate files and version information. This file will be ignored for certain clients if skip_versioncheck is enabled in the bnetd.conf file. Only the first matching line is used. If no lines match then no upgrade will be attempted and the client will remain at its current version. Note: if you want to use the autoupdate wildcard entries, you'll also need to uncomment the corresponding wildcard entries in versioncheck.conf. Do not include "/" in any of the filenames. Example: With the following line: IX86 W3XP W3XP_107A W3XP_IX86_1xx_111A.mpq
dcterms:subject
dbkwik:pvpgn/prope...iPageUsesTemplate
abstract
  • This is a list of client tags and their equivalent autoupdate files and version information. This file will be ignored for certain clients if skip_versioncheck is enabled in the bnetd.conf file. Only the first matching line is used. If no lines match then no upgrade will be attempted and the client will remain at its current version. Note: if you want to use the autoupdate wildcard entries, you'll also need to uncomment the corresponding wildcard entries in versioncheck.conf. Do not include "/" in any of the filenames. The versiontag is used to identify a particular version as specified in the versioncheck configuration file. It works like this: versioncheck identifies a version by reported version number, checksum, clienttag, etc. The autoupdate then uses the arch tag,client tag and version tag to find the needed update file. War3 and War3x clients have different mpq files for the different game languages. This is accounted for by the server, and the client will get the correct file. Only one entry is needed per arch, client, and version tag. Example: With the following line: IX86 W3XP W3XP_107A W3XP_IX86_1xx_111A.mpq war3x english clients will receive the file "W3XP_IX86_1xx_111A_enUS.mpq" where russian clients will receive the file "W3XP_IX86_1xx_111A_ruRU.mpq" and german clients will receive the file "W3XP_IX86_1xx_111A_deDE.mpq" Make sure all the required mpq files are in the files directory or autoupdate will not work. The avaliable language files are: enUS csCZ deDE esES frFR itIT jaJA koKR plPL ruRU zhCN zhTW The format of this file is as follows: archtag clienttag versiontag -----update file-----
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