***DOD Ultimate Sticky!*** (Rules and all. Info for everyone's eyes)

[|CoR| Cool_Hand_Luke]

Our current server rules 9/13/09:

http://www.corclan.com/gameassets/dod/motd/dod1motd.html

God Bless,
Doc

Spawn Camping Rules

I’m the General of DoD and this is the rule. Shooting into and out of spawn is not against the rules.  Shooting into spawn for no other purpose other than to rack up a high score is against the rules. This is to be determined by the senior admin on the server at the time and the decision of that admin is to be followed. Of course there are an infinite number of situations and possible scenarios, so I hope that everyone (admin and non-admin alike) understand that common sense is required in this life and this is no exception to that rule.  If the intent is to pin down you’re opponents so as to allow your teammates to progress and capture the map this is perfectly acceptable.  And shooting out of spawn in that situation to attempt to get out and retake ground is also perfectly acceptable.  What is not acceptable is to take a position where the opponents can not possibly advance and your sole purpose is to sit and rack up kills this would be considered not part of game play but simply bad sportsmanship this is not allowed I hope this makes this perfectly clear to everyone and if you have any questions, PM me thank you.  General Stinker

|CoR| General Disclaimer

|CoR| General Disclaimer:

Statements made by members and non-members of |CoR| may or may not reflect the thoughts and opinions of |CoR|'s leadership.  The community here at |CoR| City of Refuge is varied in their history and background.  With such a large group spanning the globe, it is inevitable that some may have differing views than others.  As different as those views may be, they may or may not be held by the leadership of |CoR|.  In order to ascertain an official position by the leadership of |CoR| on any given issue, please visit our Statement of Faith first, then ask any one of our Team Generals, Support Staff, Vice-President, and President.

If you disagree with an opinion given by any member or non-member of |CoR|, please treat each other with dignity and respect.  |CoR|'s Terms of Service lists the conduct required by |CoR| members and non-members alike.

How To: Bind a key for Recruiting & Stop Cussing

The syntax for the bind command is as follows:

bind <key> <command>

Samples:

For DOD 1.3

So for the Recuiting bind I would do something like this for dod

bind k "amx_csay For |CoR| recruiting info, go to http://recruiting.corclan.com"

So for the Stop Cussing bind I would do something like this for dod

bind k "amx_csay Please do not use foul language, this is a Christian Server, thank you."

For DOD:SOURCE

So for the Recuiting bind I would do something like this for DOD:Source

bind k "sa_csay For |CoR| recruiting info, go to http://recruiting.corclan.com"

So for the Stop Cussing bind I would do something like this DOD:Source

bind k "sa_csay Please do not use foul language, this is a Christian Server, thank you."

That would to a centered message to everyone on the server.  If you wanted to just post it as a normal chat message, replace amx_csay with say.

Thank you DDogbert, that is very helpful.
Grace & Peace,

What does "rate" mean?

Here is a description of what "Rate" means and how to set yours correctly, as reported directly from Valve:

Rates
Rates are, simply put, your connection settings for how often you communicate with the host server.

Setting Rates
Setting your rates is very simple.  In the console, use the following commands for the corresponding rate, substituting the number you want for #:

Rate - rate #
Cmdrate - cl_cmdrate #
Updaterate - cl_updaterate #


Explanation of Rates
Most people do not know what their rates do for them, if they know that there is such a thing as rates.  Rates determine how often you sync with the server.  There are three rates, rate, cmdrate, and updaterate.

Rate is usually in the range of 10000 to 30000.  This is the maximum bytes per second you receive from the server.  Your rate should be determined by your connection.  For example, with a 128k connection, you would be able to receive a maximum of 12800, 256k should be able to receive 25600, and so on.  Note that with a 56k modem, you should be using a rate of 5600, which is not allowed on LoC servers (the minimum is 10000), but those using a 56k modem are never going to be able to maintain less than 200 ping (also a requirement on the server) and will likely be auto-kicked for high ping.

Cmdrate is usually in the range of 20 to 100.  This is the number of times per second that your computer sends a packet, which is a bundle of information, to the server.  General rule of thumb is to take your rate, divide by 200, and round down for a maximum.  For example, 12800 for a rate would result in a maximum cmdrate of 64.  The most a server can handle varies, like the LoC Day of Defeat server runs on 66 tick and will handle 66 cmdrate maximum.  Anything over 66 will be treated like 66.  The LoC Counterstrike server runs on 100 tick and will handle 100 cmdrate maximum.  The minimum cmdrate on LoC servers is 20 to prevent players “glitching” and “warping” across the map.

Updaterate is exactly the same as cmdrate but involves the number of packets per second your computer receives from the server.  Again, the minimum is 20 and may go as high as 100.  Remember, however, that the maximum used by LoC Day of Defeat server is 66 and any value above 66 will be treated as 66, while on the LoC Counterstrike server, the maximum is 100.

To determine your optimum functional rates, use net_graph 3 to view your in, out, ping, and choke while changing rates.  Your in and out will be capped based on your cmd and update rates, your ping will change based on your rate, and choke will change based on the cmd and update rates.  You want to minimize your ping and choke at the same time.  Ping is basically your “lag” in communicating with the server and occurs when your rate is low and you receive less packets per second.  Choke occurs when the server detects that you have not received the last packet it sent you and holds packets until the last one it sent reaches you.  Choke is caused by a cmd or update rate that is set too high for your connection, causing a digital traffic jam while the server tries to communicate faster than your computer is capable.

By experimenting with many combinations, you will find the optimal setting for your connection and computer.  This optimal setting will greatly enhance your gameplay, from an increase in frames per second to a decrease in ping and choke.

Also, your optimum setting is what is best for the server.  Rates that are too high will cause you to “glitch” or “warp” on the screens of other players, something that is not beneficial to the server by any means.  Rates that are too low will cause the same but you will notice the same “glitching” and “warping” in other players as they notice in you.  This is the reason we must often ask players to change their rates, to make sure the game is fair and fun for everyone.

Here's a tweak for this week:
If you have some tweaking tips, please pass them onto a general and we will be sure to post them.  Have fun.

1. Go to C:Program FilesSteamSteamAppsyouremailday of defeatdod.
2. Open your config.cfg file. Your config.cfg a can be opened, edited, and saved with Notepad, Wordpad, Word, Works, etc. Make sure you backup this file to a floppy disk periodically. Some DoD servers change it without you knowing.
3. For a much nicer white colored in-game text find con_color and change the value to "255 255 255". 4. To change the in game text size, find cl_hudfont and change it to:

"0" - Tiny
"1" - Small
"2" - Medium


4. Find cl_fog and change it to "0".
5. Find cl_dynamic_xhair and change it to "0".
6. Find cl_particlefx amd change it to "0".
7. Bind a key to "stopsound". Ex. bind "k" "stopsound".
8. The "g" key puts an X marker on your minimap for your team to see.
9. The "L" key zooms in and out of your minimap.
10. Find hud_fastswitch and change it to "1". (This allows you to change weapons faster)
11. bgmvolume "1.000000" will turn on the intro music, setting it to "0" will turn it off.
12. Find fps_max and change it to "101". (This opens your Video Card to its max level)
13. Find net_graph and change it to "3". In game you will see your fps and choke. Set it to "0" to turn net_graph off.

Okay Steam itself takes up a lot of system resources. If you hit Ctrl-Alt-Del and click on Processes in the Task Manager, you will see a list of programs and services that are running. Find Steam.exe and right click on it. Go down to "Set Priority" and you will see that Steam.exe is set to "high" priority. I wonder what genius thought that Steam should be on high priority. The last time I checked, I didn't want to play Steam, I wanted to play DoD. This "high" priority is taking up valuable system resources that we could be using for DoD and having lower ping and higher fps. So we have to find a way to make Steam startup with a "low" priority. And if you have Steam startup every time your computer boots up, this makes it even more of a problem.

First, if you have Steam startup every time you boot-up, you will have to go back to that "msconfig" and uncheck the box next to Steam.exe and reboot. Now that Steam is not loaded, we can set it to startup with a "low" priority:

a. Open notepad or wordpad.
b. Type in “cmd /c start /Low Steam.exe”
c. Save as Steam.bat in C:ProgramFilesValveSteam.
d. Make sure to save it as a .bat file.
c. Go to your desktop and create a new shortcut.
d. Go to C:Program FilesValveSteam and select Steam.bat and click ok.
e. Choose a name for your shortcut and click on Finish.

Now click on the shortcut and it will run and startup Steam with a low priority selection. Hit Ctrl-Alt-Del and click on Processes in the Task Manager. Find Steam.exe and right click on it. Go down to "Set Priority" and you will see that Steam.exe is set to "low" priority. Yeah! We are now smarter than Spock and Albert Einstein!

Now that Steam is set to load on low priority, we must set your Steam connection speed. Right-click on your little black Steam icon in the lower right corner and left-click on “Settings”. Now click on the “Internet” tab and you will see a box under Internet Connection Speed. Click the little down-arrow and select “LAN/T1>1M”. Then click Ok. This will open up your steam internet connection to the max. Now Steam is ready to obey your every command in taking over the world, hehe!

Help for those of you who share computers

I've noticed that some of you share computers, and as such, you have to change your name every time you take turns playing.  There's a much easier way to do that:

Open notepad.  Type in the following:

name "|CoR| whoever*GI*"

Save it as whoever.cfg (make sure it's on "all files" and not "text document") and place it in your dod directory.  Then bind a key to "exec whoever.cfg" -you can do that for however many people share the computer.  And if you can't figure it out, let me know and I'll make the config files for you.

Discipleship/Leadership Structure:

Here is the structural breakdown.
Rank you are in
1.Rank you are responsible for implementing Discipleship/Leadership
2.Rank you are responsible for implementing Discipleship/Leadership

General
1.LtGen & BGen
2.Recruits

LtGen
1.Colonel, LtCol, & Major
2.Recruits

BGen
1.Captain & Lieutenant
2.Recruits

Colonel
1.Sargeant
2.Recruits

Major
1.Corporal
2.Recruits

Captain
1.Specialist
2.Recruits

Lt
1.Private 1st Class
2.Recruits


____________________________________________________________
Suggested Ideas for Discipleship/Leadership:

Methods of Communication:
Forum Private Message
E-Mail
Phone
MSN Messanger
AOL Instant Messanger
ICQ
Ventrilo
etc.

Ideas for Communication:
Encourage members to attend practices and other events.
Ask for prayer requests and pray for them.
Convey latest news and events in the clan and sub-team.
Share your personal testimony.
Give godly advice and wisdon to issues of life.
Share Bible verves.
Encourage Sunday Church attendance.
Give tips on game play.
Help with their admin setup.
Help with troubleshooting issues on thier computer and games.
Share the Gospel of Jesus Christ.
ect.

When to Communicate:
Once a week or bi-weekly.

May the Lord enrichen your life and the ones you mentor.

Updated by Doc 9/13/09 to show the current rank structure.

|CoR| DOD Forum Banners from Game Tracker
|CoR| Christian Gaming www.corclan.com Forum Banner

560×95 DOD Server Image Banner

Code: [Select]

[url=http://www.gametracker.com/server_info/63.209.36.82:27015/][img]http://cache.www.gametracker.com/server_info/63.209.36.82:27015/b_560x95.png[/img][/url]
______________________________________________________

350×20 DOD Server Image Banner

Code: [Select]

[url=http://www.gametracker.com/server_info/63.209.36.82:27015/][img]http://cache.www.gametracker.com/server_info/63.209.36.82:27015/b_350x20_C692108-381007-FFFFFF-000000.png[/img][/url]

Code: [Select]

[url=http://www.gametracker.com/server_info/63.209.36.82:27015/][img]http://cache.www.gametracker.com/server_info/63.209.36.82:27015/b_350x20_CFFAD41-E98100-000000-591F11.png[/img][/url]

Code: [Select]

[url=http://www.gametracker.com/server_info/63.209.36.82:27015/][img]http://cache.www.gametracker.com/server_info/63.209.36.82:27015/b_350x20_C5A6C3E-383F2D-D2E1B5-2E3226.png[/img][/url]

Code: [Select]

[url=http://www.gametracker.com/server_info/63.209.36.82:27015/][img]http://cache.www.gametracker.com/server_info/63.209.36.82:27015/b_350x20_C323957-202743-F19A15-111111.png[/img][/url]

Here's the link for the stats site for the DoD server:
http://gamestats.corclan.com/dod/

You can find the code for embedding a image of your stats in your signature on your player page.  Just select the color you want and then copy the text in the BBCODE textbox to the signature in your forum profile.

Where to buy Day of Defeat

http://www.corclan.com/index.php?option=com_wrapper&Itemid=221

[|CoR| DDogbert]

Another handy bind I use for admin purposes is as follows.

Code: [Select]

bind o "status;condump"

This will print out everyones steam id and save it as a condump text file.  Much easier and faster than typing it in the console.

[|CoR| Adoh]

just a reminder, these binds are for admin use.   
If you wish to make one for a non-admin say,    change the "amx_casy" to "say"  and the same for source.

If you need any help check practice tonight or make a post, we will be happy to help.

[|CoR| Hippie]

Are these key binds done in the config file or from the console? 

[|CoR| Adoh]

hippie,

either will work, I find it easier in console, can check it to make sure it works quickly

[|CoR| DDogbert]

Are these key binds done in the config file or from the console? 

The only reason you would have to do it in your config file would be if you have your config file set to read-only.

[|CoR| Hippie]

The reason I was wondering is this:

If I do it from the console won't I have to rekey it every time I restart the game?

[|CoR| Cool_Hand_Luke]

The reason I was wondering is this:

If I do it from the console won't I have to rekey it every time I restart the game?

Correct, that is why it should be in your config file so that it is permanant.  You will need to set your config file to write, make your changes, then reset it back to read only.

[|CoR| βřàvehëar†]

oh cool! its just like the grapple thing in half life! sweet! oh can clan members use it or just admins?

[|CoR| Punish3r]

Need to get those binded for the next times I'm playing

[Knight_Wing]

oh ok finally i figure this out.... i was asking dark knight but hadnt finished cuz i had to leave... but thanks for reposting and redirecting it... works for me!!!

 

[|CoR| Judah]

Quick question: is this the config file in

c:\Program Files\Steam\config

or the one in

C:\Program Files\Steam\Steamapps\myname\day of defeat\dod....



Thanks!

[|CoR| psyco-elmo]

the correct answer would be #2. you want it in your dod config.

[|CoR| MOONFACE]

I am trying to set an arrow key for amx_vote "mapchange" "yes" "No"
But every time I do it in config the whole line disappears after accept the changes and then close the file.
Any suggestions. All my other binds work, just this one with the arrow keys.

[|CoR| SpiritVII]

I am trying to set an arrow key for amx_vote "mapchange" "yes" "No"
But every time I do it in config the whole line disappears after accept the changes and then close the file.
Any suggestions. All my other binds work, just this one with the arrow keys.

right click your config file -> properties, uncheck "read only", add the bind again, save, right click ->properties, make it read only again. Hope that helps

[|CoR| MOONFACE]

Still not working dont know whats wrong.

[{Apostle}]

ITs not working because... The Console is only reading 2 Quotaion Marks...
all its seeing is amx_vote "mapchange" and it  doesnt have the parameters for the answers so it is Not sending the Question...

Or another problem...

bind k "amx_vote "mapchange" "yes" "no"

Color Coded for Quotation Corolation... Its picking up "amx_vote " as one parameter. " " as 2 others and an onpen Quotation as the last... With no actual command line.
(Someone Correct me if i am wrong)

try this

Code: [Select]

bind <key> amx_vote New_Map? Yes No
With No quotations at all.

God Bless,
Apostle

[OneShot]

just a side note:

sometimes the easiest thing is the problem..

bind "UPARROW"
bind "DOWNARROW"
bind "LEFTARROW"
bind "RIGHTARROW"

those are the arrow keys as reconized by the config..

Code: [Select]

ex.
1) bind "UPARROW" "amx_vote MapChange? Yes No"

2) bind "DOWNARROW" "amx_vote" "Map Change?" "Yes" "No"

3) bind "RIGHTARROW" "amx_vote Map Change?" Yes No

my best bet would be #2

[{Apostle}]

#2 and #3 wont work...

#1 is best option

#2 is sending in the command amx_vote with No parameters

#3 is sending in the command amx_vote with the parameter Mapchange? (amx_vote neews at least 3 parameters)

[|CoR| MOONFACE]

#2 and #3 wont work...

#1 is best option

#2 is sending in the command amx_vote with No parameters

#3 is sending in the command amx_vote with the parameter Mapchange? (amx_vote neews at least 3 parameters)

DING DING DING!! Winna winna chicken dinnah!!!

cmeah yung mayne gitcha self a prize
#1 works purrrfectly!!

(bowing low) you are da man Apostle

MOON

[|CoR| DDogbert]

Would you guys stop spamming the sticky.

FYI...I cleaned out the spam to try and keep this clean

[|CoR| Dr. Wiggy]

Our current server rules 9/13/09:

http://www.corclan.com/gameassets/dod/motd/dod1motd.html


I have compiled most of *GI*'s stickies in Luke's first post today, Stinker said I could 'clean up' the *GI* section a bit.

God Bless,
Doc

[|CoR| Dr. Wiggy]

Something I have been sorta working on for a while, and no its not a complete list, so if you have any that can be fit in let me know, or post here.

This is a list of maps that are played on DOD that coincide with actual battles fought in WWII.  THese also go with a date and place they were fought.

I think it would be neat if one practive that we could start in order, and if allies win, go to the next map in order, if Axis hold, go back to previous map.   Yes some of these have time limits, others don't.  Might even have to do best 2 out of three as some are very quick maps.

dod_avalanche - Italy, September 9th 1943
dod_anzio - Italy, January 22nd 1944
dod_donner - France, July 18th 1944
dod_flash - Netherlands - German Border, October 13th 1944
dod_glider - France, June 6th, 1944
dod_charlie - France, June 6th 1944
dod_merderet - France, June 13th 1944
dod_jagd - France, June 13 - 14th 1944
dod_chemillie - Cotentin Peninsula, Normandy, France, June 25th 1944
dod_cherbourg, Northern France, June 21st-25th
dod_caen - France, 8 - 9th July 1944
dod_escape - Holland, September 17th, 1944
dod_kraftstoff - Allied Teritory (French-German Border), October 4th 1944,
dod_forest - Germany, 2nd November 1944
dod_kalt - Western Front, December 15th 1944
dod_zalec - Belgium, January 15th 1945
dod_vicenza - Italy, 25th April, 1945

Also, I have information if you might be intrested in any of these battles on what took place.  If you want to know about one.  Make a new topic and post the map/battle in question, I'll get you the information I have.  These more than what I have out there about them.   Please keep this thread only for additions into the timeline of maps that we have on the server.

There have been a couple request on information about these battles.

Below is a brief description on these battles.

Look in the monthly newsletter for even more detailed information on these battles and what effect they had on the war.

dod_avalance:
Operation Avalanche - the primary invasion force of mainland Italy. Allied forces, following a successful landing at  Salerno on 9th September, faced a fierce German counterattack in the surrounding hill towns. All invasion objectives were abandoned in favour of holding the landing zone through the fighting that ensued over 13 - 14th September.

dod_anzio:
Not to be outdone by the recent advance into Poland by Soviet forces, the Allies launch another landing into mainland Italy, hoping to break the back of the German resistance in the North of the country.

dod_donner:
The Allied offensive continues at a painfully slow pace, with the invading force still attempting to secure vital road junctions and towns, weeks behind the planned schedule. Allied forces enter the town of Sainte-Lo, securing the town will secure key road junctions leading to Caen and Carentan.

dod_flash:
On the back of the failed operation Market Garden. the British 8th Corps launch a new offensive - a thrust towards the town of Venlo, and then the German border. Many small villages, and a significant, determined, German force lie in their path.


dod_glider:
American paratroopers drop behind the main German defensive lines, early in the morning before the Normandy Landings. Their objectives are numerous - destroy enemy gun emplacements, cut communication lines, capture key roads, bridges and villages. All the objectives combine into a single aim - to facilitate a rapid as possible expansion from the beaches.

dod_charlie:
D-Day - Operation Overlord - the largest sea-borne invasion force in history land on 5 beaches on the bleak Normandy coastline. Some landings go ahead virtually unopposed, others suffer heavy losses, with the unrelenting sea consuming tanks and men, and the well prepared German defenders exacting a heavy price on the landing troops.

dod_merderet:
The small town of Ramelle, a fictional scenario. With it's key bridge over the Merderet river, became key objective for both the Allied and German forces during the post D-Day weeks. The town, captured by American paratroopers on and shortly after D-Day, provided a key link between Omaha and Utah beaches. For the German forces, the bridge would allow them to flood the Contentin Peninsula with armour and troops, preventing the Allies from taking the deepwater port of Cherbourg.

dod_jagd:
Advancing through the Normandy countryside towards there post D-Day objectives, the British forces are caught unawares in the town of Viller-bocage, close to Caen. A single Tiger knocks out dozens of Allied tanks, half-tracks and armoured vehicles before it is disabled, and Panzershrek teams have been sighted in the town, intent on destroying the already mauled remnants of the British 22nd Armoured Brigade.

dod_chemillie:
Elements of the US 1st Army advance into the suburbs of Cherbourg. Heavily bombed by Allied aircraft, much of the industrial area of the city lies in ruins. Capture of the city, and its deepwater port, are vital to the sucess of Operations in Normandy - the makeshift docks established on the D-Day beaches will be unable to deal with the shear volume of men, vehicles and supplies that will be needed.

dod_caen:
Following the stalemate that was the outcome of Operation Epsom (a plan to encircle the occupied city of Caen), British and Canadian forces launched a full-scale attack on the besieged city itself. A massive aerial bombardment was launched, which raised the once grand city, to the ground. German defenders hung on bitterly, making the Allies fight to the death for every ruin and pile of rubble.

dod_escape:
General Montgomery's bold plan to advance the Allies across the Rhine, Operation Market Garden, begins. Elements of the 82nd Airbourne tasked with securing the bridges at Grave and Nijmegen, land in their dropzones. The bridge across the River Maas at Grave, is assaulted by a small group of paratroopers, and secured intact. The rest of the operation does not fair so well...

dod_kraftstoff:
Having broken through the Siegfried Line a few days prior, elements of the 1st US Army find themselves at the sharp end of a German counterattack.

dod_forest:
American troops, having broken through the Siefried Line, continue their push into Germany. The American's next offensive was to take the town of Schmidt. Bad weather meant many of the attacking divisions were put on hold, however the orders never reached the American 28th Division, who, alone, launched an offensive into to Germany along a front stretching over 150 miles. The American attack to take Schmidt would have to pass through the Hurtgen forest - a maze of entrenched German positions, bunkers, pillboxes and booby-traps.

dod_kalt:
The town of Kalt, like so many other towns along and just inside the German border, offered stiff resistance to the advancing Allies. Little did the American troops know, this would be the first and last they saw of the German homeland for many months. The following day, Germany launched a massive offensive in the Ardennes Forest, and the Battle of the Bulge began ...

dod_zalec:
The Battle of the Bulge is almost won. American troops reach the Belgium town of Houffalize, cutting off the remaining German forces in the Ardennes. Regular forces, accompanied by troops with specialist Anti-Tank bazookas, take the town and neutralise any remaining German armour.

dod_vicenza:
The British and American advance through northern Italy is close to turning into a rout. The few remain armoured units offer some resistance, however German infantry are surrendering in large numbers, and the fall of Italy seems close.

Using the voice command "negative" as a response to a question or order is NOT against our rules.

Using the voice command "negative" as a 'put down' after a kill is rude, disrespectful and has already been discussed by ALL of the Officers of CoR and is considered to be a punishable offence. How you are punished, will very on a case by case basis.

Any CoR member who violates this rule is subject to punishment from their senior ranking piers (Sgt, Capt, Col, Gen whoever that may be)

This topic has already been throughly discussed and until further notice is not questionable.

Thank you all for your input, and please,
have a nice day.
 

Merged another two topics.

God Bless,
Doc