YoChoyLaMuete
11-26-2002, 04:58 AM
DogTag is a really nice piece of code written by DogMeat. It allows server admins to disable "force models" server side, force a certain model for all players on the server, apply Dogmeat Map Fixes without additional mods and customizing the ping screen by presenting additional info to the players. It's very versatile, since it's a server mod and doesn't require any additional software, so it can be run both on Linux and Windows servers.
Before running DogTag, you should uninstall any previous version of his map fixes (i.e.: the Stuka on Destroyed Village and the like), and ensure it's the last file on your main folder when it's sorted alphabetically.
This guide applies to DogTag 1.6b or 1.7b (it's not clear, since it's referenced both ways on the internal scripts. All the setup process is done by editing the dmzdogtag_config.scr file which should be located into the main\global folder after uncompressing DogTag.
Settings:
level.dmz_map_mohdm2 = 1
If set to 1, the server will spawn a Stuka on Destroyed Village which will block the path under the map. If set to 0, it wont be spawned.
level.dmz_mapvis_mohdm2 = 0
If set to 1, the players will be able to see the Stuka. If set to 0, the Stuka will be invisible, but still present and blocking the path.
level.dmz_map_mohdm4 = 1
Similar to the previous setting, blocks the path under the map on The Bridge
level.dmz_grenade_obj_team1 = 0
This is a experimental fix for The Hunt, which avoids the "grenade spamming" issue on that map when set to 1.
level.dmz_map_obj_team4 = 1
It's the same fix as for mohdm4, but applyed to the obj version of the map.
level.dmzdt_pausesecurity = 30.0
This is the number of seconds DogTag will "sleep" between checks (see below).
level.dmzdt_sec_forcemodel = 1
If set to 0, clients will be able to use the "forcemodel" setting. If set to 1, server will manage the forced models.
level.dmzdt_securityforcemodel = 0
If set to 0 it will disable the use of forcemodels for every player when level.dmzdt_sec_forcemodel is set to 1.
If set to 1, the server will force the same skin for all the members of each team.
level.dmzdt_sec_playermodel = 0
level.dmzdt_securityplayermodel = "allied_airborne"
When level.dmzdt_sec_playermodel is set to 1, every allied player willl wear the skin assigned on level.dmzdt_securityplayermodel.
level.dmzdt_sec_playergermanmodel = 0
level.dmzdt_securityplayergermanmodel = "german_waffenss_shutze"
Similar as the previous setting, for the axis team.
level.dmzdt_pauselong = 25.0
How long (seconds) each message on the ping screen will last.
level.dmzdt_scroll = 1
(the dt config file is pretty explanatory here)
0 = Default Score Text
1 = Normal Scroller : via dmzdogtag_order.scr (default)
2 = Pre-Config Scroller 2 Pages
3 = Pre-Config Scroller 3 Pages
level.dmzdt_step = 6
How many lines on the MoTD (the text on the ping screen) to scroll at once.
level.dmzdt_maxslots = 18
How many lines (total) on the MoTD.
Dogtag is the best tool available so far to deal with player skins, not only the bright ones, but true cheatskins which are the worst menace for Mohaa players so far. Get used to it and you'll love it. Really.
Regards,
YoChoy
Before running DogTag, you should uninstall any previous version of his map fixes (i.e.: the Stuka on Destroyed Village and the like), and ensure it's the last file on your main folder when it's sorted alphabetically.
This guide applies to DogTag 1.6b or 1.7b (it's not clear, since it's referenced both ways on the internal scripts. All the setup process is done by editing the dmzdogtag_config.scr file which should be located into the main\global folder after uncompressing DogTag.
Settings:
level.dmz_map_mohdm2 = 1
If set to 1, the server will spawn a Stuka on Destroyed Village which will block the path under the map. If set to 0, it wont be spawned.
level.dmz_mapvis_mohdm2 = 0
If set to 1, the players will be able to see the Stuka. If set to 0, the Stuka will be invisible, but still present and blocking the path.
level.dmz_map_mohdm4 = 1
Similar to the previous setting, blocks the path under the map on The Bridge
level.dmz_grenade_obj_team1 = 0
This is a experimental fix for The Hunt, which avoids the "grenade spamming" issue on that map when set to 1.
level.dmz_map_obj_team4 = 1
It's the same fix as for mohdm4, but applyed to the obj version of the map.
level.dmzdt_pausesecurity = 30.0
This is the number of seconds DogTag will "sleep" between checks (see below).
level.dmzdt_sec_forcemodel = 1
If set to 0, clients will be able to use the "forcemodel" setting. If set to 1, server will manage the forced models.
level.dmzdt_securityforcemodel = 0
If set to 0 it will disable the use of forcemodels for every player when level.dmzdt_sec_forcemodel is set to 1.
If set to 1, the server will force the same skin for all the members of each team.
level.dmzdt_sec_playermodel = 0
level.dmzdt_securityplayermodel = "allied_airborne"
When level.dmzdt_sec_playermodel is set to 1, every allied player willl wear the skin assigned on level.dmzdt_securityplayermodel.
level.dmzdt_sec_playergermanmodel = 0
level.dmzdt_securityplayergermanmodel = "german_waffenss_shutze"
Similar as the previous setting, for the axis team.
level.dmzdt_pauselong = 25.0
How long (seconds) each message on the ping screen will last.
level.dmzdt_scroll = 1
(the dt config file is pretty explanatory here)
0 = Default Score Text
1 = Normal Scroller : via dmzdogtag_order.scr (default)
2 = Pre-Config Scroller 2 Pages
3 = Pre-Config Scroller 3 Pages
level.dmzdt_step = 6
How many lines on the MoTD (the text on the ping screen) to scroll at once.
level.dmzdt_maxslots = 18
How many lines (total) on the MoTD.
Dogtag is the best tool available so far to deal with player skins, not only the bright ones, but true cheatskins which are the worst menace for Mohaa players so far. Get used to it and you'll love it. Really.
Regards,
YoChoy