|
 | DoD Source Binds Tutorial |  |
The 907th Binding Guide
Below is a guide that covers a vast majority of knowledge on binds and some useful in game commands for Day of Defeat:Source.
Overview - Binding is a way to make keyboard and mouse shortcuts to do tasks for you in game. Basically you are binding a "key" to do something or say something. I'll use “g” as the example key but, obviously you will have to select a new key each time you create a new bind.
(Anywhere I use the letter “g” in a bind; you can replace it with any key you like.)
Some Examples of a basic bind are:
bind “g” "say Hello friends! >S<"
bind “g” "say_team I need help!"
Make sure you have your binds typed correctly in console or your config.cfg before giving up. A lot of mistakes people make with binds are spelling errors in the bind. Double check your binds before you try to use them.
At the end of this tutorial, there is a list of all the voice commands and bindable keys. Use this section as a quick reference guide to commands and keys.
There are many binds to be made with this information. Everything here is to give you a few ideas on how to get you started binding like a pro. Although binds can be very helpful, some people may not feel that way. The overuse of reload binds and voice command binds may be considered SPAM to some people. Please be smart about your binds, and try not to go overboard and have a bind for every action you do on a server. Most of all, remember that you’re not the only one playing the game. Be considerate to others on the server.
Feel free to look us up! 907th R.A.I.D. Gaming Guild
Simple Communications Binds
Team messages - say_team is the command to activate the chat to your team only
bind "g" "say_team Sorry for the TK buddy. Are we still friends?" This one comes in handy for those bad days ;-)
All Chat - say
bind "g" "say Hello everyone! >S<"
bind “g” "say Good Game everyone"
DOD Source COMMUNICATION FUNCTIONS
%t – time left in the map round*
This is a great command to bind. Instead of typing out “timeleft” in chat and getting a less accurate time, just bind %t to a key.
%l - location*
%c - your class type (i.e. Para FG42)*
%h - your health level*
*Keep in mind that the letters need to be lower case in order to work
**Also note that the %i command to see who was in front of you last no longer works.
The last three make great binds to let your team know where you are with the push of a button. For example:
bind "g" "say_team I am at %l with %h health, I am a (n) %c. HELP!"
In game, it looks like this:
[907th] Bob Smith: I am at The Bridge with 100 health. I am a (n) Rifleman. HELP!
At times, that may be too much information for your team to read. You should only try and bind at most two of those commands in one bind.
For example:
bind “g” "say_team I am at %l with a %c"
in game it looks like this:
[907th] Bob Smith: I am at The Underpass with .30 cal
A few more examples of binds with communication functions:
bind “g” "say_team I just fragged an Axis at %l!"
bind “g” "say_team I Need Cover Fire @ %l"
Advanced binds
It is possible to bind a key/mouse button that already does something coupled with another command. Some of these functions are "reload", "flashlight" and "dropping MG Ammo".
Some examples are...
bind “g” "say_team Cover me, I’m reloading!; +reload; wait; -reload" (reloads gun plus informs team that you are)
bind “g” "say_team MG AMMO DROP! Shoot ‘em up!; dropammo"
It is possible to make a bind for multiple name switches:
bind “f1” "name Havegunwilltravel"
bind “f2” "name Travelinggunsalesmen"
Console Status Bind to Any Key
One key in game grabs ALL Player Steam IDs at that moment and writes them to a file on your hard drive. The file is saved in your Day of Defeat folder. This is great, so you don’t have to worry about grabbing and keeping a problematic player’s STEAM ID.
Paste this into your userconfig.cfg file:
//START Saves all STEAM ID´s to condump000 in your Day of Defeat source\dod folder
bind "g" "steamid"
alias m_wait "m_wait_100"
alias m_wait_lan "wait; wait; wait"
alias m_wait_100 "m_wait_lan; m_wait_lan; wait"
alias m_wait_200 "m_wait_100; m_wait_100"
alias m_wait_300 "m_wait_200; m_wait_100"
alias m_wait_400 "m_wait_200; m_wait_200"
alias m_wait_500 "m_wait_200; m_wait_200; m_wait_100"
alias v "m_wait"
alias v2 "v; v"
alias v3 "v; v2"
alias v4 "v; v3"
alias dv0 "developer 0"
alias dv1 "developer 1"
alias "steamid" "condump; clear; status; v4; v4; v4; v4; condump
// END Saves all STEAM ID´s to condump000 in your Day of Defeat source\dod folder.
*A new file is made after every time you use this bind. Remember to clear out your DoD folder every now and then.
Voice Commands
bind "g" “voice_command”
If you want to use Voice Commands or Hand signals, put them BEFORE the say_team message and use a semi-colon ( ; ) after to separate from the say_team. Make sure the entire bind following the key name is within the quote ( " ) marks.
For example: bind “g” "voice_sniper; say_team There is a sniper in the Plaza window. Heads up! Move fast!"
Voice Commands
voice_takeammo
voice_fireinhole
voice_backup
voice_tank
voice_movewithtank
voice_medic
voice_medic2
voice_left
voice_negative
voice_right
voice_yessir
voice_niceshot
voice_thanks
voice_mgahead
voice_grenade
voice_enemyahead
voice_enemybehind
voice_sniper
voice_areaclear
voice_wtf
voice_cover
voice_gogogo
voice_attack
voice_fireleft
voice_areaclear
voice_fireright
voice_left
voice_right
voice_coverflanks
voice_fallback
voice_ceasefire
voice_hold
voice_sticktogether
voice_displace
voice_usesmoke
voice_usegrens
voice_usebazooka
voice_bazookaspotted
voice_grenade
voice_wegothim
voice_enemyahead
voice_enemybehind
voice_moveupmg
voice_negative
voice_dropweapons
Potential Keys To Bind - besides the regular keyboard, the 1-10 number keys, and the F1-F12 keys
Scroll Keys
Ins
Del
Home
End
Pgdn
Pgup
Arrow Keys
Leftarrow
Rightarrow
Uparrow
Downarrow
Keypad Keys
kp_leftarrow
kp_del
kp_end
kp_downarrow
kp_pgup
kp_ins
kp_5
kp_plus
kp_uparrow
kp_enter
kp_pgdn
kp_rightarrow
kp_slash
kp_minus
kp_home
Mouse Buttons
Wheelup
Wheeldown
Mouse1
Mouse2
Mouse3
*Some mice have more than 3 buttons. Please refer to user’s manual and check if these buttons are compatible in game.
Useful binds/Other Information
key_findbinding [command] - Find the key bound to the specified command.
key_listboundkeys - Lists all the keys which currently have a binding.
unbind [key] - Removes any bindings from the specified key.
unbindall - Removes bindings from all keys
cl_downloadfilter "nosounds" Doesn't allow servers to force you to download sounds (A personal favorite)
voice_menu1 is now voicemenu1
voice_menu2 is now voicemenu2
voice_menu3 is now voicemenu3
+map is now overview_togglezoom
prone is now +alt1
cl_dynamic_xhair 0 is now cl_dynamic_crosshair 0
cl_fog 0 is now fog_enable 0
the command to turn the map on and off is overview_mode
Credits:
• Captain John Miller – Day of defeat forums
• ComradeNachaev[OwP] comradenachaev@cogeco.ca
• 907th RipTide for the DoD1.3 Console Status Bind. I reworked it to work with Source. It just changes the type of log file you get.
• Most of the work I did was regrouping and reorganizing previous data with owners’ permissions. I also updated spelling and removed unnecessary and redundant material.
Please go to our forums to leave comments and feedback on this tutorial: www.907th.com/forum Registration is necessary but is an easy and free process.
© Peterson for 907th.com. Any reproduction without the owner’s permission is strictly prohibited.
|
|
| | Dod Netiquette guide | |
The Art of War - DoD Etiquette
Life on the battlefield can be tough. Not only do you have to worry about running out of ammunition, treading on a landmine, friendly fire, and the enemy - but you need to look out for your squad as well. After all, who else is going to be there to back you up when you head round a corner and stumble straight into an enemy stronghold?
With that in mind, here's a guide to the best way to stay alive and work with your team for victory. Of course, not all of this is essential reading, but if you're new to the mod and want to play it as it should be played - as a team game - as opposed to a WWII-era deathmatch, then read on.
1. Basic Communication
FlipKami84 has already covered a lot of the below in his Teamplay article, so I'll try not to tread on his toes too much...
Day Of Defeat offers a wide range of communication options to help you arrange maneuvers with your team. There’s the obligatory chat channels - write text messages to the whole server with the global mode (default key is Y), and to your team using the teamchat channel (default key is "U").
Then there are the voice commands and hand signals. By using the command menu (accessed with the "K" key), you can select between a variety of different commands and warnings, ranging from "Enemy ahead!" to the classic "GRENADE!!", not forgetting the completely-pointless yet somehow strangely hilarious "Drop Your Weapons!" - allowing you to re-create scenes from Saving Private Ryan if you really want to. One thing to note - most experienced Day Of Defeat players have a lot of the voice commands set to different keys, to avoid having to pause in the heat of battle to search through a command menu. If you want to learn how to do it yourself, I suggest you check out the Official Day Of Defeat Tactics Forum, as there's a ton of threads in there which tell you how to bind your keys - as well as several pre-configured sets available for download.
Finally, we have the most useful option - the voicecomm channel. By holding down the CAPS LOCK key, you can use your PC's microphone to broadcast your voice to your team. No time-outs whilst you type a mini-essay on how you think your team could best make it up the cliff-face, and no fumbling with a command menu; just hold down the key and talk. The best part? You can only talk with your own team, meaning you can discuss your tactics to your heart's content without worrying about the enemy overhearing you. (One small point to note though - there's a 1-second delay between speaking and your message being broadcast - so bear that in mind when you see an enemy grenade come soaring towards your team-mates.)
Communication Etiquette
* DO report your location frequently to your team (check FlipKami84's article for tips on how) - if your team knows where you are and then see your name pop up on the wrong side of a death message, then they know where the enemy is coming from.
* DO keep your voicecomm broadcasts short and to the point. Babbling on for 10 seconds when you could simply say "Enemy MG at Hotel" is not the best way to endear yourself to your team.
* DON'T "voicespam" - if you have voice_grenade set to play whenever you hit your G key, running around the map repeatedly pressing it isn't going to win you any friends.
* DON'T insult people over the chat. Life's too short to worry about a moron half a world away and exactly what he thinks of your parents. As always, arguing over the Internet is completely pointless; even if you win, you're still a loser.
One more thing...
Just because you can see what you've typed, doesn't mean your team can. If you type in a global message between dying and respawning, only other "dead" players - or Spectators - can read what you've written. Typing team messages whilst dead will restrict the recipients to other dead team-mates. Whilst waiting to respawn, the voicecomm channel can also only be heard by dead teammates. And voice commands can only be heard within a certain radius - any team-mates within that radius will get a subtitle, but enemies within earshot won't. Not a problem if you're an Axis player, as I presume you can understand English just fine, but the other way around can prove tricky (unless you're a fluent German speaker). Try playing as an Axis class and testing out the voice commands until you have a vague idea which sound matches which command.
2. Moving As a Group
The last thing you want is to stumble, all alone, straight into a tight group of enemy troops whilst crashing blindly around DoD's levels. As in real life, a few bullets to your body and you won't be getting up (but, unlike real life, you'll respawn a few seconds later). The key to victory lies in the numbers involved - a stronger base of fire will almost always defeat a numerically weaker force. If you're new to on-line games, or have only played deathmatch or Counter-Strike (yes, I am being serious - as well as needlessly biased) before, moving as a group instead of bowling around all by yourself can prove a little daunting. Your best bet is to pick out a teammate and follow them around until you get a feel for the map and the way your team is working together. If you get separated, hole up and wait for another teammate to come past, or fall back to a position where you can safely await backup. By moving in a group of two or more, you force the enemy to pick a target - meaning that the more people you're with, the better the odds of survival (unless you come up against a Machine-Gunner - in which case, fall back and try using a grenade or two to dislodge them). Plus sticking together means that you can start a multi-person flag capture instantly, rather than having to wait for backup - and the less time you have to hang around waiting for a flag's colours to change, the more you can push forwards to victory.
Moving together isn't without its hazards, though. Sticking too tightly together restricts maneuverability, and there's nothing more frustrating - particularly on the Paratrooper maps, where you only get one shot at it before you have to sit the rest of the round in limbo - then to dash out of cover, grenade an enemy position and get shot as you retreat, all because the person behind decided to block your path (and probably got themselves killed in the process). And a tightly-packed group is extremely vulnerable to enemy MG and grenade damage. As a rule of thumb, keep close enough to your teammate to offer covering fire, but not so close that you limit their movement options dramatically.
Movement Etiquette
* DO give backup. If you're running past a flag which your team hasn't claimed yet, and there's a person waiting there for another friendly troop before they can start capturing it, stick around for a few seconds and help them out.
* DON'T give your squad's position away. Running around makes a lot of noise, as does jumping; if the rest of your team are crouched or prone, enabling silent movement, don't broadcast your location to the enemy by deciding your team is moving too slowly and charging around like a headless chicken.
* DON'T get in other people's way. Blocking doorways and narrow passages as you type in a message is considered a major faux-pas, as is blocking the path of a teammate as they try to retreat. Situational awareness is king.
3. Covering Fire
One of the most under-rated positions in Day Of Defeat is the Support role. Sure, you might not be at the front line of the battle, but that doesn’t mean you’re useless – hang back and cover your team as they advance into enemy territory. The sound and sight of a few bullets whizzing close to their position will make even the most battle-hardened DoD veteran think twice about rounding a corner. Hell, it’s what the Machine-Gunner class was made for.
Just watch where you’re shooting. If friendly fire (“FF”) is on, your shots will kill your own team, which is not the best position to be in – especially as most servers will kick you after three or four Team Kills (or TKs). But even if FF is off, hitting your own team will slow them down and, if you shoot them in the head, blind them with a red mist which will only fade slowly. Again, it’s not the most stylish way to enter enemy territory: half-blind and cursing your teammates’ aim. One thing you need to be very careful of is the use of grenades. Even if friendly fire is off, any grenades you throw will harm you, but leave your teammates unscathed. One way to use this to your advantage is as an Ally on one of Day Of Defeat’s set-piece beach maps – advance up the flanks and throw some grenades up onto the cliffs, and tell your team to charge just before the 5-second fuse is due to blow. This offers a distraction to any defenders up on the cliff top, and will also obscure your movement with a thick cloud of smoke that takes several seconds to dissipate. Just make sure you hold back and take the opportunity to lay down some cover fire whilst you avoid death by your own grenade.
One final rule for covering fire is one that’s employed in real life army, police and SWAT training. It’s known as the “laser” rule – basically, you imagine a laser being projected from the tip of your barrel into infinity. If at any point you move your barrel so that it crosses a comrade’s body, the “laser” is broken and they are put at risk. Whilst you’re not in enemy territory, it’s not much of a problem – after all, unless you’re a complete fool you wouldn’t pull on your trigger until a contact was imminent – but as soon as you enter a battle zone it’s a different story. Try pairing off with someone at the spawn and following them around, and when you start to hear enemy movement or fire comes your way, crouch down and lay down covering fire on the suspected area as your teammate moves up to scout the area. Believe it or not, this will give you a much higher success rate, as enemies who get lucky and ice your comrade will think that the area is clear and then follow up, hopefully running straight into your sights.
Covering Fire Etiquette
* DO offer covering fire whenever possible. If you’re an MG, you have no excuse not to cover your troops as they advance.
* DO watch your ammo. Call out to your teammates if you’re running low – most organized DoD players will drop ammo to an MG crying out for it.
* DON’T aim too low, especially if Friendly Fire is on. A steady aim with the MG can help your team advance under its cover without placing them at its mercy.
4. Orders, “Cheaters” and other things
Just to finish, I’ll cover a few more of the things which new players may find useful.
Orders
On most DoD servers you play on, there will be at least one person who reckons they’ve got what it takes to order the rest of their team around, or at least encourage them to victory. Try listening to them at first – and if you’re winning, keep listening. However, if the orders or information they’re feeding you turns out to be useless, or worse leads your team into the same ambushes time and time again, try offering your own suggestions (voicecomms work best for this; grab yourself a decent earphone/microphone headset for the best DoD experience). If you’re giving orders, or requesting backup, make sure you follow through.
Good example? Trying to execute a flanking maneuver, you call for backup and then as soon as it arrives you charge through together, decimating the opposition.
Bad example? Calling for backup and then sitting there, staring into space as the enemy finds your position and grenades the whole lot of you.
"Cheaters"
As with most Half-Life modifications – and any on-line games – accusations of cheating are unfortunately rife. 9.9 times out of 10, the “cheaters” are nothing more than quick-witted veteran players who’ve learned the best tricks, like listening for enemy footsteps to give them an idea of where the main threat is, or how to shoot accurately whilst in mid-air (you can’t shoot whilst in the upward arc of a jump, but in the downward section your gun becomes active again). Occasionally you will come across someone who is blatantly beyond the most skilled of honest players – someone who can track and shoot you through a solid wall, or who can fire a heavy automatic weapon with far too much accuracy, and hit you in the head each time. On these occasions, there are several courses of action to choose from. You can scream “CHEAT!” , which – unless you have some pretty hefty evidence – will only serve to annoy and confuse the person you’re accusing, and most likely any server admins as well. This is the least productive and immature way to behave.
You could switch to the spectating team and watch the person you suspect through first-person mode – if you can’t follow them, or their graphics are distorted, or their aim magically “snaps” onto an enemy, then the odds are that they are cheating. Take some screenshots of their actions, then take it to the admins – if it’s a clan server, most will have a web page and a contact e-mail to send stuff to. If it’s a public server, the provider – for example, Jolt or BlueYonder in the UK – have IRC channels and forums to take your evidence to. If you’re playing on a clan server, there will most likely be an admin present. If so, try asking them to join you on the spectator team so you can discreetly talk about it. Broadcasting it over the global chat channel is brazen and unnecessary, and will most likely annoy more people than it helps.
Finally, you could just let it go. Most servers are protected by Valve Anti-Cheat, which doesn’t ban cheaters immediately like the other anti-cheat programs do. Instead, it waits a few days, so that cheat coders can’t see instantly if their cheats are undetected by the software or not. The odds are that if you see someone you think is cheating more than a couple of times on the same servers, then they’re just skilled and you shouldn’t really judge them.
Take a look around
Not everyone is good at a game the second they sit down at the keyboard. As a result, you may find yourself occasionally frustrated by the lack of common sense and co-ordination you’ll encounter, as people run straight past you whilst you’re trying to capture a two-man flag. If you keep seeing a complete lack of teamwork on public servers, look for a Clan-rented server and try playing there; you’ll generally find that there’s a much higher degree of teamwork and co-operation involved, with people tripping over each other to help you capture a flag.
Take your lumps with a smile
Try to be kind and courteous to everyone you can. It’s a fact of life that ‘net is full of bigoted, foul-mouthed trash who aren’t afraid to share their blinkered views, or players who seem a little too good with a rifle. Never let them get under your skin; doing so will only give them satisfaction. Instead, ignore them as best you can. There’s no need to rise to the bait of people who can’t accept that you might be able to beat them, or who find it fun to team-kill. If you’re playing a game and it’s ruined by people like this, just walk away and find a different server – there’s no shortage of them, after all. By insulting them back, or returning fire, you’ll only provoke them further. Alternatively, ask an admin to remove them from the game. If you’re playing on a Clan server, look for a player whose name carries a tag that matches part of the server name, and talk to them about it; however, most respectable clans keep their servers well-policed and fun to play on.
Watch your language
Finally, a major point about vocal etiquette and its application in on-line games. Swearing is all too common; we all do it, no matter how much we’d like to avoid it. Therefore, slipping a swearword in by accident when you’re talking into your microphone is acceptable. However, typing one out is taking it too far – there’s nothing subconscious or spontaneous about typed text. A lot of servers try to keep bad language to a minimum, and some employ text filters to kick people who persistently swear. So act in the proper manner, don’t insult people and don’t whine about skilled players, and you’ll have no reason to be kicked off any server you come across.
All said, remember that Day of Defeat is a game – a highly-atmospheric one, but a game nonetheless. If a player is getting to you, or you’re suffering a bad gaming streak, walk away for a couple of hours. Getting frustrated and keeping going just leads to messy situations that you have to clear up later. So play nice out there, and I’ll see you on the battlefield!
Please go to our forums to leave comments and feedback on this tutorial: www.907th.com/forum Registration is necessary but is an easy and free process.
Published on 907th.com after the original author's approval. Copyrights owned by DarkPenfold and PlanetHalf-Life.com, website owned by IGN Entertainment, Inc. Any reproduction without the owner’s permission is strictly prohibited.
|
|
| | Install a Custom Crosshair | |
First off, you need to find a site that offers crosshair sprites or crosshair packs. I would suggest the website DoD Editing Center
If you scroll down the page, you’ll find a Sprites section on the right hand sidebar. Click on the crosshair subcategory.
My personal favorite crosshair pack is, “Capt. Darling’s Xhairs 1.3”
They have a nice variety as shown here:
Once you download the .zip file, unzip it to your desktop.
Now open up your DoD folder located here:
C:\Program Files\Valve\Steam\SteamApps\YOUR EMAIL\day of defeat\dod
In this folder, find and open the sprites folder. Now drag the “customxhair.spr” file from your desktop into your sprites folder.
Now we get to the tricky part. Go back to your DoD folder and open up your config.cfg file.
Type or paste in the following:
bind "k" "xtog"
(Since this is a bind, you can assign it to any key you want. Just replace the letter K with any available key you may have.)
Save your config.cfg file. I recommend that you make it read only. Do so by right clicking the file and selecting properties. Check off the “read only” box and click ok.
Now you need to open up your userconfig.cfg file. If you don’t have one, open up a notepad and save the file named “userconfig.cfg” in your DoD folder.
In your userconfig.cfg, paste this in there:
alias xtog "xtog1"
alias xtog0 "gl_spriteblend 1; cl_xhair_style 0; alias xtog xtog1"
alias xtog1 "gl_spriteblend 0; cl_xhair_style 1; alias xtog xtog2"
alias xtog2 "gl_spriteblend 0; cl_xhair_style 2; alias xtog xtog3"
alias xtog3 "gl_spriteblend 1; cl_xhair_style 3; alias xtog xtog4"
alias xtog4 "gl_spriteblend 1; cl_xhair_style 4; alias xtog xtog5"
alias xtog5 "gl_spriteblend 1; cl_xhair_style 5; alias xtog xtog6"
alias xtog6 "gl_spriteblend 1; cl_xhair_style 6; alias xtog xtog7"
alias xtog7 "gl_spriteblend 0; cl_xhair_style 3; alias xtog xtog8"
alias xtog8 "gl_spriteblend 0; cl_xhair_style 4; alias xtog xtog9"
alias xtog9 "gl_spriteblend 0; cl_xhair_style 5; alias xtog xtog10"
alias xtog10 "gl_spriteblend 0; cl_xhair_style 6; alias xtog xtog11"
alias xtog11 "gl_spriteblend 1; cl_xhair_style 7; alias xtog xtog12"
alias xtog12 "gl_spriteblend 1; cl_xhair_style 8; alias xtog xtog13"
alias xtog13 "gl_spriteblend 1; cl_xhair_style 9; alias xtog xtog14"
alias xtog14 "gl_spriteblend 1; cl_xhair_style 10; alias xtog xtog15"
alias xtog15 "gl_spriteblend 0; cl_xhair_style 11; alias xtog xtog16"
alias xtog16 "gl_spriteblend 0; cl_xhair_style 12; alias xtog xtog17"
alias xtog17 "gl_spriteblend 0; cl_xhair_style 13; alias xtog xtog18"
alias xtog18 "gl_spriteblend 0; cl_xhair_style 14; alias xtog xtog19"
alias xtog19 "gl_spriteblend 1; cl_xhair_style 15; alias xtog xtog20"
alias xtog20 "gl_spriteblend 0; cl_xhair_style 16; alias xtog xtog0"
Save your userconfig.cfg file, then open up DoD.
You can now push the K key (or whatever key you bound “xtog” to) and scroll through the different colored and styled crosshairs.
Please go to our forums to leave comments and feedback on this tutorial: www.907th.com/forum Registration is necessary but is an easy and free process.
© Peterson for 907th.com. Any reproduction without the owner’s permission is strictly prohibited.
|
|
| | 907th Spray creation tutorial | |
This guide will help you set up a custom Spray Like this one:
This is a step-by-step guide to help you make custom sprays
The first step to creating a custom spray is to have a design ready to go. If you need help finding a design feel free to ask. Once you have your image save it to the desktop or your dod folder.
Next download this program: HlTagConverter_014.zip
This program will assist changing your design to a format that will allow your design to be seen.
Unzip the file to a location where it will be easy to find.
I suggest putting it into your “C:\Program Files\Valve\Steam\SteamApps\\day of defeat” Folder. Once you have it unzipped double-click on the “HlTagConverter.exe” This Screen will open:
Click on “Open Image” button.
Next, locate the image file that you would like to use and open it:
you get this:
The next step is to adjust your image. When you hit the “Adjust Image” button, this screen will pop up:
It will resize your image to the maximum size it can be and still work correctly. Hit the “Apply changes and convert to 256 colors” button.
This screen pops up next.
Hit the “Save Tag” button and select the :
and hit “OK”
You then must save the .WAD file into “C:\Program Files\Valve\Steam\SteamApps\\day of defeat\ \dod” folder. The name MUST BE tempdecal
Hit “Save”
Hit “Save” again and select the tempdecal.wad file. Right-click on it and go to “properties.”
Select the ‘Read-only” option on the bottom and click “OK” Then hit “Cancel” on the save screen and then “Close” on the program.
Finally go to any dod server and hop on. Go to the nearest wall and hit “t” ( this is the default key). Have patience, It may take a few sprays for your tag to work. This is the end result:
If you have any question there is an old readme file included with the zip. If that does not help please just ask and we will be happy to help.
Please go to our forums to leave comments and feedback on this tutorial: www.907th.com/forum Registration is necessary but is an easy and free process.
© Kelldroma for 907th.com. Any reproduction without the owner’s permission is strictly prohibited.
|
|
| | 907th Binds Tutorial | |
The 907th Binding Guide
Below is a guide that covers a vast majority of knowledge on binds and some useful in game commands for Day of Defeat.
Overview - Binding is a way to make keyboard and mouse shortcuts to do tasks for you in game. Basically you are binding a "key" to do something or say something. I'll use f1 as the example key but, obviously you will have to select a new key each time you create a new bind.
(Anywhere I use the letter “g” in a bind; you can replace it with any key you like.)
Some Examples of a basic bind are:
bind “g” "say Hello friends! >S<"
bind “g” "say_team I need help!"
Make sure you have your binds typed correctly in console or your config.cfg before giving up. A lot of mistakes people make with binds are spelling errors in the bind. Double check your binds before you try to use them.
At the end of this tutorial, there is a list of all the voice commands, hand signals, and bindable keys. Use this section as a quick reference guide to commands and keys.
There are many binds to be made with this information. Everything here is to give you a few ideas on how to get you started binding like a pro. Although binds can be very helpful, some people may not feel that way. The overuse of reload binds and voice command binds may be considered SPAM to some people. Please be smart about your binds, and try not to go overboard and have a bind for every action you do on a server. Most of all, remember that you’re not the only one playing the game. Be considerate to others on the server.
Feel free to look us up!
907th R.A.I.D. Gaming Guild
Simple Communications Binds
Team messages - say_team is the command to activate the chat to your team only
bind "g" "say_team Sorry for the TK buddy. Are we still friends?" This one comes in handy for those bad days ;-)
All Chat - say
bind "g" "say Hello everyone! >S<"
bind “g” "say Good Game everyone"
DODv.3 COMMUNICATION FUNCTIONS
%t – time left in the map round*
This is a great command to bind instead of typing out “timeleft” in chat and getting a less accurate time, just bind %t to a key
%l - location*
%i - last buddy you have seen (name actually appeared in center screen)*
%c - your class type (i.e. Para FG42)*
%h - your health level*
*Keep in mind that the letters need to be lower case in order to work
The last four make great binds to let your team know where you are with the push of a button. For example:
bind "g" "say_team I am at %l with %h health, I last saw %i, I am armed with a(n) %c"
In game, it looks like this:
[907th] Bob Smith: I am at The Bridge with 100 health, I last saw Pvt. Bob, I am armed with a(n) MP40.
**At times, that may be too much information for your team to read. You should only try and bind at most two of those commands in one bind. **
For example:
bind “g” "say_team I am at %l with a %c"
in game it looks like this:
[907th] Bob Smith: I am at The Underpass with .30 cal
A few more examples of binds with communication functions:
bind “g” "say_team I just fragged an Axis at %l!"
bind “g” "say_team Watch yer' six o'clock %i!"
Advanced binds
It is possible to bind a key/mouse button that already does something coupled with another command. Some of these functions are "reload", "flashlight" and "dropping MG Ammo".
Some examples are...
bind “g” "say_team Cover me, I’m reloading!; +reload; wait; -reload" (reloads gun plus informs team that you are)
bind “g” "say_team MG AMMO DROP! Shoot em up %i!; dropammo" whom you dropped it too.)
It is possible to make a bind for multiple name switches:
bind “f1” "name Havegunwilltravel"
bind “f2” "name Travelinggunsalesmen"
How to take a perfectly clean screenshot
This will allow you to take screenshots without any kind of hud, minimap, weapon to hinder it. Only thing u can't take out is the crosshair so switch to your knife/spade not to have it right before hitting the key to screenshot
First, add this to your autoexec.cfg or userconfig.cfg:
alias wait2 "wait;wait"
alias wait4 "wait2;wait2"
alias wait8 "wait4;wait4"
Next, add this to your config.cfg:
bind "g" "cl_hud_msgs 0;cl_hud_ammo 0;cl_hud_health 0;cl_hud_reinforcements 0;cl_hud_objtimer 0;cl_hud_objectives 0;cl_minimap 0;cl_dmsmallmap 0;hud_deathnotice 0;r_drawviewmodel 0;net_graph 0;hud_saytext 0;wait8;snapshot;wait8;cl_hud_msgs 2;cl_hud_ammo 1;cl_hud_health 1;cl_hud_reinforcements 1;cl_hud_objtimer 1;cl_hud_objectives 1;cl_minimap 2;cl_dmsmallmap 1;hud_deathnotice 2;r_drawviewmodel 1;net_graph 1;hud_saytext 1"
* If you do not have netgraph selected already (FPS showing at the bottom right of your screen) then delete the netgraph part in the process.
** hud_deathnotice time will set the amount of time the frag messages appear. 0 disables them, 2 is for two seconds. Pick what you think is best for you
Console Status Bind to Any Key
One key in game grabs ALL Player Steam IDs at that moment and writes them to a file on your hard drive. The file is saved in your Day of Defeat folder. This is great, so you don’t have to worry about grabbing and keeping a problematic player’s STEAM ID.
Paste this into your userconfig.cfg file:
//START Saves all STEAM ID´s to qconsole.log in your Day of Defeat folder
bind "g" "steamid"
alias m_wait "m_wait_100"
alias m_wait_lan "wait; wait; wait"
alias m_wait_100 "m_wait_lan; m_wait_lan; wait"
alias m_wait_200 "m_wait_100; m_wait_100"
alias m_wait_300 "m_wait_200; m_wait_100"
alias m_wait_400 "m_wait_200; m_wait_200"
alias m_wait_500 "m_wait_200; m_wait_200; m_wait_100"
alias v "m_wait"
alias v2 "v; v"
alias v3 "v; v2"
alias v4 "v; v3"
alias dv0 "developer 0"
alias dv1 "developer 1"
alias "steamid" "condebug; clear; status; v4; v4; v4; v4; condebug
// END Saves all STEAM ID´s to qconsole.log in your Day of Defeat folder.
Voice or Hand Signals
bind "g" “voice_command”
If you want to use Voice Commands or Hand signals, put them BEFORE the say_team message and use a semi-colon ( ; ) after to separate from the say_team. Make sure the entire bind following the key name is within the quote ( " ) marks.
For example: bind “g” "voice_sniper; say_team There is a sniper in the Plaza window. Heads up! Move fast!"
Voice Commands
voice_ceasefire
voice_usegrens
voice_moveupmg
voice_mgahead
voice_enemybehind
voice_enemyahead
voice_gogogo
voice_assault
voice_displace
voice_areaclear
voice_fireleft
voice_fireright
voice_fireinhole
voice_negative
voice_coverflanks
voice_sticktogether
voice_spreadout
voice_dropguns
voice_takecover
voice_backup
voice_needammo
voice_medic
voice_hold
voice_right
voice_left
voice_yessir
voice_grenade
voice_flank
voice_cover
voice_fallback
voice_attack
voice_sniper
Hand Signals
signal_enemyspotted
signal_spreadout
signal_holdposition
signal_takecover
signal_coveringfire
signal_areaclear
signal_flankright
signal_moveout
signal_flankleft
signal_grenade
signal_enemyleft
signal_enemyright
signal_backup
signal_sniper
signal_yes
signal_no
signal_fallback
signal_sticktogether
Potential Keys To Bind - besides the regular keyboard, the 1-10 number keys, and the F1-F12 keys
Scroll Keys
Ins
Del
Home
End
Pgdn
Pgup
Arrow Keys
Leftarrow
Rightarrow
Uparrow
Downarrow
Keypad Keys
kp_leftarrow
kp_del
kp_end
kp_downarrow
kp_pgup
kp_ins
kp_5
kp_plus
kp_uparrow
kp_enter
kp_pgdn
kp_rightarrow
kp_slash
kp_minus
kp_home
Credits:
• Captain John Miller – Day of defeat forums
• ComradeNachaev[OwP] comradenachaev[at]cogeco.ca
• 907th RipTide for the Console Status Bind
• 907th Furyo for reworking the Clean Screenshot bind to work with STEAM and 1.0 versions!
• Most of the work I did was regrouping and reorganizing previous data with owners’ permissions. I also updated spelling and removed unnecessary and redundant material.
Please go to our forums to leave comments and feedback on this tutorial: www.907th.com/forum Registration is necessary but is an easy and free process.
© Peterson for 907th.com. Any reproduction without the owner’s permission is strictly prohibited.
|
|
| | How to get started mapping in Source: Getting Hammer 4.0 ready (2/2) | |
If you haven't looked at the first part of this tutorial, please refer to this link to view it: Getting Hammer 4.0 ready (Part 1)
1) Game Data Files: This field will always refer to a .fgd file, which is the file that contains all the entities and game information for your specific game. Don’t change it unless you’re an expert user and want to try a new fgd file.
2) Texture format: Because HL2 introduced a new 3D engine, it also introduced new textures. In Source, textures are no longer called textures but “Materials” because they not only are the textures but also contain the information the engine needs to render them (see our tutorials section for a detailed explanation). The only reason you would want to change this field would be to map under the Half-Life engine.
3) Map Type: Same as above, do not change unless you want to map under the Half-Life engine.
4) Default PointEntity class: This refers to the default non brush based entity you want to see appear whenever you use entities. The default info_player_start defines spawn points for your character in game. Change it to whichever you prefer, light may be a good choice as you’ll be using a lot of these in your map.
5) Default SolidEntity class: Same as above, this refers to the default brush based entity you want your brush to turn to when turning it into an entity. This default one is used to turn detailed parts of your architecture into func_detail entities, which use fewer resources to be rendered, and improve the overall playability of your map. As a brand new mapper, you should probably be reading a lot on the different key entities before you start mapping, or your project could be unplayable before long. Set this entity to whichever you like. For example, if you will be working on a big set of breakable windows, you may want to set it to func_breakable automatically
6) Default texture scale: Self explanatory, the texture scale represents the ratio at which the original texture should apply to your surface, by default. Of course this is changeable in the materials tools within Hammer. 0.25 is the best choice, because most Valve textures are designed to fit better with that parameter.
7) Default Lightmap scale: I wouldn’t change this setting in the default options, but once you become an experienced mapper, you may want to try different settings depending on your map design and surfaces.
8) Cordon Texture: Cordons are a new tool in Hammer 4 that help defining a certain area within a certain map that needs to be compiled for testing, instead of having to compile the whole map all the time (which increasingly takes time as your map gets bigger). Any defined area should still contain all mandatory entities to run it as if it was the entire map (spawn points, environment lighting, etc). This setting defines which texture should be applied to the cordons (or limits of that defined area). I see no reason to change it from skybox, because you’ll probably want to look at a sky above your head rather than any other texture…
9) Game Executable Directory: Easily enough, this points to your selected game executable file. As you can see it looks for the Sourcesdk folder wherever it may be placed on your computer. You therefore don’t have to enter the whole path to your .exe file.
10) Game Directory: Same as above, only for the main game folder.
11) Hammer Map Directory: Again, same as above, only this time it refers to the folder in which you wish to store your maps. You can change it to whichever fits you best.
This is it for this first settings tab. Here is a short description of what the others contain.
Those are self explanatory as well. For performance reasons, you may want to reduce the undo levels, which control the amount of times you can delete any action you may have done, therefore controls the amount of memory needed to perform these undo levels. This only depends on the amount of RAM memory you have, and you’ll see if you need to change this setting as you work on your map and it gets bigger.
Hammer display window is divided in 4 areas. 3 of which are grids for each dimension you work with (x ->y ; x -> z and y->z or top, side and front). Change anything you may want. I like my grid to be as small as possible to allow for more detailed work. This setting only goes down to 4 (size) but you can reduce it to 1 using your “[“ key (and increase it again using “]”)
This set of options only controls the 4th display area: the 3D render. This is of course and by far the most demanding of the 4 areas resource wise, and you should carefully use these options to make your mapping experience more enjoyable. For example the Back Clipping Plane controls the distance that is being rendered before any other content disposed beyond is no longer rendered. This directly impacts the amount of work your computer needs to do so you can see what you’re working on. Depending on your experience you may want to change this setting.
I will overlook the “Materials” tab which doesn’t concern any brand new user and would go beyond the scope of this tutorial.
In this last tab, you can select which programs to use to compile your map. For more details on the different processes (BSP, VIS and RAD), please see another tutorial. Just know that you don’t necessarily need the three for your map to work (only the BSP is necessary) but that all 3 will be needed to test your lighting and generally speaking when you release your map of course.
Different programs exist to compile your map. Those are the ones provided by Valve with the SDK, which arguably produce the best result. You may also want to try the Custom Source Tools made by Adam McKern from http://www.zhlt.tk/
Then simply head for the “File” menu, select new and start mapping !
This concludes this tutorial to get yourself ready mapping. I hope it will be useful to some.
Please go to our forums to leave comments and feedback on this tutorial: www.907th.com/forum Registration is necessary but is an easy and free process.
© Furyo for 907th.com. Any reproduction without the owner’s permission is strictly prohibited.
|
|
| | How to get started mapping in Source: Getting Hammer 4.0 ready (1/2) | |
How to get started mapping in Source: Getting Hammer 4.0 ready (1/2)
This tutorial aims at helping any brand new Source mapper getting started with Valve’s mapping software: Hammer
Since Steam was put in place, Hammer is a lot easier to configure. First of all you’ll need to download it. It’s located in your “Play Games” menu in Steam, at the bottom of the list in the “Tools” Category.
Don’t search for “Hammer”. Hammer is only one of the many things included in the Source Software Development Kit (SDK). As with any other games in Steam, “Source SDK” should appear greyed out, which means you simply don’t have the program yet. Double click on it and you’ll start downloading it, just like any other games.
Once downloaded, it’ll appear in white, as seen in the above picture. Double click on Source SDK to install it and make another window appear:
As you can now see, the SDK is made of more than just a mapping software… In this tutorial, we’ll only consider the first choice in the list: Hammer Editor, as well as the “Current Game” selection bar at the bottom of the window.
Think of the”Current Game” as the settings for Hammer. The game you choose automatically impacts the way Hammer will work once launched. The reason for this is that Steam automatically sets up Hammer so it works for the selected game, so you don’t have to set up everything yourself (unlike previous versions of Hammer).
At the time of this tutorial, only three games are available: Half-Life 2, Counter Strike Source and Half-Life 2 : DeathMatch. Whenever a new Source game is made available on Steam, the SDK will receive an update and the new game will automatically present itself in that list.
Now select the game you want to map for, and double click on “Hammer Editor” at the top to launch your new favourite program. In this tutorial, I’ll use Half-Life 2 as the game to map for.
As this point, Hammer should work and, upon first launch, come up with this new window:
As you can see, Steam has automatically set up Hammer to work for HL2. These are the default settings and allow any mapper to start working on his/her project. If you are eager to start working on your map, consider this the end of the tutorial. For those who want to learn more about these options, let’s review them together here
Please go to our forums to leave comments and feedback on this tutorial: www.907th.com/forum Registration is necessary but is an easy and free process.
© Furyo for 907th.com. Any reproduction without the owner’s permission is strictly prohibited.
|
|
|
News
