COD Modding & Mapping Wiki - User contributions [en]

Call of Duty 4: Custom Textures

2009-05-05T22:09:57Z

Novemberdobby:

[[Category:Call of Duty 4]]
[[Category:Modtools]]
[[Category:Radiant]]
[[Category:Advanced Editing]]
{{warning_forpro}}
[[Image:Nutshell.png]] This tutorial will show you how to add a new custom texture to the game, to be used in Radiant.
 
''By NovemberDobby''
[[Image:warning.png]] Custom textures will show as white unless you are running a mod, as textures must be stored in an IWD archive.
[[Image:rgn_warning.png|right]]
The game won't read custom IWD's at all unless a mod is running.

Note: Custom textures will show as white unless you are running a mod, as textures must be stored in an IWD archive. COD4 won't read custom IWD's at all unless a mod is running.

First of all, you'll need a texture file. This can be a .dds, .tga, or .jpg image - no other extensions will work with the converter.

Open Asset Manager through the Cod4CompileTools, or by finding it in COD4\bin\asset_manager.exe.

In the list box at the top left, select 'material', and click 'New Entry'. Pick a relevant name for the material, and make sure there are no spaces in it.

Set the first four settings at the top of the options to:

materialType: world phong

sort: <default>*

surfaceType: whatever you want, this will determine how bullets hit the material. Be sure to change it from 'error'.

usage: this can be anything, but it'll help you sort the texture into a group with similar other materials in Radiant.

In the 'Locales' section, pick one or more locales to access the texture from. Picking an appropriate locale is not vitally important, but make sure you pick at least one so you can find it in Radiant later.

In the 'Color Map' option section, click the ellipses (...) button on the right of the text box. Navigate to your dds/jpg/tga texture and open it. This should be somewhere inside a sub-directory of COD4, as Asset Manager won't let you use one from any other location.

If you have a Normal Map (AKA a bumpmap) for your texture, click the ellipses next to the Normal Map box, and navigate to that file. It must be in an uncompressed RGB format, such as .tga.

Go to File>Save, and put the GDT file in \Call of Duty 4\source_data. Give it any name, bearing in mind you'll have to open this file again if you want to change/reconvert this texture.

Go to PC Convert>Current Asset only, or hit F10. Choosing to convert all assets would convert every single stock asset that came with the mod tools, which can take quite a while and cause problems if interrupted.

'''You should see something like this:'''

[[Image:custom_669.png]]

[[Image:warning.png]] But if there are any errors, the compiler will warn you.

It will only re-convert if you have changed the input texture filename, changed the texture itself, or any other material option in Asset Manager.

You should now be able to find your texture in Radiant, by going to textures>locales and selecting your chosen locales, or by using the material/surfaceType.

If your texture appears gritty at a distance, then open up the image editing program you used to save it in, and make sure Mipmaps are generated (and reconvert).

Distortion textures can be added by setting the materialType to distortion, and finding a colour map.

-NovemberDobby

Call of Duty 4: Custom Textures

2009-05-05T22:09:30Z

Novemberdobby: updated a bit

Call of Duty 5: Multiplayer Perks

2008-11-21T22:37:23Z

Novemberdobby:

[[Category:Call of Duty 5]]
[[Category:Perks]]
 [[Image:Nutshell.png]] All of the perks that are in the World at War game:

== Perk Set 1 ==

* Special Grenades x3
* Satchel Charge x2
* M9A1 Bazooka x2
* Bomb Squad
* Bouncing Betty x2 (similar to claymores)
* Bandolier
* Primary Grenades x2
* M2 Flamethrower

[[Image:perks_32.png]][[Image:perks_18.png]][[Image:perks_5.png]][[Image:perks_11.png]][[Image:perks_26.png]][[Image:perks_3.png]][[Image:perks_20.png]][[Image:perks_33.png]]

== Perk Set 2 ==

* Stopping Power
* Fireworks (explosives cause more damage)
* Flak Jacket (decreases damage taken by explosives)
* Gas Mask
* Juggernaut
* Camouflage
* Sleight of Hand
* Shades (decreases intensity of signal flares)
* Double Tap
* Overkill

[[Image:perks_27.png]][[Image:perks_28.png]][[Image:perks_29.png]][[Image:perks_4.png]][[Image:perks_1.png]][[Image:perks_13.png]][[Image:perks_12.png]][[Image:perks_25.png]][[Image:perks_16.png]][[Image:perks_8.png]]

== Perk Set 3 ==

* Deep Impact
* Extreme Conditioning
* Steady Aim
* Toss Back (resets fuse on tossing back enemy grenade)
* Second Chance (ability to revive allies)
* Martyrdom
* Fireproof
* Dead Silence
* Iron Lungs
* Reconnaissance (shows artillery and tanks on map)

[[Image:perks_2.png]][[Image:perks_23.png]][[Image:perks_15.png]][[Image:perks_24.png]][[Image:perks_30.png]][[Image:perks_21.png]][[Image:perks_31.png]][[Image:perks_19.png]][[Image:perks_7.png]]

== Vehicle Perk ==

* Water Cooler (less overheat on tank machine guns)
* Greased Bearings (quicker turret rotational speed)
* Ordinance Training (faster tank main turret reloading)
* Leadfoot (faster moving tanks)
* Coaxial Machine Gun (driver gets a machine gun too)

[[Image:perks_17.png]][[Image:perks_22.png]][[Image:perks_6.png]][[Image:perks_14.png]][[Image:perks_10.png]]

==For modders==

''In script/stringtables names of the perks''

<pre>
specialty_bulletaccuracy :Steady Aim
specialty_doublegrenade :Primary grenade x2
specialty_fireproof :Reduce the effects of the flamethrower
specialty_greased_bearings :Speed up the rate of rotation of tank turrets
specialty_longersprint :Sprint for longer
specialty_pistoldeath :Last stand
specialty_shades :Reduces the effects of flares/stun grenades
specialty_weapon_betty :Bouncing Betty x2
specialty_bulletdamage :Stopping Power
specialty_explosivedamage :Fireworks - Increase explosive damage
specialty_flak_jacket :Reduce damage taken from explosives
specialty_grenadepulldeath :Martyrdom
specialty_quieter :Dead Silence
specialty_specialgrenade :Specials Grenades x3
specialty_weapon_flamethrower :M2 Flamethrower
specialty_armorvest :Juggernaut
specialty_bulletpenetration :Deep Impact
specialty_extraammo :Bandolier
specialty_gas_mask :Reduces the effects of gas grenade attacks
specialty_holdbreath :Iron lungs
specialty_ordinance :Faster firing main tank gun
specialty_recon :Reconnaissance (shows artillery and tanks on map)
specialty_twoprimaries :Overkill
specialty_weapon_rpg :2x Rocket Propelled Grenades
specialty_boost :Coaxial Machine Gun(driver gets a machine gun too)
specialty_detectexplosives :Bomb Squad
specialty_fastreload :Sleight of hand (faster reload)
specialty_gpsjammer :Conceal yourself from radar
specialty_leadfoot :Increase the drive speed of tanks
specialty_pin_back :Toss back - resets timer on throwing back grenades
specialty_rof :Double tap
specialty_water_cooled :Decreases tank MG overheat rate
specialty_weapon_satchel :Satchel Charges x2
</pre>

''Some comments from _class.gsc''

<pre>
"perk_bulletDamage", "40" // increased bullet damage by this %
"perk_fireproof", "55" // reduced flame damage by this %
"perk_armorVest", "75" // multipy damage by this %
"perk_explosiveDamage", "25" // increased explosive damage by this %
"perk_flakJacket", "75" // explosive damage is this % of original
"perk_flakJacketMaxDamage", "75" // max damage caused by grenade in %
</pre>

--[[User:Zeroy|Zeroy.]] 12:20, 13 November 2008 (UTC)

Call of Duty 5: Create Custom Textures

2008-11-21T14:28:12Z

Novemberdobby: specular detail thing

[[Image:rgn_warning.png|right]]
===Export from Photoshop===
You can use any program that will save an image as either a .tga or .dds, Photoshop is the industry standard so I'll start in there.

If your using Photoshop then download this plug in and install:

*[http://developer.nvidia.com/object/photoshop_dds_plugins.html Nvidia Plugin]
*[http://ati.amd.com/developer/sdk/radeonsdk/html/tools/toolsplugins.html ATI Normal map generators]

[[Image:Information.png]] The ATI Normal map generators is the easiest to use, it converts premade .tga files.
You can use your color map or a bump map.
The Nvidia plugin can do normal maps too in the "Normal map settings" button in the picture.

'''1.''' First resize your image as (n^2)x(n^2) and "n" can be any number.

IE: (8^2)x(16^2) = 64 x 256 pixels, this would be useful for trim.

*Some other sizes: 64 x 64, 512 x 512, 1024 x 512, 256 x 128, ect...

'''2.''' Save as either .tga or .dds.

*TGA is only useful for opaque textures, this is easiest to use as there are no options.
*DDS can be used for textures that have transparency like windows.
**DXT1 has only 1 bit alpha, like an on / off switch. There is no fading and a pixel is either opaque or see through.
**DXT5 has the most detailed alpha so fading between opaque and transparent looks good, good for dirty glass.
**DXT3 has a less detailed alpha channel so its good for fading but only if there's a little of it.

'''3.''' Save into your raw/images folder.
*I suggest you save a copy elsewhere too but when we go to Asset Manager it will only consider images in the "raw/images" folder.
 
[[Image:teximport1.jpg]] 

===Asset Manager===

'''1.''' Create the Material

*Once you open asset manager there is a menu to the left and select "Material".
*Once "material" is highlighted then click on New Entry and fill in the name of your texture.
*Click on OK and your material should show up like in the picture.

[[Image:teximport2.jpg]]

'''2.''' Filling in the rest of the information.

*materialType - Select "world phong" for a texture.
*surfaceType - Select the proper surface type to use stock settings for the type of material.
**Stock settings include impact effects, sounds, and penetration ability.
*sort - Leave as "<default>*".
*usage - Select the intended use for your texture.
*Locales - Intended theme or location for your texture.
*Framebuffer operations - Leave alone unless you are an advanced user.
**If creating an alpha blending texture then change "blendFunc" to "blend".
*Color Map - This is the image file that you created, this is also what the player will see.
*Normal Map - This section can accept a bump map or normal map to show height.
**A bump map is a Grey scale image of your texture showing height.
***Black is low, white is high, values in between are relative height.
**A normal map is provided by converting a bump map with a plug in.
***while most of your image may be purple there are different colors that represent height.
**A bump map only shows height in an image, a normal map shows height and direction of a bump.
*Detail Normal Map - This is the same as a normal map but only shows when the player is close to the texture, usually only small bumps or holes.
*Specular color map - Same rules as a bump map but white is shiny and black is no shine. This will only be visible if r_specular is set to 1.
*Cosine power map - Adjustments to Specular color map.

[[Image:teximport3.jpg]]

[[Image:teximport4.jpg]]

'''3.''' Convert your file.

*Once everything is setup go to "PC Convert -> Current Assets Only"
**You can use the convert all option but any errors may be lost in scrolling log.
*Once successful you will have 3 files to keep in mind when packing your map or mod.
**raw/materials/texturename <no file type>
**raw/material_properties/texturename <no file type>
**raw/images/texturename.iwi

===Viewing===
To be sure your custom texture has been successfully imported, you can open up radiant and find your texture setup by the filters you specified. If you can view it in radiant then you will be able to use it anywhere. If you created a model phong then you can view your texture on your model in asset viewer.

Sources: [http://wiki.treyarch.com/wiki/Creating_A_Custom_Texture Treyarch's Wiki]

[[Category:Modding]]
[[Category:Mapping]]
[[Category:Call of Duty 5]]
[[Category:Textures]]

Call of Duty 5: Modding Files

2008-11-13T21:56:32Z

Novemberdobby:

Thanks to Gagarin & Novemberdobby, here are the files rip from Call Of Duty : World at War version 1.1

[[Image:Data.png]] [http://wiki.modsrepository.com/codww_files/codww_fullrip2.zip Gagarin's Rip - Without Sounds, 5Mb] 
[[Image:Data.png]] [http://wiki.modsrepository.com/codww_files/codww_fullrip.zip Dobby's Rip - 2.8Mb]

----

Thanks to NovemberDobby, here are String tables missing from rip:

<pre>
rankTable.csv
rankicontable.csv
statsTable.csv
classtable.csv
offline_classtable.csv
attachmentTable.csv
</pre>

[[Image:Data.png]] [http://wiki.modsrepository.com/codww_files/codww_missingcsvs.zip HERE]
[[Category:Call of Duty 5]]
[[Category:Modding]]
[[Category:Technical Reference]]

Call of Duty 5: Multiplayer Perks

2008-11-08T14:39:10Z

Novemberdobby:

[[Category:Call of Duty 5]]
[[Category:Perks]]
 [[Image:Nutshell.png]] COD has announced all of the perks that will be in the World at War game:

== Perk Set 1 ==

* Special Grenades x3
* Satchel Charge x2
* M9A1 Bazooka x2
* Bomb Squad
* Bouncing Betty x2 (similar to claymores)
* Bandolier
* Primary Grenades x2
* M2 Flamethrower

== Perk Set 2 ==

* Stopping Power
* Fireworks (explosives cause more damage)
* Flak Jacket (decreases damage taken by explosives)
* Gas Mask
* Juggernaut
* Camouflage
* Sleight of Hand
* Shades (decreases intensity of signal flares)
* Double Tap
* Overkill

== Perk Set 3 ==

* Deep Impact
* Extreme Conditioning
* Steady Aim
* Toss Back (resets fuse on tossing back enemy grenade)
* Second Chance (ability to revive allies)
* Martyrdom
* Fireproof
* Dead Silence
* Iron Lungs
* Reconnaissance (shows artillery and tanks on map)

== Vehicle Perk ==

* Water Cooler (less overheat on tank machine guns)
* Greased Bearings (quicker turret rotational speed)
* Ordinance Training (faster tank main turret reloading)
* Leadfoot (faster moving tanks)
* Coaxial Machine Gun (driver gets a machine gun too)

''[http://www.worthplaying.com/article.php?sid=56148 Sources]''

Call of Duty 4: Tips

2008-11-08T14:33:00Z

Novemberdobby:

== Common Errors & Solutions ==

*Help! My map is shining all red!

You need to add [Call of Duty 4: Reflection Probes|Reflection Probes].

*Help! My guns and random stuff are shining rainbow!

First stop smokin the good stuff, then create a [Call of Duty 4: Gridfile|Grid File].

*While compiling the BSP, I get an error that .d3dbsp cannot be loaded!:

The editor automatically tries to load a previous version of a compiled map if it runs into errors while compiling. If for some reason the previously compiled files are missing, it gives that error. If you scroll up the DOS window, i'm sure another error will display itself, and that's the real reason you aren't compiling.

*I've added destructible cars to my map, and now when compiling reflections I get "CANNOT SWITCH ON UNDEFINED":

[http://www.modsonline.com/Tutorials-read-457.html Fix Here].

*While compiling the BSP, I get errors about lights leaking or *******Leaking*******

This happens when your skybox is not completely closed and the player has the possibility to see the infinity! Close the compile, go to the editor, and go to File >> PointFile. It will show you where it's leaking. This can also be the cause of Portals not being in an enclosed space. Learn about portals and re-implement! Links above!

*Surface partially floating or needs to be aligned

You can, most of the time ignore this warning but to be sure, load the map in Radiant and use the Error File to check that patches are properlly alighend toghether.

*WARNING: Attempting to meld model, but root part 'j_spine4' of model 'blah blah' not found in model 'blah blah' or any of its descendant.

[http://www.mycallofduty.com/modules.php?name=Forums&file=viewtopic&t=1626 Fix thread here].

Basically, add "include,mptypes_woodland" into your map CSV. "include,mptypes_desert" if you are using desert style players. Update zone file and build new FF and map works fine with extreme and ace and awe.

*Screen is completely red (can't see anything) or red FX signs over bodies

Read the above and do it.

== Useful commands ==

In Console:

If mp_backlot automatically loads when you try to run your map, type in these commands to load into your map even with errors, allowing you to shift+tilde (~) and see what is wrong.

/sv_mapRotation ""
/sv_mapRotationCurrent ""
/devmap [yourmapname]
Change to any map without dev mode.

/map [themap]
Third person view (first load with /devmap [mapname])

/cg_thirdperson 1

More Usefull ServerCommands:

''only available in devmap mode.''

\give airstrike_mp
\give helicopter_mp
\give radar_mp

In CoD4Tools Custom Command Line Options:

<pre>+set scr_game_matchstarttime 0 +set scr_game_playerwaittime 0 +set fs_game mods/modWarfare</pre>
This one line takes off the wait timers at the beginning of the game when you load in, as well as loads you into ModWarfare from the start.

Call of Duty 4: Console usage

2008-11-08T14:23:45Z

Novemberdobby:

[[Category:Modtools]]
[[Category:Call of Duty 4]]
[[Image:Information.png]] To open the console, simply press the tilde key ('~') while you are in-game, this should bring up a minimal console. To get a full console, to see any game output, press Shift + tilde (Shift + '~'). The tilde key is above your tab key, normally.

If nothing happens when you press any of the above key combinations, you don't have the console enabled. To enable it, open CoD4 multiplayer, then go to Options -> Game Options -> Enable Console and switch it to Yes.

The variable 'monkeytoy'can be set to 1 to disable the console, or 0 to allow it.

==Commands==
I have a small list of the most useful commands [http://daevius.com/archive/call-of-duty-4/commands Here]

You can get a full list, by entering '/cmdlist' in the console.

Call of Duty 4: Console usage

2008-11-08T14:22:33Z

Novemberdobby: monkeytoy

[[Category:Modtools]]
[[Category:Call of Duty 4]]
[[Image:Information.png]] To open the console, simply press the tilde key ('~') while you are in-game, this should bring up a minimal console. To get a full console, to see any game output, press Shift + tilde (Shift + '~'). The tilde key is above your tab key, normally.

If nothing happens when you press any of the above key combinations, you don't have the console enabled. To enable it, open CoD4 multiplayer, then go to Options -> Game Options -> Enable Console and switch it to Yes.

The variable 'monkeytoy'can be set to 1 to disable the console, or 0 to allow it.

==Commands==
I have a small list of the most usable commands [http://daevius.com/archive/call-of-duty-4/commands Here]

You can get a full list, by entering '/cmdlist' in the console.

Call of Duty 4: Equipment

2008-11-08T14:10:01Z

Novemberdobby: lined up images better

[[Category:Call of Duty 4]]
[[Category:Weapons]]
[[Category:Technical Reference]]
[[Image:Nutshell.png]] In depth CoD4 Equipment stats.

Welcome to the equipment section of CoD4 Central. Here you will find information regarding the explosives and other equipment in CoD4 such as grenades, and some stats/information about them.

Note: All grenades do a small amount of damage to enemies if they hit before exploding, just as if you had thrown a rock at your opponent. You can use this to kill wounded opponents and fulfill some of the Humiliation challenges unlocked at ranks 47 and 48! It's also really funny, so try it if the opportunity arises.

==Frag Grenades==
[[Image:cod4frag.jpg|right]]
When you press the grenade key, you'll lob a grenade with a 5-second fuse on it. Unless you want to flush enemies out of hiding or get the nade lobbed back at you, this isn't a good idea. Instead, hold the key down. Your crosshairs will start pulsing, and the grenade will explode at the fifth pulse. For best results, lob the grenade at your opponent at the third or fourth pulse (fourth if they're close) and they won't have time to react. You can throw any frag grenade you're standing on by hitting the grenade key. This takes a second or two, so unless you have no other choice, run instead of going for the throw. Also, you can kill yourself by throwing a friend's grenade even if friendly fire is off.

Damage: 300-75 / 15 Direct Impact
Range: 0-256
Fuse/Detonator: 5 seconds / 2.5 Martdrom
Other: "Cooking", synchronized, beats to seconds

== Flashbang Grenades ==
[[Image:cod4flash.jpg|right]]
Has no timer. Sets off a loud bang and a bright flash about two seconds after it is thrown, blinding anyone facing it (including you but not your teammates if FF is off) for several seconds. Blinded players can still move and fire freely, so be careful of wild fire when you flash and enter an area.

Damage: 0 / 15 Direct Impact
Range: 200-800
Fuse/Detonator: 1 second
Other: Detonates at exactly one second

== Stun Grenades ==
[[Image:cod4stun.jpg|right]]
Has no timer; goes off two seconds after thrown. Momentarily blinds those in its radius and slows their motion and turning for several seconds. You don't have to be facing it for it to stun you. Ideally you should use this on enemies with their backs to you so you can take a leisurely headshot or backstab.

Damage: 40-1 / 15 Direct Impact
Range: 0-512
Fuse/Detonator: 1 second
Other: Only detonates after touching ground

== Smoke Grenades ==
[[Image:cod4smoke.jpg|right]]
The smoke grenades in CoD4 are very effective when compared to other fps games. After tossing one, you will notice the area really becomes impossible to see, and therefore proving great cover for getting across an area with snipers, or campers. It is also great for taking over an objective. Toss one down and move around a bit in the smoke, the enemy won't be able to spot you.

Damage: 0 / 15 Direct Impact
Range: 200-800

== Knife ==
[[Image:cod4knife.jpg|right]]
Hit melee to whip out the knife regardless of how impossible it is to carry your potentially heavy gun in one hand and slash quickly and effectively with the other. The combat knife one-shot kills any target, unless you're on a feedback FF server where the damage you inflict on friendlies goes to you instead. In that case, you take damage to within one point of death. I'm not sure on how the game decides to have you stab or slash someone... perhaps you slash if you're strafing. Slashing is rather quick, whereas stabbing has a recovery time of a couple seconds, which can be perilous if you miss your target but the stab animation happens anyway.

Damage: 400
Range: 0-20
Other: Great for quiet kills

== Camouflage ==
[[Image:cod4cam.jpg|right]]
Paint your gun! In some cases having the proper camo on your gun will actually disguise you better, but don't sweat this too much because you can't change camo in the middle of a round. Mainly you use camo to make your gun look cool and for prestige. All primary weapons that you have unlocked automatically come with desert and woodlands camo. The following camos are unlocked for all weapons by completing their respective Expert Challenges (headshot quotas):

*Digital Camouflage: (25 headshots): gray, blocky micropattern camo good in concrete-filled maps like Countdown, Pipeline and Vacant, as well as Wet Work.

*Blue Tiger Camouflage: (75 headshots): blue and dark gray tigerstriped camo, most likely to blend in in Wet Work and the concrete maps.

*Red Tiger Camouflage: (150 headshots): red and dark gray tigerstriped camo.

*Gold: Available for the AK-47, Mini-Uzi, M60E4, M1014, and Dragunov when you complete all Marksman and Expert challenges for every gun in their respective classes. Shiny and easily noticeable by everyone, but you should be proud to show it off!

Call of Duty 5: Perks Icons

2008-11-08T13:52:11Z

Novemberdobby:

[[Image:codww_perks1.png]] [[Image:codww_perks2.png]] 

specialty_bulletaccuracy: Steady Aim 
specialty_doublegrenade: Primary grenade x 2 
specialty_fireproof: Reduce the effects of the flamethrower 
specialty_greased_bearings: Speed up the rotational speed of a tank's turret 
specialty_longersprint: Sprint for longer 
specialty_pistoldeath: Last stand 
specialty_shades: Reduces the effects of flares/stun grenades 
specialty_weapon_betty: Bouncing Betty x 2 
specialty_bulletdamage: Stopping Power 
specialty_explosivedamage: Fireworks - like sonic boom in COD4 
specialty_flak_jacket: Reduce damage taken from explosives 
specialty_grenadepulldeath: Martyrdom 
specialty_quieter: Dead Silence 
specialty_specialgrenade: Specials Grenades x 3 
specialty_weapon_flamethrower: M2 Flamethrower 
specialty_armorvest: Juggernaut 
specialty_bulletpenetration: Deep Impact 
specialty_extraammo: Bandolier 
specialty_gas_mask: Reduces the effects of gas grenade attacks 
specialty_holdbreath: Iron lungs 
specialty_ordinance: Faster firing main tank gun 
specialty_recon: ? 
specialty_twoprimaries: Overkill 
specialty_weapon_rpg: 2 x Rocket Propelled Grenades 
specialty_boost: ? 
specialty_detectexplosives: Bomb Squad 
specialty_fastreload: Sleight of hand 
specialty_gpsjammer: Conceal yourself from radar 
specialty_leadfoot: Increase tank's drive speed 
specialty_pin_back: Toss back - resets timer on throwing back grenades 
specialty_rof: Double tap 
specialty_water_cooled: Slows the overheating of tank guns 
specialty_weapon_satchel: Satchel Charges x 2

Call of Duty 5: Perks Icons

2008-11-08T13:51:34Z

Novemberdobby: added perk names/descriptions

Call of Duty 4: Attachments

2008-11-08T13:16:08Z

Novemberdobby: moved images to line up better

[[Category:Call of Duty 4]]
[[Category:Weapons]]
[[Category:Technical Reference]]
[[Image:Nutshell.png]] These items can be attached to the specified weapon classes with the exceptions of the Desert Eagle and MP44. All equipment except for the grenade launcher and pistol silencer must be unlocked for each individual weapon by completing the Marksman (kill quota) challenges for that weapon. The kills needed to unlock the equipment are listed next to the equipment names.

== Grenade Launcher ==
[[Image:cod4noob.jpg|right]]
(assault rifles) (replaces Tier One perk): The n00b tube! Equip this attachment with 5 to bring up the grenade reticule, and fire. The impact grenade won't arm until a second or two after leaving the barrel, so aim for at least medium-distance targets. The exception is impact kills. If you can hit someone up close with an undetonated grenade, they die instantly! The kill icon is rather amusing

Damage: 155-25 / 135 Direct Impact
Range: 0-300
Fuse/Detonator: 375 Range To Activate
Other: Will not detonate under 375 range

== Silencer ==
[[Image:cod4silencer.jpg|right]]
(assault rifles 75, SMGs 75, pistols): A silenced weapon suffers a 2+ penalty to range and an unspecified minor penalty to damage, but when fired it won't appear on enemy radar. I believe the silencer reduces recoil somewhat as well. Use if you don't want to be detected as easily.

Damage: Minor Penalty
Range: 2+ Penalty
Other: Allows to player to go undetected, but can still be seen by UAV if not using UAV jammer

== Red Dot Sight ==
[[Image:cod4reddot.jpg|right]]
(assault rifles 25, SMGs 25, LMGs 25, shotguns 25): Replaces your weapon's iron sights with a battery-powered laser red dot sight. If you have trouble lining up shots easily with the iron sights, switch to the red dot. The laser dot will obscure your target at long range, but it's bright and easy to aim quickly. I always use this if I don't need any other attachment for my primary weapon.

Type: Precision Reflex Sight
Other: Great attachment for any weapon that can use it. Allows the use of perk 1, unlike some other attachments.

== Grip ==
[[Image:cod4grip.jpg|right]]
(LMGs 75, shotguns 75) (replaces Tier One perk): Increases weapon accuracy by 3 and therefore decreases recoil. A considerable benefit for high-recoil weapons if you don't mind losing the Tier One perk; not really necessary for the relatively low-recoil SAW LMG.

Pro: +3 Accuracy
Con: Cannot use perk 1.
Other: This is a great attachment for the M60. The M60 has the most powerful shot out of all of the LMGs,
but has a problem with recoil and not being so accurate. If you put grip, stopping power and deep impact, the M60
turns into a monster if played correctly.

== ACOG Scope ==
[[Image:cod4acog.jpg|right]]
(assault rifles 150, SMGs 150, LMGs 150, sniper rifles 100) Advanced Combat Optical Gunsight. A telescopic sight intermediate between the iron sight/red dot zoom and the sniper scope zoom, with a reticule illuminated by radioactive tritium. Decreases accuracy by 1 and increases range by 2+. Use with fairly accurate weapons that you prefer to use at long range if you can't line up or reach enemies with the iron/red dot sights.

Accuracy: -1
Range: +2

Call of Duty 5: Beta Server Config

2008-11-08T13:12:12Z

Novemberdobby:

[[Category:Call of Duty 5 Beta]]
[[Category:Server Help]]
''By Bullet-Worm and Zeroy''

== Port Forwarding ==

In order to run your own server and open it up to internet users, you need to do some port forwarding in your Router. ''The ports to forwards are as follow:''

UDP 20800
UDP 20810
UDP 28960-28970

For a detailed How-to setup port forwarding on your router, see [http://www.portforward.com/english/routers/port_forwarding/routerindex.htm Portforward.com]

[[Image:Warning.png]] Make sure your Windows Firewall has either added rules for those ports or/and CoDWaWbeta.exe is unblocked from it!

== Allowed Gametypes ==

{| border=1 cellpadding=0 cellspacing=0 width=369
|- height=20 style='height:15.0pt'
| height=20 class=xl6615909 width=77 style='height:15.0pt;width:58pt' |  
| class=xl6415909 width=72 style='border-left:none;width:54pt' | mp_castle
| class=xl6415909 width=110 style='border-left:none;width:83pt' | mp_makin
| class=xl6415909 width=110 style='border-left:none;width:83pt' | mp_roundhouse
|- height=20 style='height:15.0pt'
| height=20 class=xl6315909 style='height:15.0pt;border-top:none' | Gametypes
| class=xl6315909 style='border-top:none;border-left:none' |  
| class=xl6315909 style='border-top:none;border-left:none' |  
| class=xl6315909 style='border-top:none;border-left:none' |  
|- height=20 style='height:15.0pt'
| height=20 class=xl6315909 style='height:15.0pt;border-top:none' | DM
| class=xl6515909 style='border-top:none;border-left:none' | Yes
| class=xl6515909 style='border-top:none;border-left:none' | Yes
| class=xl6515909 style='border-top:none;border-left:none' | Yes
|- height=20 style='height:15.0pt'
| height=20 class=xl6315909 style='height:15.0pt;border-top:none' | TWAR
| class=xl6515909 style='border-top:none;border-left:none' | Yes
| class=xl6515909 style='border-top:none;border-left:none' | Yes
| class=xl6515909 style='border-top:none;border-left:none' | Yes
|- height=20 style='height:15.0pt'
| height=20 class=xl6315909 style='height:15.0pt;border-top:none' | TDM
| class=xl6515909 style='border-top:none;border-left:none' | Yes
| class=xl6515909 style='border-top:none;border-left:none' | Yes
| class=xl6515909 style='border-top:none;border-left:none' | Yes
|- height=20 style='height:15.0pt'
| height=20 class=xl6315909 style='height:15.0pt;border-top:none' | SD
| class=xl6515909 style='border-top:none;border-left:none' | Yes
| class=xl6515909 style='border-top:none;border-left:none' | Yes
| class=xl6515909 style='border-top:none;border-left:none' | Yes
|- height=20 style='height:15.0pt'
| height=20 class=xl6315909 style='height:15.0pt;border-top:none' | SAB
| class=xl6515909 style='border-top:none;border-left:none' | Yes
| class=xl6515909 style='border-top:none;border-left:none' | Yes
| class=xl6515909 style='border-top:none;border-left:none' | Yes
|- height=20 style='height:15.0pt'
| height=20 class=xl6315909 style='height:15.0pt;border-top:none' | DOM
| class=xl6515909 style='border-top:none;border-left:none' | Yes
| class=xl6515909 style='border-top:none;border-left:none' | Yes
| class=xl6515909 style='border-top:none;border-left:none' | Yes
|- height=20 style='height:15.0pt'
| height=20 class=xl6315909 style='height:15.0pt;border-top:none' | KOTH
| class=xl6515909 style='border-top:none;border-left:none' | Yes
| class=xl6515909 style='border-top:none;border-left:none' | Yes
| class=xl6515909 style='border-top:none;border-left:none' | Yes
|- height=20 style='height:15.0pt'
| height=20 class=xl6315909 style='height:15.0pt;border-top:none' | CTF
| class=xl6515909 style='border-top:none;border-left:none' | Yes
| class=xl6515909 style='border-top:none;border-left:none' | Yes
| class=xl6515909 style='border-top:none;border-left:none' | Yes
|- height=20 style='height:15.0pt'
| height=20 class=xl6315909 style='height:15.0pt;border-top:none' | SUR
| class=xl6515909 style='border-top:none;border-left:none' | No
| class=xl6515909 style='border-top:none;border-left:none' | No
| class=xl6515909 style='border-top:none;border-left:none' | No
|- height=0 style='display:none'
| width=77 style='width:58pt' |
| width=72 style='width:54pt' |
| width=110 style='width:83pt' |
| width=110 style='width:83pt' |
|}

== Server Config ==

This next section will give you a base server config, a more detailed Server Config can be found [[Call of Duty 5: Advanced Server Config|HERE]]

Now Create a file called '''server.cfg''' and place in /Main -- '''Server.cfg''' can contains (change passwords of course):

<pre>
seta sv_punkbuster 1
wait
pb_sv_enable

// Server name
set sv_hostname "MY CoDWW Beta Server"

// Server password
set g_password "" // blank means NO password

// Rconpassword
set rcon_password "changeme"

// Maximum Clients
//set sv_privateclients "6"
set sv_maxclients "32"

// Max Ping
set sv_maxping "225"

// Rate
set sv_maxRate "25000"

// Map_rotation
set g_gametype "tdm"

set sv_mapRotation "gametype tdm map mp_castle gametype tdm map mp_makin gametype tdm map mp_roundhouse";
</pre>

== Starting Server ==

[[Image:Warning.png]] Windows ONLY and not for servers from Game Servers Providers!

*Right-click your Shorcut for CoDWaWbeta.exe and add this at the end:

+set dedicated 2 +set net_ip xxx.xxx.xxx.xxx +set net_port 28960 +exec server.cfg +map_rotate

[[Image:Warning.png]] Make sure that " are present in the Shorcut around CoDWaWbeta.exe. Example:

"C:/Program Files/Activision/Call of Duty- World at War Beta\CoDWaWbeta.exe" +set dedicated 2 +set net_ip xxx.xxx.xxx.xxx +set net_port 28960 +exec server.cfg +map_rotate

[[Image:Information.png]] Replace xxx.xxx.xxx.xxx by your Public IP adress. If unsure of your Public IP Address you can go [http://www.whatismyip.com HERE] to check it out.

[[Image:codww_server_1.png]]

*Once the server starts you should get the console:

[[Image:codww_server_2.png]]

Call of Duty 4: ModTools Content

2008-11-04T17:48:45Z

Novemberdobby:

[[Category:Modtools]]
[[Category:Call of Duty 4]]
==What's included==

Xmodels: After the Modtools are installed, 'C:\Program Files\Activision\Call of Duty 4 - Modern Warfare\main\xmodel\' should contain all the extracted model files.

----

bin\CoD4Radiant.exe
Level editor. Create custom .map files for single player or multiplayer.

On running CoD4Radiant for the first time, you will need to load the included cod4.prj project file which is located in "\bin".

'''Note: all files below are in the specified subfolder of the Call Of Duty 4 folder.'''

bin\CoD4_EffectsEd.exe
The CoD4 effect editor. Create and modify your own effects.

On running CoD4_EffectsEd for the first time, you will be asked to browse to the location the game is installed. The default location is "C:\Program Files\Activision\Call of Duty 4 - Modern Warfare". For Steam users, this directory is: "C:\steam\steamapps\common\call of duty 4\".

bin\CoD4CompileTools\CoD4CompileTools.exe
Graphical UI tool that is handy for compiling and running maps.

On running CoD4CompileTools for the first time you must click the "browse" button in the upper left corner and browse to the location the game is installed. The default location is "Program Files\Activision\Call of Duty 4 Modern Warfare".

bin\asset_manager.exe

Tool used for adding/modifying assets to the game. See the [[Call of Duty 4: Maya|Maya documentation]] for sample usage.

bin\cod4map.exe
Compiles the .map file and creates a .d3dbsp. Referenced by CoD4CompileTools.exe, but can be called manually as well.

bin\cod4rad.exe
Calculates lighting for a map and writes to the .d3dbsp. Referenced by CoD4CompileTools.exe, but can be called manually as well.

bin\cod4rad64.exe
64-bits version of the above.

bin\converter.exe
Converts data from asset manager to game data. If you add something to asset_manager, you must then run converter before seeing your assets in the game.

bin\linker_pc.exe
Linker PC is the piece of software that will process the required resources for a mod/map and compress them into a FastFile (.ff).

bin\maya\
In here you will find the Maya 8 model and animation export Plugins. See the [[Call of Duty 4: Maya|Maya documentation]] for information on how to setup these Plugins with Maya 7 or 8.5.

collmaps\
This is where collision map files are stored. Their filenames correspond to the xmodel name in the xmodel folder. By default, static models do not have collision, they get their collision data from these collmaps that we have made.

devraw\
CoD4EffectsEd.exe looks in this folder for effectsEd_box.d3dbsp which is the bsp the editor loads. You can replace this bsp with another if you'd like CoD4EffectsEd.exe to use a different bsp.

map_source\
Included is the source for two official maps (Blackout - Single-player & Backlot - Multi-player) and this is where they are located, along with all the prefabs they reference. There is also a multiplayer test map (mp_test.map) included which contains the basics for any multiplayer map that can be helpful for testing. Finally a test map for single player is also included for your benefit (test_traverses.map)

xmodel_export\
The base character and hotbox model is located here. See included [[Call of Duty 4: Maya|Maya documentation]] for explanation of this.

Call of Duty 4: ModTools Content

2008-11-04T17:48:30Z

Novemberdobby:

[[Category:Modtools]]
[[Category:Call of Duty 4]]
==What's included==

Xmodels: After the Modtools are installed, 'C:\Program Files\Activision\Call of Duty 4 - Modern Warfare\main\xmodel\' should contain all the extracted model files.

----

bin\CoD4Radiant.exe
Level editor. Create custom .map files for single player or multiplayer.

On running CoD4Radiant for the first time, you will need to load the included cod4.prj project file which is located in "\bin".

'''Note: all files below are in the specified subfolder of the Call Of Duty 4 main folder.'''

bin\CoD4_EffectsEd.exe
The CoD4 effect editor. Create and modify your own effects.

On running CoD4_EffectsEd for the first time, you will be asked to browse to the location the game is installed. The default location is "C:\Program Files\Activision\Call of Duty 4 - Modern Warfare". For Steam users, this directory is: "C:\steam\steamapps\common\call of duty 4\".

bin\CoD4CompileTools\CoD4CompileTools.exe
Graphical UI tool that is handy for compiling and running maps.

On running CoD4CompileTools for the first time you must click the "browse" button in the upper left corner and browse to the location the game is installed. The default location is "Program Files\Activision\Call of Duty 4 Modern Warfare".

bin\asset_manager.exe

Tool used for adding/modifying assets to the game. See the [[Call of Duty 4: Maya|Maya documentation]] for sample usage.

bin\cod4map.exe
Compiles the .map file and creates a .d3dbsp. Referenced by CoD4CompileTools.exe, but can be called manually as well.

bin\cod4rad.exe
Calculates lighting for a map and writes to the .d3dbsp. Referenced by CoD4CompileTools.exe, but can be called manually as well.

bin\cod4rad64.exe
64-bits version of the above.

bin\converter.exe
Converts data from asset manager to game data. If you add something to asset_manager, you must then run converter before seeing your assets in the game.

bin\linker_pc.exe
Linker PC is the piece of software that will process the required resources for a mod/map and compress them into a FastFile (.ff).

bin\maya\
In here you will find the Maya 8 model and animation export Plugins. See the [[Call of Duty 4: Maya|Maya documentation]] for information on how to setup these Plugins with Maya 7 or 8.5.

collmaps\
This is where collision map files are stored. Their filenames correspond to the xmodel name in the xmodel folder. By default, static models do not have collision, they get their collision data from these collmaps that we have made.

devraw\
CoD4EffectsEd.exe looks in this folder for effectsEd_box.d3dbsp which is the bsp the editor loads. You can replace this bsp with another if you'd like CoD4EffectsEd.exe to use a different bsp.

map_source\
Included is the source for two official maps (Blackout - Single-player & Backlot - Multi-player) and this is where they are located, along with all the prefabs they reference. There is also a multiplayer test map (mp_test.map) included which contains the basics for any multiplayer map that can be helpful for testing. Finally a test map for single player is also included for your benefit (test_traverses.map)

xmodel_export\
The base character and hotbox model is located here. See included [[Call of Duty 4: Maya|Maya documentation]] for explanation of this.

Call of Duty 4: ModTools Content

2008-11-04T17:36:41Z

Novemberdobby: Added full directories & Steam folder location

[[Category:Modtools]]
[[Category:Call of Duty 4]]
==What's included==

Xmodels: After the Modtools are installed, 'C:\Program Files\Activision\Call of Duty 4 - Modern Warfare\main\xmodel\' should contain all the extracted model files.

----

Inside '''bin\'''

bin\CoD4Radiant.exe
Level editor. Create custom .map files for single player or multiplayer.

On running CoD4Radiant for the first time, you will need to load the included cod4.prj project file which is located in "\bin".

Note: all files below are in the specified subfolder of the Call Of Duty 4 main folder.

bin\CoD4_EffectsEd.exe
The CoD4 effect editor. Create and modify your own effects.

On running CoD4_EffectsEd for the first time, you will be asked to browse to the location the game is installed. The default location is "C:\Program Files\Activision\Call of Duty 4 - Modern Warfare". For Steam users, this directory is: "C:\steam\steamapps\common\call of duty 4\".

bin\CoD4CompileTools\CoD4CompileTools.exe
Graphical UI tool that is handy for compiling and running maps.

On running CoD4CompileTools for the first time you must click the "browse" button in the upper left corner and browse to the location the game is installed. The default location is "Program Files\Activision\Call of Duty 4 Modern Warfare".

bin\asset_manager.exe

Tool used for adding/modifying assets to the game. See the [[Call of Duty 4: Maya|Maya documentation]] for sample usage.

bin\cod4map.exe
Compiles the .map file and creates a .d3dbsp. Referenced by CoD4CompileTools.exe, but can be called manually as well.

bin\cod4rad.exe
Calculates lighting for a map and writes to the .d3dbsp. Referenced by CoD4CompileTools.exe, but can be called manually as well.

bin\cod4rad64.exe
64-bits version of the above.

bin\converter.exe
Converts data from asset manager to game data. If you add something to asset_manager, you must then run converter before seeing your assets in the game.

bin\linker_pc.exe
Linker PC is the piece of software that will process the required resources for a mod/map and compress them into a FastFile (.ff).

bin\maya\
In here you will find the Maya 8 model and animation export Plugins. See the [[Call of Duty 4: Maya|Maya documentation]] for information on how to setup these Plugins with Maya 7 or 8.5.

collmaps\
This is where collision map files are stored. Their filenames correspond to the xmodel name in the xmodel folder. By default, static models do not have collision, they get their collision data from these collmaps that we have made.

devraw\
CoD4EffectsEd.exe looks in this folder for effectsEd_box.d3dbsp which is the bsp the editor loads. You can replace this bsp with another if you'd like CoD4EffectsEd.exe to use a different bsp.

map_source\
Included is the source for two official maps (Blackout - Single-player & Backlot - Multi-player) and this is where they are located, along with all the prefabs they reference. There is also a multiplayer test map (mp_test.map) included which contains the basics for any multiplayer map that can be helpful for testing. Finally a test map for single player is also included for your benefit (test_traverses.map)

xmodel_export\
The base character and hotbox model is located here. See included [[Call of Duty 4: Maya|Maya documentation]] for explanation of this.

Call of Duty 4: mapping mp

2008-11-04T17:26:03Z

Novemberdobby: more sorting

[[Image:Call-of-duty-4.gif|right]]

[[Image:Design.png|left]]

== Getting Started ==
[[Image:Tutorials.png|right]]
* [[Call of Duty 4: needed|What's needed]]
* [[Call of Duty 4: ModTools Content|ModTools Content]]
* [[Call of Duty 4: Your First Map|Building your first map in Radiant]]

== Basic Editing ==
[[Image:Design.png|right]]
* [[Call of Duty 4: First Room|Making Your First Room + Texturing]]
* [[Call of Duty 4: Prefab|Creating and Using Prefabs]]
* [[Call of Duty 4: Lighting|Adding Light]]
* [[Call of Duty 4: Adding Entities|Adding Entities (like MP Spawns)]]
* [[Call of Duty 4: Placing Models|Adding Models]]
* [[Call of Duty 4: Skybox|Adding a Skybox]]
* [[Call of Duty 4: Building Stairs|Building Stairs]]
* [[Call of Duty 4: Water|Using Water]]
* [[Call of Duty 4: Patches|Curve and Terrain Patches]]
* [[Call of Duty 4: Arches|Creating Arches]]
* [[Call of Duty 4: Adding Decals|Adding Decals]]
* [[Call of Duty 4: Reflection Probes|Adding Reflection Probes]]
* [[Call of Duty 4: Gridfile|Create a Gridfile]]
* [[Call of Duty 4: Compile Tools|Using Compile Tools]]

----
[[Image:Articles.png|right]]
* [[Call of Duty 4: Tool Textures Explained|Tool Textures Explained]]
** [[Call of Duty 4: Mantles|Mantles]]
** [[Call of Duty 4: Ladders|Ladders]]
** [[Call of Duty 4: Clip|Clip]]

== Advanced Editing ==
[[Image:Design.png|right]]
* [[Call of Duty 4: Advanced Lighting|Advanced Lighting]]
* [[Call of Duty 4: Portals|Portals, How-to]]
** [[Call of Duty 4: Portals1|Portals tutorial #1]]
** [[Call of Duty 4: Portals2|Portals tutorial #2]]
** [[Call of Duty 4: Portals3|Portals tutorial #3]]
* [[Call of Duty 4: Detailing|The Art of Detailing]]
* [[Call of Duty 4: Decals|The Art of Decals]]
* [[Call of Duty 4: Sounds|Ambient and map Sounds]]
* [[Call of Duty 4: Sun|Adding Sun/Moon]]
* [[Call of Duty 4: Custom Textures|Custom Textures]]
* [[Call of Duty 4: transparent Minimap|Create a Transparent Minimap]]
* [[Call of Duty 4: Custom Skyboxes|Create a Custom Skybox]]
* [[Call of Duty 4: Create a mp burg like map#Making a tunnel|Making a Tunnel (Like mp_burg)]]
* [[Call of Duty 4: .vision file|Create a Vision File]]
* [[Call of Duty 4: Hint Brushes|Using Hint Brushes]]
* [[Call of Duty 4: Minefields|Create Minefields]]
* [[Call of Duty 4: Breakable Brushes|Breakable Brushes]]
* [[Call of Duty 4: Godrays|Adding Godrays]]
* [[Call of Duty 4: Video Mapicted Tutorials|Mapicted Videos Tutorials]]
----
[[Image:Tutorials.png|right]]
* [[Call of Duty 4: FXs|Special Effects - FXs]]
** [[Call of Duty 4: FXs|Place FXs in Map]]
** [[Call of Duty 4: destruct model|Destructable Models]]
** [[Call of Duty 4: RainFX|Adding Rain]]
** [[Call of Duty 4: Editing Stock FX|Editing Stock FXs]]

== Modelling / Skinning ==
[[Image:Design.png|right]]
* [[Call of duty 4: Import models|Import models in game]]
* [[Call of Duty 4: Import COD2 Models|Import COD2 Models]]
* [[Call of Duty 4: Maya|Modelling/Skining]]
**[[Call of Duty 4: Maya#Maya 8 plugin setup|Maya setup]]
**[[Call of Duty 4: Maya#Setting up, skinning and exporting a character model|General setup]]
**[[Call of Duty 4: Maya#IW Dev conventions|Conventions]]
**[[Call of Duty 4: Maya#Creating a Rig|Create a Rig]]
**[[Call of Duty 4: Maya#Rigging|Rigging]]
**[[Call of Duty 4: Maya#Materials|Materials]]
**[[Call of Duty 4: Maya#Animations|Animations]]
**[[Call of Duty 4: Maya#Working with and exporting animations|Exporting Animations]]
**[[Call of Duty 4: Maya#Asset Manager|AssMan]]
**[[Call of Duty 4: Maya#Models|Models]]
**[[Call of Duty 4: Maya#Converting models and animations|Convert Models/Anims]]

== Scripts & Mapping ==
[[Image:Articles.png|right]]
* [[Call of Duty 4: Rotating Models|Scripting: Rotating Brushes/Models]]
* [[Call of Duty 4: Moving Brushes|Scripting: Moving Brushes]]
* [[Call of Duty 4: Bobbing Models|Scripting: Bobbing Models]]
* [[Call of Duty 4: Elevator Brushes|Scripting: Elevators]]
* [[Call of Duty 4: Breakable Windows|Scripting: Breakable Windows]]
* [[Call of Duty 4: Teleporter|Scripting: Teleporters]]
* [[Call of Duty 4: Jumppads|Scripting: Jump Pads]]
* [[Call of Duty 4: Vending Machine|Scripting: Vending Machines]]
* [[Call of Duty 4: Flapping Shutters|Scripting: Flapping Shutters]]
* [[Call of Duty 4: Switches Primary Light|Scripting: Primary Light Switch]]

== Gametypes==
[[Image:Tutorials.png|right]]
* [[Call of Duty 4: Adding Entities#Setting up gameplay modes|Adding Stock Gametypes]]
* [[Call of Duty 4: Gametypes |Adding CTF/CTFB to your map]]
* [[Call of Duty 4: Retrieval |Adding Retrieval Gametype to your map]]

==Releasing a Map==
[[Image:Articles.png|right]]
* [[Call of Duty 4: Test the map|Test your map]]
* [[Call of Duty 4: Minimap|Create a Minimap ]]
* [[Call of Duty 4: Loadscreen Creation|Create a Loadscreen]]
* [[Call of Duty 4: Helipaths|Create Helipath]]
* [[Call of Duty 4: Map naming|Map naming]]
* [[Call of Duty 4: Readme file|Create a Readme]]
* [[Call of Duty 4: Releasing General|Releasing a Map]]

== Tips & Troubleshooting ==
[[Image:Articles.png|right]]
* [[Call of Duty 4: Tips|Tips]]
* [[Call of Duty 4: Troubleshooting|Troubleshooting]]
* [[Call of Duty 4: Compile Errors|Compile Errors]]

==Technical References==
[[Image:Information.png|right]]
* [[Call of Duty 4: d3dbsp|D3DBSP File format by Daevius]]
* [[Call of Duty 4: Demo Player|Demo Player]]
* [[Call of Duty 4: Gameplay standards|Gameplay standards]]
* [[Call of Duty 4: MAP file structure|.MAP file structure by Daevius]]
* [[Call of Duty 4: Map Overhead|MP Maps Overhead - COD4]]
* [[Call of Duty 4: MP Lights Settings|MP Maps Worldspawn]]
* [[Call of Duty 4: MP Weapons|MP Weapons]]
* [[Objects]]
** [[Call of Duty 4: Items|Items (weapons, pickups)]]
** [[Call of Duty 4: World Models|World Models]]
* [[Call of Duty 4: Partial Fastfile Decompile|Partial Fastfile Decompile by Sprinter]]
* [[Radiant Editor]]
** [[Call of Duty 4: Radiant|FAQs]]
** [[Call of Duty 4: Radiant Hotkey Reference|Hotkey Reference]]
** [[Call of Duty 4: Toolbar|The Toolbar]]
* [[Call of Duty 4: Scripting Reference|Scripting Reference Cod4]]
* [[Call of Duty 4: Skinning Tools|Skinning/Image Tool]]
* [[Call of Duty 4: Stock .vision files|Stock Vision Files]]
* [[Call of Duty 4: Tool Textures|Tool Textures]]
* [[Call of Duty 4: Update Zone File|Zone File]]
* [[Call of Duty 4: Xmodel Exporter|Xmodel Exporter]]

== Upload Sites ==
[[Image:Online.png|right|32px]]
* [[Call of Duty 4: File Hosting Sites|File Hosting Sites]] - A list of reliable websites that host user created maps
* [[Call of Duty 4: News Site List|News Site List]] - A list of websites for hype/advertisement and discussion

== About Cod4 and its creators ==
[[Image:Infinityward.png|right]]
'''Infinity Ward''', located in Encino, California, is a computer game developer founded in 2002 by 22 former employees of 2015, developers of Medal of Honor: Allied Assault. Infinity Ward was acquired by Activision in October 2003.

----

'''Call of Duty 4: Modern Warfare''' is a first-person shooter video game developed by Infinity Ward and published by Activision for the PlayStation 3, Windows, and the Xbox 360. It was released on September 30, 2008 for Mac OS X. It is the fourth installment of the Call of Duty video game series, excluding expansion packs. The game breaks away from the World War II setting of previous games in the series and is instead set in modern times.
The game is the first in the series to be rated Mature in North America. The title and game details were announced on April 25, 2007, and the game was released worldwide between November 6, 2007 and November 9, 2007. It became available on Steam on November 6, 2007 for pre-purchase, and was available to play on November 12, 2007. The game was in development for two years. It uses a proprietary game engine, and includes features that include true world-dynamic lightning, HDR lighting effects, dynamics shadows, and depth of field.

[[Image:Geographylogo.png]][http://www.infinityward.com/ IW Official Website]

Call of Duty 4: Radiant Hotkey Reference

2008-11-04T17:20:16Z

Novemberdobby:

[[Category:Call of Duty 4]]
[[Category:Radiant]]
[[Category:Technical Reference]]
[[Image:Nutshell.png]] These are the default hot key commands for ''Call of Duty 4'' Radiant level editing.

'''AddTerrainRow''' Shift + Control + A 
'''AdvancedCurveEdit''' Y 
'''ApplyPatchCap''' Shift + Control + P 
'''AssociateEntities''' Shift + G 
'''AutoCaulk''' Alt + C 
'''AutoEdgeTurn''' Alt + F2 
'''CameraAngleDown''' Z 
'''CameraAngleUp''' A 
'''CameraBack''' Down 
'''CameraDown''' C 
'''CameraForward''' Up 
'''CameraLeft''' Left 
'''CameraRight''' Right 
'''CameraStrafeLeft''' Comma 
'''CameraStrafeRight''' Period 
'''CameraUp''' D 
'''CapCurrentCurve''' Shift + C 
'''Center2DOnCamera''' Alt + X 
'''CenterView''' End 
'''ClipSelected''' Return 
'''CloneSelection''' Space 
'''ConnectSelection''' W 
'''Copy''' Control + C 
'''CSGMerge''' Control + U 
'''CubicClipZoomIn''' Control + [ 
'''CubicClipZoomOut''' Control + ] 
'''CycleCapTexturePatch''' Shift + Control + N 
'''CyclinderHeightDown''' Alt + Comma 
'''CyclinderHeightUp''' Alt + Period 
'''DecPatchColumn''' Shift + Control + Subtract 
'''DecPatchRow''' Control + Subtract 
'''DeleteSelection''' Backspace 
'''DisassociateEntities''' Shift + Control + G 
'''DownFloor''' PageDown 
'''DragEdges''' E 
'''DragVertices''' V 
'''DropVertices''' Shift + Alt + Control + D 
'''DynEntities''' Shift + Y 
'''EnterPrefab''' Alt + PageDown 
'''EntityColor''' K 
'''ExtrudeTerrainRow''' Alt + O 
'''FileOpen''' Control + O 
'''FileSave''' Control + S 
'''FitBrush''' Shift + B 
'''FlipClip''' Control + Return 
'''GetDistance''' Alt + F1 
'''GridDown''' [ 
'''GridUp''' ] 
'''HideByClassname''' Shift + Alt + Control + H 
'''HideSelected''' H 
'''HideUnSelected''' Alt + H 
'''IncPatchColumn''' Shift + Control + Plus 
'''IncPatchRow''' Control + Plus 
'''InvertCurve''' Control + I 
'''InvertCurveTextureX''' Shift + Control + I 
'''InvertCurveTextureY''' Shift + I 
'''InvertSelection''' I 
'''LeavePrefab''' Alt + PageUp 
'''LightPreviewClear''' Alt + F8 
'''LightPreviewRegions''' Shift + Control + F8 
'''LightPreviewStart''' Shift + F8 
'''LightPreviewStop''' Shift + Alt + F8 
'''LightPreviewSun''' Control + F8 
'''LightPreviewToggle''' F8 
'''LightShiftDown''' Alt + [ 
'''LightShiftUp''' Alt + ] 
'''LinkSelected''' Alt + Q 
'''LinkSelectionToggle''' Shift + O 
'''MakeDetail''' Shift + Control + D 
'''MakeNonColliding''' Shift + Control + Minus 
'''MakeStructural''' Shift + Control + S 
'''MakeWeaponClip''' Shift + Control + W 
'''MapInfo''' M 
'''MaxLightIntensity''' Alt + Control + F8 
'''MouseRotate''' R 
'''MoveSelectionDOWN''' Subtract 
'''MoveSelectionUP''' Plus 
'''NaturalizePatch''' Control + N 
'''NextLeakSpot''' Shift + Control + K 
'''NextView Control''' + Tab 
'''OverBrightShiftDown''' Shift + [ 
'''OverBrightShiftUp''' Shift + ] 
'''Paste''' Control + V 
'''Patch TAB''' Shift + Tab 
'''Patch TAB''' Tab 
'''PatchInspector''' Shift + S 
'''PatchMatrixTranspose''' Shift + Control + M 
'''Preferences''' P 
'''PrevLeakSpot''' Shift + Control + L 
'''RedisperseCols''' Shift + Control + E 
'''RedisperseRows''' Shift + E 
'''RedisperseVertices''' Shift + F 
'''Redo Control''' + Y 
'''RefreshTextures''' F5 
'''RemoveColorNode''' Control + R 
'''RemoveTerrainRow''' Shift + Control + Q 
'''RotateZ''' Shift + D 
'''SameTarget''' Control + B 
'''SameTargetname''' B 
'''SelectAllOfType''' Shift + A 
'''SelectAllOfTypeRecurse''' Alt + A 
'''SelectConnectedEntities''' Alt + Control + E 
'''SelectedAssociated''' Control + X 
'''SelectionKeyValue''' Shift + Control + F 
'''SelectNext''' Shift + Period 
'''SelectNudgeDown''' Alt + Down 
'''SelectNudgeLeft''' Alt + Left 
'''SelectNudgeRight''' Alt + Right 
'''SelectNudgeUp''' Alt + Up 
'''SelectPrev''' Shift + Comma 
'''SelectSnapPointsToGrid''' Control + G 
'''SelectTargettedEntities''' Control + E 
'''SetGrid1''' 1 
'''SetGrid16''' 5 
'''SetGrid2''' 2 
'''SetGrid256''' 8 
'''SetGrid32''' 6 
'''SetGrid4''' 3 
'''SetGrid512''' 9 
'''SetGrid64''' 7 
'''SetGrid8''' 4 
'''SetGridPointFive''' ~ 
'''SetViewToEntity''' F6 
'''ShowAllTextures''' Control + A 
'''ShowHidden''' Shift + H 
'''ShowLastHidden''' Shift + Control + H 
'''ShowTexturesInUse''' U 
'''SplaySelection''' Alt + W 
'''SplitPatch''' Shift + Control + X 
'''SplitSelected''' Shift + Return 
'''SurfaceInspector''' S 
'''TexDecrement''' Shift + Subtract 
'''TexIncrement''' Shift + Plus 
'''TexLayerCycle''' Shift + L 
'''TexRotateClock''' Control + Left 
'''TexRotateCounter''' Control + Right 
'''TexScaleLeft''' Control + Left 
'''TexScaleRight''' Control + Right 
'''TexShiftDown''' Shift + Down 
'''TexShiftLeft''' Shift + Left 
'''TexShiftRight''' Shift + Right 
'''TexShiftUp''' Shift + Up 
'''TextureFit''' Control + F 
'''TextureFitAll''' Alt + Control + F 
'''ThickenPatch''' Shift + Control + T 
'''ToggleCamera''' Shift + Control + C 
'''ToggleClipper''' X 
'''ToggleCrosshairs''' Shift + X 
'''ToggleCubicClip''' Control + \ 
'''ToggleGrid''' 0 
'''ToggleLayeredMaterialWnd''' F4 
'''ToggleLayers''' L 
'''ToggleLockPatchVertices''' Control + Period 
'''ToggleOutlineDraw''' J 
'''TogglePatchWireframes''' Shift + W 
'''ToggleSnapToGrid''' Alt + Control + G 
'''ToggleTexMoveLock''' Shift + T 
'''ToggleTexRotateLock''' Shift + R 
'''ToggleTintDraw Shift''' + J 
'''ToggleTurnTerrainEdges''' Control + ¿ 
'''ToggleUnlockPatchVertices''' Shift + Control + Period 
'''ToggleView''' Shift + Control + V 
'''ToggleZ''' Shift + Control + Z 
'''TolerantWeld''' Shift + Control + J 
'''Undo''' Control + Z 
'''UnSelectSelection''' Escape 
'''UpFloor''' PageUp 
'''VehicleGroup''' Shift + V 
'''VertEdit''' G 
'''Vertex Select Down''' Control + Down 
'''Vertex Select Up''' Control + Up 
'''ViewConsole''' O 
'''ViewEntityInfo''' N 
'''ViewFilters''' F 
'''ViewTextures''' T 
'''ZoomIn''' Delete 
'''ZoomOut''' Insert 
'''ZZoomIn''' Control + Delete 
'''ZZoomOut''' Control + Insert

Call of Duty 4: Radiant Hotkey Reference

2008-11-04T17:17:46Z

Novemberdobby: Removed some unused shortcuts, sorted alphabetically.

[[Category:Call of Duty 4]]
[[Category:Radiant]]
[[Category:Technical Reference]]
[[Image:Nutshell.png]] These are the default hot key commands for ''Call of Duty 4'' Radiant level editing.

'''AddTerrainRow''' Shift + Control + A 
'''AdvancedCurveEdit''' Y
'''ApplyPatchCap''' Shift + Control + P
'''AssociateEntities''' Shift + G
'''AutoCaulk''' Alt + C
'''AutoEdgeTurn''' Alt + F2
'''CameraAngleDown''' Z
'''CameraAngleUp''' A
'''CameraBack''' Down
'''CameraDown''' C
'''CameraForward''' Up
'''CameraLeft''' Left
'''CameraRight''' Right
'''CameraStrafeLeft''' Comma
'''CameraStrafeRight''' Period
'''CameraUp''' D
'''CapCurrentCurve''' Shift + C
'''Center2DOnCamera''' Alt + X
'''CenterView''' End
'''ClipSelected''' Return
'''CloneSelection''' Space
'''ConnectSelection''' W
'''Copy''' Control + C
'''CSGMerge''' Control + U
'''CubicClipZoomIn''' Control + [
'''CubicClipZoomOut''' Control + ]
'''CycleCapTexturePatch''' Shift + Control + N
'''CyclinderHeightDown''' Alt + Comma
'''CyclinderHeightUp''' Alt + Period
'''DecPatchColumn''' Shift + Control + Subtract
'''DecPatchRow''' Control + Subtract
'''DeleteSelection''' Backspace
'''DisassociateEntities''' Shift + Control + G
'''DownFloor''' PageDown
'''DragEdges''' E
'''DragVertices''' V
'''DropVertices''' Shift + Alt + Control + D
'''DynEntities''' Shift + Y
'''EnterPrefab''' Alt + PageDown
'''EntityColor''' K
'''ExtrudeTerrainRow''' Alt + O
'''FileOpen''' Control + O
'''FileSave''' Control + S
'''FitBrush''' Shift + B
'''FlipClip''' Control + Return
'''GetDistance''' Alt + F1
'''GridDown''' [
'''GridUp''' ]
'''HideByClassname''' Shift + Alt + Control + H
'''HideSelected''' H
'''HideUnSelected''' Alt + H
'''IncPatchColumn''' Shift + Control + Plus
'''IncPatchRow''' Control + Plus
'''InvertCurve''' Control + I
'''InvertCurveTextureX''' Shift + Control + I
'''InvertCurveTextureY''' Shift + I
'''InvertSelection''' I
'''LeavePrefab''' Alt + PageUp
'''LightPreviewClear''' Alt + F8
'''LightPreviewRegions''' Shift + Control + F8
'''LightPreviewStart''' Shift + F8
'''LightPreviewStop''' Shift + Alt + F8
'''LightPreviewSun''' Control + F8
'''LightPreviewToggle''' F8
'''LightShiftDown''' Alt + [
'''LightShiftUp''' Alt + ]
'''LinkSelected''' Alt + Q
'''LinkSelectionToggle''' Shift + O
'''MakeDetail''' Shift + Control + D
'''MakeNonColliding''' Shift + Control + Minus
'''MakeStructural''' Shift + Control + S
'''MakeWeaponClip''' Shift + Control + W
'''MapInfo''' M
'''MaxLightIntensity''' Alt + Control + F8
'''MouseRotate''' R
'''MoveSelectionDOWN''' Subtract
'''MoveSelectionUP''' Plus
'''NaturalizePatch''' Control + N
'''NextLeakSpot''' Shift + Control + K
'''NextView Control''' + Tab
'''OverBrightShiftDown''' Shift + [
'''OverBrightShiftUp''' Shift + ]
'''Paste''' Control + V
'''Patch TAB''' Shift + Tab
'''Patch TAB''' Tab
'''PatchInspector''' Shift + S
'''PatchMatrixTranspose''' Shift + Control + M
'''Preferences''' P
'''PrevLeakSpot''' Shift + Control + L
'''RedisperseCols''' Shift + Control + E
'''RedisperseRows''' Shift + E
'''RedisperseVertices''' Shift + F
'''Redo Control''' + Y
'''RefreshTextures''' F5
'''RemoveColorNode''' Control + R
'''RemoveTerrainRow''' Shift + Control + Q
'''RotateZ''' Shift + D
'''SameTarget''' Control + B
'''SameTargetname''' B
'''SelectAllOfType''' Shift + A
'''SelectAllOfTypeRecurse''' Alt + A
'''SelectConnectedEntities''' Alt + Control + E
'''SelectedAssociated''' Control + X
'''SelectionKeyValue''' Shift + Control + F
'''SelectNext''' Shift + Period
'''SelectNudgeDown''' Alt + Down
'''SelectNudgeLeft''' Alt + Left
'''SelectNudgeRight''' Alt + Right
'''SelectNudgeUp''' Alt + Up
'''SelectPrev''' Shift + Comma
'''SelectSnapPointsToGrid''' Control + G
'''SelectTargettedEntities''' Control + E
'''SetGrid1''' 1
'''SetGrid16''' 5
'''SetGrid2''' 2
'''SetGrid256''' 8
'''SetGrid32''' 6
'''SetGrid4''' 3
'''SetGrid512''' 9
'''SetGrid64''' 7
'''SetGrid8''' 4
'''SetGridPointFive''' ~
'''SetViewToEntity''' F6
'''ShowAllTextures''' Control + A
'''ShowHidden''' Shift + H
'''ShowLastHidden''' Shift + Control + H
'''ShowTexturesInUse''' U
'''SplaySelection''' Alt + W
'''SplitPatch''' Shift + Control + X
'''SplitSelected''' Shift + Return
'''SurfaceInspector''' S
'''TexDecrement''' Shift + Subtract
'''TexIncrement''' Shift + Plus
'''TexLayerCycle''' Shift + L
'''TexRotateClock''' Control + Left
'''TexRotateCounter''' Control + Right
'''TexScaleLeft''' Control + Left
'''TexScaleRight''' Control + Right
'''TexShiftDown''' Shift + Down
'''TexShiftLeft''' Shift + Left
'''TexShiftRight''' Shift + Right
'''TexShiftUp''' Shift + Up
'''TextureFit''' Control + F
'''TextureFitAll''' Alt + Control + F
'''ThickenPatch''' Shift + Control + T
'''ToggleCamera''' Shift + Control + C
'''ToggleClipper''' X
'''ToggleCrosshairs''' Shift + X
'''ToggleCubicClip''' Control + \
'''ToggleGrid''' 0
'''ToggleLayeredMaterialWnd''' F4
'''ToggleLayers''' L
'''ToggleLockPatchVertices''' Control + Period
'''ToggleOutlineDraw''' J
'''TogglePatchWireframes''' Shift + W
'''ToggleSnapToGrid''' Alt + Control + G
'''ToggleTexMoveLock''' Shift + T
'''ToggleTexRotateLock''' Shift + R
'''ToggleTintDraw Shift''' + J
'''ToggleTurnTerrainEdges''' Control + ¿
'''ToggleUnlockPatchVertices''' Shift + Control + Period
'''ToggleView''' Shift + Control + V
'''ToggleZ''' Shift + Control + Z
'''TolerantWeld''' Shift + Control + J
'''Undo''' Control + Z
'''UnSelectSelection''' Escape
'''UpFloor''' PageUp
'''VehicleGroup''' Shift + V
'''VertEdit''' G
'''Vertex Select Down''' Control + Down
'''Vertex Select Up''' Control + Up
'''ViewConsole''' O
'''ViewEntityInfo''' N
'''ViewFilters''' F
'''ViewTextures''' T
'''ZoomIn''' Delete
'''ZoomOut''' Insert
'''ZZoomIn''' Control + Delete
'''ZZoomOut''' Control + Insert

Call of Duty 4: Radiant Hotkey Reference

2008-11-04T17:17:18Z

Novemberdobby: Removed some unused shortcuts, sorted alphabetically.

[[Category:Call of Duty 4]]
[[Category:Radiant]]
[[Category:Technical Reference]]
[[Image:Nutshell.png]] These are the default hot key commands for ''Call of Duty 4'' Radiant level editing.

'''AddTerrainRow''' Shift + Control + A
'''AdvancedCurveEdit''' Y
'''ApplyPatchCap''' Shift + Control + P
'''AssociateEntities''' Shift + G
'''AutoCaulk''' Alt + C
'''AutoEdgeTurn''' Alt + F2
'''CameraAngleDown''' Z
'''CameraAngleUp''' A
'''CameraBack''' Down
'''CameraDown''' C
'''CameraForward''' Up
'''CameraLeft''' Left
'''CameraRight''' Right
'''CameraStrafeLeft''' Comma
'''CameraStrafeRight''' Period
'''CameraUp''' D
'''CapCurrentCurve''' Shift + C
'''Center2DOnCamera''' Alt + X
'''CenterView''' End
'''ClipSelected''' Return
'''CloneSelection''' Space
'''ConnectSelection''' W
'''Copy''' Control + C
'''CSGMerge''' Control + U
'''CubicClipZoomIn''' Control + [
'''CubicClipZoomOut''' Control + ]
'''CycleCapTexturePatch''' Shift + Control + N
'''CyclinderHeightDown''' Alt + Comma
'''CyclinderHeightUp''' Alt + Period
'''DecPatchColumn''' Shift + Control + Subtract
'''DecPatchRow''' Control + Subtract
'''DeleteSelection''' Backspace
'''DisassociateEntities''' Shift + Control + G
'''DownFloor''' PageDown
'''DragEdges''' E
'''DragVertices''' V
'''DropVertices''' Shift + Alt + Control + D
'''DynEntities''' Shift + Y
'''EnterPrefab''' Alt + PageDown
'''EntityColor''' K
'''ExtrudeTerrainRow''' Alt + O
'''FileOpen''' Control + O
'''FileSave''' Control + S
'''FitBrush''' Shift + B
'''FlipClip''' Control + Return
'''GetDistance''' Alt + F1
'''GridDown''' [
'''GridUp''' ]
'''HideByClassname''' Shift + Alt + Control + H
'''HideSelected''' H
'''HideUnSelected''' Alt + H
'''IncPatchColumn''' Shift + Control + Plus
'''IncPatchRow''' Control + Plus
'''InvertCurve''' Control + I
'''InvertCurveTextureX''' Shift + Control + I
'''InvertCurveTextureY''' Shift + I
'''InvertSelection''' I
'''LeavePrefab''' Alt + PageUp
'''LightPreviewClear''' Alt + F8
'''LightPreviewRegions''' Shift + Control + F8
'''LightPreviewStart''' Shift + F8
'''LightPreviewStop''' Shift + Alt + F8
'''LightPreviewSun''' Control + F8
'''LightPreviewToggle''' F8
'''LightShiftDown''' Alt + [
'''LightShiftUp''' Alt + ]
'''LinkSelected''' Alt + Q
'''LinkSelectionToggle''' Shift + O
'''MakeDetail''' Shift + Control + D
'''MakeNonColliding''' Shift + Control + Minus
'''MakeStructural''' Shift + Control + S
'''MakeWeaponClip''' Shift + Control + W
'''MapInfo''' M
'''MaxLightIntensity''' Alt + Control + F8
'''MouseRotate''' R
'''MoveSelectionDOWN''' Subtract
'''MoveSelectionUP''' Plus
'''NaturalizePatch''' Control + N
'''NextLeakSpot''' Shift + Control + K
'''NextView Control''' + Tab
'''OverBrightShiftDown''' Shift + [
'''OverBrightShiftUp''' Shift + ]
'''Paste''' Control + V
'''Patch TAB''' Shift + Tab
'''Patch TAB''' Tab
'''PatchInspector''' Shift + S
'''PatchMatrixTranspose''' Shift + Control + M
'''Preferences''' P
'''PrevLeakSpot''' Shift + Control + L
'''RedisperseCols''' Shift + Control + E
'''RedisperseRows''' Shift + E
'''RedisperseVertices''' Shift + F
'''Redo Control''' + Y
'''RefreshTextures''' F5
'''RemoveColorNode''' Control + R
'''RemoveTerrainRow''' Shift + Control + Q
'''RotateZ''' Shift + D
'''SameTarget''' Control + B
'''SameTargetname''' B
'''SelectAllOfType''' Shift + A
'''SelectAllOfTypeRecurse''' Alt + A
'''SelectConnectedEntities''' Alt + Control + E
'''SelectedAssociated''' Control + X
'''SelectionKeyValue''' Shift + Control + F
'''SelectNext''' Shift + Period
'''SelectNudgeDown''' Alt + Down
'''SelectNudgeLeft''' Alt + Left
'''SelectNudgeRight''' Alt + Right
'''SelectNudgeUp''' Alt + Up
'''SelectPrev''' Shift + Comma
'''SelectSnapPointsToGrid''' Control + G
'''SelectTargettedEntities''' Control + E
'''SetGrid1''' 1
'''SetGrid16''' 5
'''SetGrid2''' 2
'''SetGrid256''' 8
'''SetGrid32''' 6
'''SetGrid4''' 3
'''SetGrid512''' 9
'''SetGrid64''' 7
'''SetGrid8''' 4
'''SetGridPointFive''' ~
'''SetViewToEntity''' F6
'''ShowAllTextures''' Control + A
'''ShowHidden''' Shift + H
'''ShowLastHidden''' Shift + Control + H
'''ShowTexturesInUse''' U
'''SplaySelection''' Alt + W
'''SplitPatch''' Shift + Control + X
'''SplitSelected''' Shift + Return
'''SurfaceInspector''' S
'''TexDecrement''' Shift + Subtract
'''TexIncrement''' Shift + Plus
'''TexLayerCycle''' Shift + L
'''TexRotateClock''' Control + Left
'''TexRotateCounter''' Control + Right
'''TexScaleLeft''' Control + Left
'''TexScaleRight''' Control + Right
'''TexShiftDown''' Shift + Down
'''TexShiftLeft''' Shift + Left
'''TexShiftRight''' Shift + Right
'''TexShiftUp''' Shift + Up
'''TextureFit''' Control + F
'''TextureFitAll''' Alt + Control + F
'''ThickenPatch''' Shift + Control + T
'''ToggleCamera''' Shift + Control + C
'''ToggleClipper''' X
'''ToggleCrosshairs''' Shift + X
'''ToggleCubicClip''' Control + \
'''ToggleGrid''' 0
'''ToggleLayeredMaterialWnd''' F4
'''ToggleLayers''' L
'''ToggleLockPatchVertices''' Control + Period
'''ToggleOutlineDraw''' J
'''TogglePatchWireframes''' Shift + W
'''ToggleSnapToGrid''' Alt + Control + G
'''ToggleTexMoveLock''' Shift + T
'''ToggleTexRotateLock''' Shift + R
'''ToggleTintDraw Shift''' + J
'''ToggleTurnTerrainEdges''' Control + ¿
'''ToggleUnlockPatchVertices''' Shift + Control + Period
'''ToggleView''' Shift + Control + V
'''ToggleZ''' Shift + Control + Z
'''TolerantWeld''' Shift + Control + J
'''Undo''' Control + Z
'''UnSelectSelection''' Escape
'''UpFloor''' PageUp
'''VehicleGroup''' Shift + V
'''VertEdit''' G
'''Vertex Select Down''' Control + Down
'''Vertex Select Up''' Control + Up
'''ViewConsole''' O
'''ViewEntityInfo''' N
'''ViewFilters''' F
'''ViewTextures''' T
'''ZoomIn''' Delete
'''ZoomOut''' Insert
'''ZZoomIn''' Control + Delete
'''ZZoomOut''' Control + Insert

Call of Duty 4: Partial Fastfile Decompile

2008-11-04T17:04:29Z

Novemberdobby:

''Added By Sprinter''

[[Image:Unpack.png|center]]

This tutorial allows you to extract any file from a fastfile that was compressed using the rawfile,filename format. That includes:

.gsc (gametype script)
.txt (e.g gametype definitions file)
.script (e.g playeranim.script)
.vision (map/mod vision files)
.shock (shellshock files)
.atr (animtrees)

[[Image:Data.png]][http://mh-nexus.de/en/hxd/ HxD] 
[[Image:Data.png]][https://www.simplyzip.com/ SimplyZip] 

--[[User:Sprinter|Sprinter]] 20:13, 16 October 2008 (UTC)
--[[User:Novemberdobby|Novemberdobby]] 17:04, 4 November 2008 (UTC)

Call of Duty 4: Partial Fastfile Decompile

2008-11-04T17:04:06Z

Novemberdobby: added rawfile info

''Added By Sprinter''

[[Image:Unpack.png|center]]

[[Image:Data.png]][http://mh-nexus.de/en/hxd/ HxD] 
[[Image:Data.png]][https://www.simplyzip.com/ SimplyZip] 

This tutorial allows you to extract any file from a fastfile that was compressed using the rawfile,filename format. That includes:

.gsc (gametype script)
.txt (e.g gametype definitions file)
.script (e.g playeranim.script)
.vision (map/mod vision files)
.shock (shellshock files)
.atr (animtrees)

--[[User:Sprinter|Sprinter]] 20:13, 16 October 2008 (UTC)
--[[User:Novemberdobby|Novemberdobby]] 17:04, 4 November 2008 (UTC)

Call of Duty 5: Beta GSCRip

2008-10-29T13:50:17Z

Novemberdobby:

[[Category:Call of Duty 5 Beta]]
[[Category:Modding]]
''By NovemberDobby''

Here are the files I've been able to get out of the demo. Organised in folders by the names of the fastfiles, and I'll work on getting the csv's out too (challenge names and rank tables).

[[Image:dobby_rip.png|500px]]

Enjoy!
 
[[Image:Data.png]] [http://www.novemberdobby.com/files/rips/strings.txt Localised strings] 
[[Image:Data.png]] [http://wiki.modsrepository.com/codww_betafiles/WWrip.zip Rip#1] 
[[Image:Data.png]] [http://www.novemberdobby.com/files/rips/WWrip.zip MIRROR - been updated a few times]

Call of Duty 5: Beta GSCRip

2008-10-28T19:36:05Z

Novemberdobby: added strings file

''By NovemberDobby''

Here are the files I've been able to get out of the demo. Organised in folders by the names of the fastfiles, and I'll work on getting the csv's out too (challenge names and rank tables).

[[Image:dobby_rip.png|500px]]

Enjoy!

[http://www.novemberdobby.com/files/rips/strings.txt Localised strings]

[[Image:Data.png]] [http://wiki.modsrepository.com/codww_betafiles/WWrip.zip HERE] 
Mirror: 
[[Image:Data.png]] [http://www.novemberdobby.com/files/rips/WWrip.zip HERE]

Call of Duty 4: Custom Textures

2008-10-25T12:18:07Z

Novemberdobby:

[[Category:Call of Duty 4]]
[[Category:Modtools]]
[[Category:Radiant]]
[[Category:Advanced Editing]]
{{warning_forpro}}
''By NovemberDobbby''
[[Image:Nutshell.png]] This tutorial will show you how to add a new custom texture to the game, that can be used in Radiant.

[[Image:warning.png]] Custom textures will show as white unless you are running a mod, as textures must be stored in an IWD archive.
[[Image:rgn_warning.png|right]]
The game won't read custom IWD's at all unless a mod is running.

* First, you need a texture to work with. the compiler can use dds, tga, jpg, and jpeg extensions, NOT iwi's.

* Open the Cod4CompileTools, go to the Applications tab and launcher the Asset Manager.

* In Asset Manager's scrolling menu, go to material, and select new entry. Think of a name without any spaces, something which has meaning like vcod_snow_1.

* Make sure the material type 'world phong' is selected. It should be selected by default. Leave the 'sort' drop-down box on *default for now. Pick any surfaceType - this determines how your texture will react to bulllets hitting it and stuff (sounds/fx). 'Error' won't work, and picking 'none' is inadvisable.

* The Usage drop-down menu will be where you can find your texture in Radiant, when you go to Textures>Usage.

* In the 'locales' section, you can pick a 'folder' from which you'll be able to access the texture in Radiant's texture menu. (Textures>Locale>Name). You can pick as many of these as you want, or none. You dno't have to however, because you can still get to your texture through Textures>Usage.

* In the 'Color Map' option box, click the ellipses (...) button on the right of the text box. Navigate to your dds/jpg/tga texture and open it. You should put this texture in a \Call of Duty 4\subdirectory, for example, Call of Duty 4\source_data.

* If you have a Normal Map (makes it look 3d/bumpy) for your texture, click the ellipses next to the Normal Map box, and navigate to that file. It must be an uncompressed RGB format, such as a .tga.

* Go to File>Save, and put the GDT file in \Call of Duty 4\source_data. Give it any name, bearing in mind you will have to open this file again if you want to change/reconvert this texture.

Note: The .gdt will only compile from /source_data. Any other folder will just give a 'conversion complete' message.

* Go to PC Convert>Current Asset only, or hit F10. You only convert the current entry because you don't want to be converting every single stock asset that came with the mod tools.

'''You should see something like this:'''

[[Image:custom_669.png]]

[[Image:warning.png]] if there are any errors, do what it says.

It will only re-convert if you have changed the input texture filename, changed the texture itself, or any other option in Asset Manager.

You can now use your texture in Radiant, by finding it under your chosen materialType/usage. If your texture appears gritty at a distance, then open up the image editing program you used to save it in, and make sure Mipmaps are generated (and reconvert).

Distortion textures can be added by setting the materialType to distortion, and finding a colour map.

Call of Duty 4: Skinning

2008-10-24T13:59:19Z

Novemberdobby:

[[Image:Nutshell.png]] This tutorial will explain how to replace Stock Skins for any models in the game.

== Requirements ==
*Adobe Photoshop (or other graphics program that supports the DDS plugin)
*Winrar
*The [[Call of Duty 4: Skinning Tools|Skinning Tools]]
*Call of Duty 4 Modern Warfare

== Initial Setup ==
*Open up cod4_converters.zip and extract the dds.8bi file (DDS plugin) into adobe\photoshop\plug-ins\File Formats (If the plugin is not installed you will be unable to open or save a .dds file)

*Create a new folder on your desktop and call it “Skinning Tools”

*Copy the two converters (iwi2dds.exe and dds2iwi.exe) into this new folder

== File selection ==
Go to

Activision\Call of Duty 4 – Modern Warfare\main
In this folder you should see 14 IW_ files going from IW_00 up to IW_13 the skins are located inside IW_00 – IW_04 (IW_12 stores IWI files used in the map mp_crash_snow and IW_13 stores IWI files used in the 4 maps released in patch 1.6) if you open up these archives you will see a folder called “images” this is where the IWI files are stored.

The IWI image files have been compiled in alphabetical order:

IW_00.iwd contains files beginning with # to Ch
IW_01.iwd contains files beginning with Ch to Ma
IW_02.iwd contains files beginning with Ma to Sa
IW_03.iwd contains files beginning with Sa to Ve
IW_04.iwd contains files beginning with Ve to Z

*Once you have decided upon which file you are wanting to skin, extract it from the .iwd to your “Skinning Tools” folder you created earlier. This should create a folder inside there called “Images”.

== File Conversion 1==
Take the file from the folder “images” and drag and drop it onto the ''iwi2dds.exe'' file.

This will create a second file with an almost identical name however it will have _out.dds at the end of it.This file can now be edited in photoshop.

== File editing ==
Double click on the new file and it should open it in photoshop. When photoshop loads up a number of boxes may appear asking certain questions.

It may ask you to choose the size of the image if so choose “normal default sizes”

It may ask you if you would like to display MIP maps with the image, select “no” if this message appears

Now this is open you can edit the skin.

Useful tools to use in Photoshop for the editing are:

Opacity level
Eraser tool
Blending options
Magic Pen
Alpha Channels

== File Saving ==
Now that you have the file edited you now need to save it. To do this go to File > save as and then select to save as a .dds file.

*Once you have done that a window should appear asking you how you would like to save the .dds file. The only two options you should be interested in unless you are experienced with it are:

Save format
MIP Maps

*Save format should be set to DXT5 and MIP Maps should be set to Generate MIP Maps

*Once this is done click save in the bottom right corner of the window

== File Conversion 2 ==
Now you have your file saved and edited it is now time to convert the file back to an IWI file.

*To do this take your .dds file and drag and drop it onto dds2iwi.exe this will then produce a new file which is your new skin in a format that Call of Duty 4 can use

*Before you archive the file however you need to ensure that the name is correct. You should rename the file back to what it originally was called before you started to edit it. This will normally be something like “weapons_ak47_c.iwi”

== Archiving the file ==
To archieve the file and create a working skin you need to copy your newly renamed IWI file into activision\Call of Duty 4 – Modern Warfare\mods\Modwarfare\images then once thast is done you need to go into the modwarfare folder and double click the makemod icon.

This will create two files. One called mod.ff and another called modwarfare.iwd copy both of these files into a new mod folder (call it what you like so long as there are no spaces in the folder name)

== Checking the skins work ==
To check the skins work you now need to load up Call of Duty 4 Multiplayer and then on the Main Menu you need to select Mods and then find the folder name you chose and select it again.

When the mod screen loads, bring up the console ( ` key) and then run /devmap (map name e.g. mp_crash) to run the map in developer mode this will then allow you to change the viewpoint you see your skin at etc.

Call of Duty 4: Models imports

2008-10-24T13:54:25Z

Novemberdobby:

[[Category:Call of Duty 4]]
[[Category:Modtools]]
[[Category:Radiant]]
[[Category:Advanced Editing]]
[[Category:Import]]
[[Category:Modtools]]
{{warning_forpro}}
[[Image:rgn_warning.png|right]]
[[Image:Nutshell.png]] This tutorial will explain how you can import Call of Duty 2 models into Cod4 to use in your custom maps.

Result:

[[Image:jeep.jpg|500px]]

==Required==

First you will need a few programs:

*XModel Creator for CoD2 V0.6, get it [http://www.zeroy.com/br/other/cod4/tutorials/model_export/xmodel_Creator_v0.6.zip here]
*XModel Exporter V5.0.0.3, get it [http://www.diegologic.net/CoD/XmodelExporter.htm here]
*IrfanView, get it [http://www.irfanview.com here]

Note: the programs above are freely available.

*A legal copy of Call of Duty 2 by Activision

*Get Call of duty 2 installed on your PC and extract '''all''' the .iwd found in /main/ to \Call of Duty 2\raw (if raw folder isnt there then create it). Not sure if they are required but to be on the safe side install the Cod2 mod tools as well, get them [http://callofduty.filefront.com/file/CoD2_Updated_MapMod_Tools;61008 here]

Of course this also assume you have Call of Duty 4 [[Call of Duty 4: needed#Modtools|Modtools]] installed

==Exporting the chosen model to .OBJ==

A - Open XModel Exporter and point to \Call of Duty 2\raw\xmodels, a list of model will show up, pick the one you wish to import in Cod4

B - Export Material images as dds by clicking on each .iwi file in the three and using the "convert to DDS" button

Once done, you can pick the first model in list, its usually either _high or _lod10 and hit "Preview Surface" to see the textured model:

[[Image:importcod2_01.jpg|500px]]

C - When happy with the Model to export click the "Export .OBJ" Button

D - Keep XModel Exporter open on that same model as you will need it again later

==Convert Material(s) to .TGA==

A - Browse to \Call of Duty 2\raw\images and look for the most recent files modified you should find the newly converted .dds:

[[Image:importcod2_02.jpg|500px]]

B - Open the DDS files one at the time using IrFanview (if you converted more than one) and save the file as .TGA in \Call of Duty 4 - Modern Warfare\texture_assets (create texture_assets if not already there) NOTE: dont touch any options when saving as .TGA

C - Open up IW Cod4 Asset Manager and select material from drop down list and hit "New Entry", for the name it is VERY important to select the same as the original name used in Cod2 for the chosen Model, in my example its ''mtl_detail_lantern'' - Use Xmodel Exporter (still open) to double check ''mtl_ name''

Use the settings sen in screenshot below for each .tga you need to import in cod4, changing the Surface Type to appropriate in your case (Metal in my example):

[[Image:importcod2_03.jpg|500px]]

Once ready, hit F10 to convert the asset, repeat if there is more than one material to create (some models have several)

==Convert .OBJ back to xmodel_export==

A - Browse to \Call of Duty 2\raw\obj\ where you should find 3 files created earlier, in my case they are:

<pre>lantern_exterior_on_lod10.mtl
lantern_exterior_on_lod10.obj
light_lantern_on_tags.txt</pre>

Copy all 3 files over to \Call of Duty 4 - Modern Warfare\model_export\custom\ (create custom folder is not present)

B - Open XModel Creator (Midi file plays quite loud!) , in "input" browse and select the .obj in \Call of Duty 4 - Modern Warfare\model_export\custom\

Click "import" then "More options" and "Materials", you should see the previously created material on the left hand side. Finally hit the "export" button and close XModel Creator

==Convert xmodel_export to usuable textured Model==

A - Copy the folder \Call of Duty 4 - Modern Warfare\raw\physic\ and all its file into \Call of Duty 4 - Modern Warfare\share\main\ ( create \share\main first)

B - Open up the Asset Manager again but this time select xmodel from list and click "New Entry" select any name you want

On the left hand side window go and browse the newly created .modelexport file in \Call of Duty 4 - Modern Warfare\model_export\custom\ (in my example its lantern_exterior_on_lod10.xmodel_export), select the physic from list that suit the best to your model:

[[Image:importcod2_04.jpg|500px]]

Hit F10 when ready and everything going well the AssMan will convert your model without errors ;D

Et Voila! The model will now be accessible in COD4 Radiant, dont forget to add a clip for it or it will have no collision!

--[[User:Zeroy|Zeroy.]] 14:48, 21 October 2008 (UTC)

Call of Duty 4: Introduction

2008-10-23T23:42:53Z

Novemberdobby:

[[Category:Call of Duty 4]]
[[Category:Modding]]
Here is a very good tutorial on COD coding that my mate Danny Redford (hence - Drofder, as its Redford
backwards :))
wrote back in 2006, which is a succint introduction to a very complex thing. '''Tally;'''

[[Image:Code.png|left]]
'''By Drofder2004'''

Ok, this is my own guide for scripting, it is incomplete and lacks a lot of formatting (I will try and get round to that soon). It was written in 2.5 hours and contains a lot of basic and slightly advanced guides on several base topics. Some areas contain more detail than others depending on relevance and difficulty.

When I get more time, I will add to this guide. Once I have pretty much finished the majority of the guide I will provide several new scripts using several advanced functions.

This guide should be used as a small starting guide for people new to scripting, and reference for those who know some scripting. This will provide an insight into how script can improve the fun of maps, and hopefully will help answer questions for those who are stuck.

If you find any problems (be it wrong syntax, spelling or etc) then post.
If you want to request/criticise/compliment or whatever, again post.

Enjoy.

== [[Getting Started]] ==

This section will include several things you need to know before you start scripting.

[[Image:Nutshell.png]] All scripts are contained within simple text files that contain no formatting, so programs such as Word are not to be used. The file format used for scripts within the Call of Duty series is 'GSC' (.gsc). It is recommended you use a simple but effective editor for programming, such programs include [http://www.crimsoneditor.com/ Crimson Editor], [http://http://www.pnotepad.org/ Programmers Notepad] and [http://www.editplus.com/ Editplus].

A few things you need to know before reading any further are a few common words used within scripting.

'''Variables:''' variables are data storage locations which are assigned a name. For example...
<pre>
integerthing = 1; //by the way, comments like this can be made using //, and are ignored by the game.
floatthing = 0.5;
stringthing = "Text and symbols 1234567890";
booleanthing = true; //another thing, almost every line must have a ; at the end or the script won't work. More on that later.
</pre>
The variables are declared on the left, and assigned a value such as an integer (whole number), a float (a number containing a decimal), a string (text and symbols) or a boolean (true/false).

'''Entities:''' These are objects that are used in maps, and can be referenced in the script. Entities include players, dropped guns, objectives, script_models, etc.

They can be referenced using their their targetname or classname that has been set within the map.

'''Functions:''' an action or procedure that can be called or threaded and can return a value. For example...
<pre>
funcMove()
{
self moveY(320, 3);
}
</pre>
The main function in the above code is '''funcMove()''', and it will perform the actions inside the curly braces when it runs. There is also another function, '''moveY''', which is a built-in function inside COD4, and moves an entity on the Y axis.

'''Arguements:''' These are key piece of information that are passed along to functions, and can be any type of object (entity, string, boolean etc). The function that was passed the arguments can then reference them.

For example, if a function is shown as
<pre>
function(arg1, arg2)
</pre>
The function is asking for two arguements to be sent to the function. An example of this in use...
<pre>
someotherstuff()
{
ent function(320, 5);
thing function(320, 5);
}

function(distance, time)
{
ent moveZ(distance, time);
}
</pre>
As you can see, function() is called on both 'ent' and 'thing', and the two arguments '320' and '5' are passed to the new function as 'distance' and 'time'. Then moveZ is called on the entities.

'''Calling/Threading:''' these are used with functions. Functions can be threaded or called sequentially.

If a function is threaded, then that function is performed while the script continues, whereas if a function is called sequentially, the script waits until the function is completed before it continues. Examples...
<pre>
function(); //the script will stop at this line and carry out function() before going down to...
thread function(); //this will start function() and carry on to execute 'ent moveZ'
ent moveZ(350, 5);
</pre>
'''Self:''' If you call a function on an entity e.g 'unnamedent thread dostuff()', then within the function dostuff(), you can refer to unnamedent as 'self'.

For example...
<pre>
something()
{
ent = getent("ent","targetname");
ent function();
}

function()
{
self moveZ(150, 5);
}
</pre>
== [[Using Variables]] ==

[[Image:Nutshell.png]] Variables can be used in several ways, but in all cases they are used to store some data for the duration of the game. Variables come in different forms: integers, floats, entities, strings, arrays and booleans, there are also several different ways variables can be stored.

A simple variable is simply declared using

variable = data;

This variable can be used in the current function and any function that passes it as an argument, or is called on it (so it'd be used as 'self').

Variables can be global (which can be used in all threads without needing to be called) by using the

level.variable = data;

or they can be assigned to entities individually

entity.variable = data;

for things like player.health (integer, already built-in, but can be modified) and level.teamBased (boolean).

== [[Maths & Operators]] ==

[[Image:Nutshell.png]] Maths is used throughout scripting to get many different values, be it the distance between two objects or to calculate an equation.

For example, a variable can be given data from an equation.

variable = 5 + 1;

Although the above example is pretty pointless, as it adds one constant to another to make a constant, and you can just calculate it yourself and use the answer i.e.

variable = 6;

But variables can be calculated using other variables, for example...

varAnswer = var1 + var2;

varAnswer will be equal to the value of var1 plus the value of var2.

There are several operators that can be used in maths...
<pre>
+ :: Addition
- :: Subtraction
* :: Multiplication
/ :: Division
% :: Modulus
= :: Equals
</pre>
There are also some more little-known operators such as...
<pre>
++ :: Increment (+1)
-- :: Decrement (-1)
+= :: Incrementation (requires number)
-= :: Decrementation (requires number)
</pre>
Example of these in use...
<pre>
var++; //Set var to var + 1
var--; //Set var to var - 1
var += int; //Set var to var + int
var -= int; //Set var to var - int
</pre>
== [[IFs, Loops & Logic]] ==

[[Image:Nutshell.png]] This section will go into a little more detail of how to use 'if' statements and loops.

An 'if' statement is used to verify whether some data satisfies certain conditions, and then to execute code depending on the outcome.

To understand this section, you must first know the operators used to compare data:

<pre>
== :: Equal To
!= :: Not Equal To
! :: Negation (Not equal to)
< :: Less than
> :: Greater than
<= :: Less or Equal to
>= :: Greater or Equal to
&& :: And
|| :: Or
</pre>

Ok, now that we have some operators, lets get started on the statement.

An 'if' statement, requires a minimum of one arguement and usually one operator.

Here are some examples...notice the lack of semicolons at the end of the statements.
<pre>
if(variable) //If variable is true
if(!variable) //If variable is not true
if(variable1 == variable2) //If variable1 is equal to variable2
if(variable1 != variable2) //If variable1 is not equal to variable2
if(integer1 < integer2) //If integer1 is less than integer2
if(integer1 > integer2) //If integer1 is greater than integer2
if(integer1 <= integer2) //If integer1 is less than or equal to integer2
if(integer1 >= integer2) //If integer1 is greater or equal to integer2
if((var1 == var2) && (var3 != var4)) //If var1 is equal to var2 AND var3 is not equal to var4
if((int1 > int2) || (var1 == var2)) //If int1 is greater than int2 OR var1 is equal to var2
</pre>
To use an if statement to determine the movement of the script, you need to use the arguements to move the script in certain directions...
<pre>
if(var1 == var2)
{
//if var1 equals var2, do this code
//everything inside these curly braces
}
//then do this code regardless of the result
</pre>

If the statement above is true, the code inside the curly brackets is processed, if it is not true, the code inside the brackets are skipped.

Whether or not the statement is true, the code outside of the brackets is going to be processed. If this is not what you want, you need to use "Else" after the statement, for example...
<pre>
if(var1 == var2)
{
//if it's true then do this
}
else
{
//if it's false then do this
}
</pre>
You can also use an "else if" in the statement. This is used in a scenario where you want to check multiple comparisons.
<pre>
if(var1 == var2)
{
//if above arguement is true
}
else if(!var1 && var3)
{
//if var1 is false but var3 is true
}
else
{
//if all other if statements were false
}
</pre>
Thats the basics of if's, so let move on to loops.

Loops come in different forms...

'''While''' :: A while loop is a loop that keeps looping WHILE the arguement is true.
'''For''' :: A for loop is a loop that loops a set amount of times

To use a while loop, a condition/some conditions must be stated: "while(conditions)"
Often, this loop is used for infinite loops, which last forever unless specifically stopped. This is done using the arguement of 1 or true (1 is the integer of true)

while(1)
while(true)

A while loop can also be used as a normal loop that loops while the arguement is true, when the arguement becomes false the loop exits automatically (or rather, doesn't begin executing the commands in the loop again but just finishes the loop in progress).
<pre>
int = 0;

while(int < 10)
{
wait 1;
int++;
}
</pre>
The above code will loop while 'int' is less than 10. The loop waits 1 second, and then the loop increments 'int'. Once 'int' is not less than 10, the loop breaks.

The same applies for FOR loops.

A FOR loop requires 3 arguements.

for(declare; while; do)

'''Declare''' is the section which declares a variable for the loop to use.

'''While''' is what determines when the loop breaks

'''Do''' is what the loop should do after each loop.

A common FOR loop looks like this...
<pre>
for(i = 0; i < int; i++)
</pre>
The above code means: (i is 0, while i is smaller than int, add one to i).

Let's replace int with an actual number:
<pre>
for(i = 0; i < 10; i++)
{
wait 1;
thread function();
}
</pre>
This is the sequence of events...

- 'i' = 0
- while i is less than 10, continue the loop
- perform code (wait 1; and function())
- increment 'i' (i++)

The FOR loop can also be used as an "infinite loop" using the "forever loop"

for(;;)

The above will simply keep repeating the code until manually terminated.

The problem with infinite loops is that they will give you an error if you don't allow them to pause at any point - so all infinite loops require a wait statement somewhere in the executed code.

To finish off, we need to know how to manually exit these loops. A common way to exit an infinite loop is to use an IF statement to determine when to 'break' (break is the keyword used to exit a loop) - here is an example of an IF statement breaking an infinite loop...
<pre>
for(;;)
{
wait 1;
if(var1 == var2)
{
break;
}
}
</pre>
The above sequence simply goes...

- wait 1 second
- check if statement...
- if var1 is equal to var2, break out of the loop
- else continue the loop

== [[Creating Functions]] ==

[[Image:Nutshell.png]] A custom function is a good way to use repeat sections of code more efficiently. For example, if you often use the same sequence of code, you can template them into a custom function. Imagine this is your code...
<pre>
{
wait 1;
brush1 moveZ(320, 5);
brush1 waittill("movedone");
wait 1;
brush2 moveZ(540, 3);
brush2 waittill("movedone");
}
</pre>
This can be simplified using a custom function, lets call this function "_moveEnt" (it is common practice to use an underscore as the first character of a function)

_moveEnt(ent, dist, time)

As the above shows, we are going to need 3 arguements, ent (entity), dist (distance) and time.

Now lets look at the full code with custom function in use...
<pre>
{
_moveEnt(brush1, 320, 5);
_moveEnt(brush2, 540, 3);
}

_moveEnt(ent, dist, time)
{
wait 1;
ent moveZ(dist, time);
ent waittill("movedone");
}
</pre>
As the above code shows, the custom function can simply be called using the required arguements, which are passed along and used in the new function.

Once the custom function has finished, the script returns to the original location from where it was called.

Functions can also return values to the original script, or even entities.

A simple function to calculate volume from the width, height and depth:
<pre>
{
area = _areaEquation(2, 4, 6);
}

_areaEquation(x, y, z)
{
answer = x * y * z;
return answer;
}
</pre>
Once the code calls the function '_areaEquation' the function works out the 'answer', 'answer' is the returned.
This declares a new variable (area). The variable area, is the answer that is returned by the function.

The two lines:

answer = x * y * z;
return answer;

could be replace by

return x * y * z;

for the same effect.

== [[Arrays]] ==

[[Image:Nutshell.png]] Arrays are objects that store several variables. These can be integers, strings, entities or even other arrays.

Arrays are extremely helpful when it comes to doing the same thing to several different objects, such as moving a few platforms by a certain amount in a map, or storing lots of related variables.

To create an array we simply type...
<pre>
arrayName = [];
</pre>
Now, to add an object/variable to this array, we can simply use:
<pre>
array(array.size) = "a string variable";
</pre>
Whenever you see array.size, the .size does not mean it's dimensions, but the amount of items in the array. So if an array contains 1 piece of data, the array.size is 1. To retrieve an items from an array, you can use array[0] for the first object/var stored in it, and then array[1] and so on for successive items.

Going back to the example above, we could retrieve the data by using array[0]. The first item in an array is listed as 0, the second as 1, and so on. This means that by using array(array.size) = "blah";, we can add new items to it because of the offset of 1.

A common use for an array is to call a function on all of the players in the game. This can be done by using an array with a FOR loop.
To start with we must get our array of players, and instead of using the above method of defining an array and adding custom data, we can use a builtin function.

players = getEntArray("player", "classname");

So, our array has been defined as "players", or more accurately, "players[]".

Inside "players[]" is every player on the server, and now all we need to do is use the array to thread a function to each player.
So, here we have a for loop to do such a thing:
<pre>
for(i = 0; i < players.size; i++)
{
players[i] thread function();
}
</pre>
That's our loop to go through every player and call function(); on them.

Remember, 'i' is a variable not a letter, so 'i' is substitued with the number of the loop.
In the first loop, 'i' equals 0, so:

players[0] thread function();

is executed.

Arrays are a complicated part of scripting, but once you have them understood, they are one of the most useful things in the game.

== [[Switch]] ==

[[Image:Nutshell.png]] Switch is often used instead of multiple if statements, as it is more efficient and doesn't require you to type as much.

''How to use "Switch".''

Switch can be quite hard to understand at first glance, but after using it, it will become easier.

Here is an example of how it is used. This is taken from the menu scripts, which handles the ingame menus, I have cut the code and also added the commented lines myself.
<pre>
self waittill("menuresponse", menu, response);

switch(response)
{

case "changeweapon":
self closeMenu();
self closeInGameMenu();
if(self.pers["team"] == "allies")
self openMenu(game["menu_weapon_allies"]);
else if(self.pers["team"] == "axis")
self openMenu(game["menu_weapon_axis"]);
break;

case "changeteam":
self closeMenu();
self closeInGameMenu();
self openMenu(game["menu_team"]);
break;

case "muteplayer":
self closeMenu();
self closeInGameMenu();
self openMenu(game["menu_muteplayer"]);
break;

case "callvote":
self closeMenu();
self closeInGameMenu();
self openMenu(game["menu_callvote"]);
break;

default:
//add default action here
break;
}
</pre>
The first part of the code is where the variable is defined. The game waits until a menu has been activated. The variables recieved are "menu" (the name of the menu activated) and "response" (what option was chosen from the menu). "Response" is the key variable for the 'Switch'.

After the variables have been defined, the Switch function is called. It then checks every "Case" (case is the term used for the possible outcomes of the variable) to find a match, if no match is found, the "Default" case is used. (if you do not have a default case, the script will crash - you can just add an empty one.)

If a match is found, then the function will do ALL the events from that point onwards, which is why you MUST add "break;" at the end of every case, if the break is not existent, then all other case functions will run also.

To use the above example, I shall input my own values to show how the example works...

When I open the menu ingame, I choose the option "changeteam".
The code kicks in and the variable "response" becomes equal to "changeteam".
The switch statement will now look at every case for a positive match.

Once the match is found, everything after the case will happen:
* self closeMenu(); //current menu closes
* self closeInGameMenu(); //close any other ingame menus
* self openMenu(game["menu_team"]); //will open the team menu
* break; //the rest of the switch statement is ended and the code continues

You can also make the script perform the same actions in multiple cases. For example:
<pre>
self waittill("menuresponse", menu, response);

switch(response)
{

case "changeweapon":
case "changeteam":
case "muteplayer":
case "callvote":
function();
break;

default:
//add default action here
break;
}
</pre>
This means that if the response variable is: 'changeweapon', 'changeteam', 'muteplayer' or 'callvote', function(); will be called.

== [[Notify / Endon / Waittill]] ==

[[Image:Nutshell.png]] These 3 functions allow you to make a script wait for specific events and then trigger those events in different parts of the scripts.

This one ends the function it is inside when 'thread_restart' is triggered on 'level':

level endon ("thread_restart");

and this triggers the 'killed_player' notification on 'self' (which is a player in this case):

self notify("killed_player");

If you use 'player waittill("x")' or 'player endon("x")', then using a 'level notify("x")' will not trigger either of them - level is not the same entity as player, and all entities' triggers are independant.

Using the functions is easy. Firstly, decide which entity you want to wait for the trigger on. This is a player most of the time, but if you want a global trigger then use 'level'.

Then you must decide which trigger to use. You can choose either "endon" or "waittill" - they are both self explanatory, one will end the function it is running in when triggered, and the other will 'wait' until the specified trigger.

----

Next you decide on a unique name for the trigger. For example...

level endon("a_unique_call");

And to activate this trigger, you use notify on the same entity (level):

level notify("a_unique_call");

You can use as many waittill and endon functions as you want on an entity, in different functions. They will all be triggered by a notify.

Here is a quick example of it in use in multiple threads in the DM gametype...
<pre>
spawnPlayer()
{
self notify("spawned");

/*... Code snipped ... this is another type of
comment that can span multiple lines. */

}

Callback_PlayerKilled(attacker, some other arguments)
{
self endon("spawned"); //this makes callback_playerkilled() terminate when "spawned" is triggered in spawnplayer().
}
</pre>

== [[Scripting hints]] ==

A few useful commands:

To print a large message on the screen:

'''iprintlnbold(stringMessage);'''
or to a specific player:
'''player iprintlnbold(stringMessage);'''

To print a small message on the bottom left of the screen:

'''iprintln(stringMessage);
same as iprintlnbold() to a specific player

To check whether a variable or entity exists:

'''if(isdefined(timetowait))'''
'''wait (timetowait);'''

You can also use functions in if statements, by the returned value:
<pre>
if(checksomething())
//code here

checksomething()
{
if(var == "hi there!") //remember to use == in if statements to check equality, but var1 = var2 to set equality outside them.
return true;
else
return false;
}
</pre>

--[[User:Novemberdobby|Novemberdobby]] 23:42, 23 October 2008 (UTC)

== Sources ==

[[Image:Geographylogo.png]][http://www.codjumper.com/forums/viewtopic.php?t=4011&sid=ed58d3b3f5bfa32350d4670d35c9f781 From CoDJumper.com]

Scripting hints

2008-10-23T23:42:13Z

Novemberdobby:

== [[Scripting hints]] ==

A few useful commands:

To print a large message on the screen:

'''iprintlnbold(stringMessage);'''
or to a specific player:
'''player iprintlnbold(stringMessage);'''

To print a small message on the bottom left of the screen:

'''iprintln(stringMessage);
same as iprintlnbold() to a specific player

To check whether a variable or entity exists:

'''if(isdefined(timetowait))'''
'''wait (timetowait);'''

You can also use functions in if statements, by the returned value:
<pre>
if(checksomething())
//code here

checksomething()
{
if(var == "hi there!") //remember to use == in if statements to check equality, but var1 = var2 to set equality outside them.
return true;
else
return false;
}
</pre>

--[[User:Novemberdobby|Novemberdobby]] 23:42, 23 October 2008 (UTC)

Scripting hints

2008-10-23T23:41:19Z

Novemberdobby: New page: == Scripting hints == A few useful commands: To print a large message on the screen: '''iprintlnbold(stringMessage);''' or to a specific player: '''player iprintlnbold(stringMessage...

Call of Duty 4: Introduction

2008-10-23T23:41:08Z

Novemberdobby:

[[Category:Call of Duty 4]]
[[Category:Modding]]
Here is a very good tutorial on COD coding that my mate Danny Redford (hence - Drofder, as its Redford
backwards :))
wrote back in 2006, which is a succint introduction to a very complex thing. '''Tally;'''

[[Image:Code.png|left]]
'''By Drofder2004'''

Ok, this is my own guide for scripting, it is incomplete and lacks a lot of formatting (I will try and get round to that soon). It was written in 2.5 hours and contains a lot of basic and slightly advanced guides on several base topics. Some areas contain more detail than others depending on relevance and difficulty.

When I get more time, I will add to this guide. Once I have pretty much finished the majority of the guide I will provide several new scripts using several advanced functions.

This guide should be used as a small starting guide for people new to scripting, and reference for those who know some scripting. This will provide an insight into how script can improve the fun of maps, and hopefully will help answer questions for those who are stuck.

If you find any problems (be it wrong syntax, spelling or etc) then post.
If you want to request/criticise/compliment or whatever, again post.

Enjoy.

== [[Getting Started]] ==

This section will include several things you need to know before you start scripting.

[[Image:Nutshell.png]] All scripts are contained within simple text files that contain no formatting, so programs such as Word are not to be used. The file format used for scripts within the Call of Duty series is 'GSC' (.gsc). It is recommended you use a simple but effective editor for programming, such programs include [http://www.crimsoneditor.com/ Crimson Editor], [http://http://www.pnotepad.org/ Programmers Notepad] and [http://www.editplus.com/ Editplus].

A few things you need to know before reading any further are a few common words used within scripting.

'''Variables:''' variables are data storage locations which are assigned a name. For example...
<pre>
integerthing = 1; //by the way, comments like this can be made using //, and are ignored by the game.
floatthing = 0.5;
stringthing = "Text and symbols 1234567890";
booleanthing = true; //another thing, almost every line must have a ; at the end or the script won't work. More on that later.
</pre>
The variables are declared on the left, and assigned a value such as an integer (whole number), a float (a number containing a decimal), a string (text and symbols) or a boolean (true/false).

'''Entities:''' These are objects that are used in maps, and can be referenced in the script. Entities include players, dropped guns, objectives, script_models, etc.

They can be referenced using their their targetname or classname that has been set within the map.

'''Functions:''' an action or procedure that can be called or threaded and can return a value. For example...
<pre>
funcMove()
{
self moveY(320, 3);
}
</pre>
The main function in the above code is '''funcMove()''', and it will perform the actions inside the curly braces when it runs. There is also another function, '''moveY''', which is a built-in function inside COD4, and moves an entity on the Y axis.

'''Arguements:''' These are key piece of information that are passed along to functions, and can be any type of object (entity, string, boolean etc). The function that was passed the arguments can then reference them.

For example, if a function is shown as
<pre>
function(arg1, arg2)
</pre>
The function is asking for two arguements to be sent to the function. An example of this in use...
<pre>
someotherstuff()
{
ent function(320, 5);
thing function(320, 5);
}

function(distance, time)
{
ent moveZ(distance, time);
}
</pre>
As you can see, function() is called on both 'ent' and 'thing', and the two arguments '320' and '5' are passed to the new function as 'distance' and 'time'. Then moveZ is called on the entities.

'''Calling/Threading:''' these are used with functions. Functions can be threaded or called sequentially.

If a function is threaded, then that function is performed while the script continues, whereas if a function is called sequentially, the script waits until the function is completed before it continues. Examples...
<pre>
function(); //the script will stop at this line and carry out function() before going down to...
thread function(); //this will start function() and carry on to execute 'ent moveZ'
ent moveZ(350, 5);
</pre>
'''Self:''' If you call a function on an entity e.g 'unnamedent thread dostuff()', then within the function dostuff(), you can refer to unnamedent as 'self'.

For example...
<pre>
something()
{
ent = getent("ent","targetname");
ent function();
}

function()
{
self moveZ(150, 5);
}
</pre>
== [[Using Variables]] ==

[[Image:Nutshell.png]] Variables can be used in several ways, but in all cases they are used to store some data for the duration of the game. Variables come in different forms: integers, floats, entities, strings, arrays and booleans, there are also several different ways variables can be stored.

A simple variable is simply declared using

variable = data;

This variable can be used in the current function and any function that passes it as an argument, or is called on it (so it'd be used as 'self').

Variables can be global (which can be used in all threads without needing to be called) by using the

level.variable = data;

or they can be assigned to entities individually

entity.variable = data;

for things like player.health (integer, already built-in, but can be modified) and level.teamBased (boolean).

== [[Maths & Operators]] ==

[[Image:Nutshell.png]] Maths is used throughout scripting to get many different values, be it the distance between two objects or to calculate an equation.

For example, a variable can be given data from an equation.

variable = 5 + 1;

Although the above example is pretty pointless, as it adds one constant to another to make a constant, and you can just calculate it yourself and use the answer i.e.

variable = 6;

But variables can be calculated using other variables, for example...

varAnswer = var1 + var2;

varAnswer will be equal to the value of var1 plus the value of var2.

There are several operators that can be used in maths...
<pre>
+ :: Addition
- :: Subtraction
* :: Multiplication
/ :: Division
% :: Modulus
= :: Equals
</pre>
There are also some more little-known operators such as...
<pre>
++ :: Increment (+1)
-- :: Decrement (-1)
+= :: Incrementation (requires number)
-= :: Decrementation (requires number)
</pre>
Example of these in use...
<pre>
var++; //Set var to var + 1
var--; //Set var to var - 1
var += int; //Set var to var + int
var -= int; //Set var to var - int
</pre>
== [[IFs, Loops & Logic]] ==

[[Image:Nutshell.png]] This section will go into a little more detail of how to use 'if' statements and loops.

An 'if' statement is used to verify whether some data satisfies certain conditions, and then to execute code depending on the outcome.

To understand this section, you must first know the operators used to compare data:

<pre>
== :: Equal To
!= :: Not Equal To
! :: Negation (Not equal to)
< :: Less than
> :: Greater than
<= :: Less or Equal to
>= :: Greater or Equal to
&& :: And
|| :: Or
</pre>

Ok, now that we have some operators, lets get started on the statement.

An 'if' statement, requires a minimum of one arguement and usually one operator.

Here are some examples...notice the lack of semicolons at the end of the statements.
<pre>
if(variable) //If variable is true
if(!variable) //If variable is not true
if(variable1 == variable2) //If variable1 is equal to variable2
if(variable1 != variable2) //If variable1 is not equal to variable2
if(integer1 < integer2) //If integer1 is less than integer2
if(integer1 > integer2) //If integer1 is greater than integer2
if(integer1 <= integer2) //If integer1 is less than or equal to integer2
if(integer1 >= integer2) //If integer1 is greater or equal to integer2
if((var1 == var2) && (var3 != var4)) //If var1 is equal to var2 AND var3 is not equal to var4
if((int1 > int2) || (var1 == var2)) //If int1 is greater than int2 OR var1 is equal to var2
</pre>
To use an if statement to determine the movement of the script, you need to use the arguements to move the script in certain directions...
<pre>
if(var1 == var2)
{
//if var1 equals var2, do this code
//everything inside these curly braces
}
//then do this code regardless of the result
</pre>

If the statement above is true, the code inside the curly brackets is processed, if it is not true, the code inside the brackets are skipped.

Whether or not the statement is true, the code outside of the brackets is going to be processed. If this is not what you want, you need to use "Else" after the statement, for example...
<pre>
if(var1 == var2)
{
//if it's true then do this
}
else
{
//if it's false then do this
}
</pre>
You can also use an "else if" in the statement. This is used in a scenario where you want to check multiple comparisons.
<pre>
if(var1 == var2)
{
//if above arguement is true
}
else if(!var1 && var3)
{
//if var1 is false but var3 is true
}
else
{
//if all other if statements were false
}
</pre>
Thats the basics of if's, so let move on to loops.

Loops come in different forms...

'''While''' :: A while loop is a loop that keeps looping WHILE the arguement is true.
'''For''' :: A for loop is a loop that loops a set amount of times

To use a while loop, a condition/some conditions must be stated: "while(conditions)"
Often, this loop is used for infinite loops, which last forever unless specifically stopped. This is done using the arguement of 1 or true (1 is the integer of true)

while(1)
while(true)

A while loop can also be used as a normal loop that loops while the arguement is true, when the arguement becomes false the loop exits automatically (or rather, doesn't begin executing the commands in the loop again but just finishes the loop in progress).
<pre>
int = 0;

while(int < 10)
{
wait 1;
int++;
}
</pre>
The above code will loop while 'int' is less than 10. The loop waits 1 second, and then the loop increments 'int'. Once 'int' is not less than 10, the loop breaks.

The same applies for FOR loops.

A FOR loop requires 3 arguements.

for(declare; while; do)

'''Declare''' is the section which declares a variable for the loop to use.

'''While''' is what determines when the loop breaks

'''Do''' is what the loop should do after each loop.

A common FOR loop looks like this...
<pre>
for(i = 0; i < int; i++)
</pre>
The above code means: (i is 0, while i is smaller than int, add one to i).

Let's replace int with an actual number:
<pre>
for(i = 0; i < 10; i++)
{
wait 1;
thread function();
}
</pre>
This is the sequence of events...

- 'i' = 0
- while i is less than 10, continue the loop
- perform code (wait 1; and function())
- increment 'i' (i++)

The FOR loop can also be used as an "infinite loop" using the "forever loop"

for(;;)

The above will simply keep repeating the code until manually terminated.

The problem with infinite loops is that they will give you an error if you don't allow them to pause at any point - so all infinite loops require a wait statement somewhere in the executed code.

To finish off, we need to know how to manually exit these loops. A common way to exit an infinite loop is to use an IF statement to determine when to 'break' (break is the keyword used to exit a loop) - here is an example of an IF statement breaking an infinite loop...
<pre>
for(;;)
{
wait 1;
if(var1 == var2)
{
break;
}
}
</pre>
The above sequence simply goes...

- wait 1 second
- check if statement...
- if var1 is equal to var2, break out of the loop
- else continue the loop

== [[Creating Functions]] ==

[[Image:Nutshell.png]] A custom function is a good way to use repeat sections of code more efficiently. For example, if you often use the same sequence of code, you can template them into a custom function. Imagine this is your code...
<pre>
{
wait 1;
brush1 moveZ(320, 5);
brush1 waittill("movedone");
wait 1;
brush2 moveZ(540, 3);
brush2 waittill("movedone");
}
</pre>
This can be simplified using a custom function, lets call this function "_moveEnt" (it is common practice to use an underscore as the first character of a function)

_moveEnt(ent, dist, time)

As the above shows, we are going to need 3 arguements, ent (entity), dist (distance) and time.

Now lets look at the full code with custom function in use...
<pre>
{
_moveEnt(brush1, 320, 5);
_moveEnt(brush2, 540, 3);
}

_moveEnt(ent, dist, time)
{
wait 1;
ent moveZ(dist, time);
ent waittill("movedone");
}
</pre>
As the above code shows, the custom function can simply be called using the required arguements, which are passed along and used in the new function.

Once the custom function has finished, the script returns to the original location from where it was called.

Functions can also return values to the original script, or even entities.

A simple function to calculate volume from the width, height and depth:
<pre>
{
area = _areaEquation(2, 4, 6);
}

_areaEquation(x, y, z)
{
answer = x * y * z;
return answer;
}
</pre>
Once the code calls the function '_areaEquation' the function works out the 'answer', 'answer' is the returned.
This declares a new variable (area). The variable area, is the answer that is returned by the function.

The two lines:

answer = x * y * z;
return answer;

could be replace by

return x * y * z;

for the same effect.

== [[Arrays]] ==

[[Image:Nutshell.png]] Arrays are objects that store several variables. These can be integers, strings, entities or even other arrays.

Arrays are extremely helpful when it comes to doing the same thing to several different objects, such as moving a few platforms by a certain amount in a map, or storing lots of related variables.

To create an array we simply type...
<pre>
arrayName = [];
</pre>
Now, to add an object/variable to this array, we can simply use:
<pre>
array(array.size) = "a string variable";
</pre>
Whenever you see array.size, the .size does not mean it's dimensions, but the amount of items in the array. So if an array contains 1 piece of data, the array.size is 1. To retrieve an items from an array, you can use array[0] for the first object/var stored in it, and then array[1] and so on for successive items.

Going back to the example above, we could retrieve the data by using array[0]. The first item in an array is listed as 0, the second as 1, and so on. This means that by using array(array.size) = "blah";, we can add new items to it because of the offset of 1.

A common use for an array is to call a function on all of the players in the game. This can be done by using an array with a FOR loop.
To start with we must get our array of players, and instead of using the above method of defining an array and adding custom data, we can use a builtin function.

players = getEntArray("player", "classname");

So, our array has been defined as "players", or more accurately, "players[]".

Inside "players[]" is every player on the server, and now all we need to do is use the array to thread a function to each player.
So, here we have a for loop to do such a thing:
<pre>
for(i = 0; i < players.size; i++)
{
players[i] thread function();
}
</pre>
That's our loop to go through every player and call function(); on them.

Remember, 'i' is a variable not a letter, so 'i' is substitued with the number of the loop.
In the first loop, 'i' equals 0, so:

players[0] thread function();

is executed.

Arrays are a complicated part of scripting, but once you have them understood, they are one of the most useful things in the game.

== [[Switch]] ==

[[Image:Nutshell.png]] Switch is often used instead of multiple if statements, as it is more efficient and doesn't require you to type as much.

''How to use "Switch".''

Switch can be quite hard to understand at first glance, but after using it, it will become easier.

Here is an example of how it is used. This is taken from the menu scripts, which handles the ingame menus, I have cut the code and also added the commented lines myself.
<pre>
self waittill("menuresponse", menu, response);

switch(response)
{

case "changeweapon":
self closeMenu();
self closeInGameMenu();
if(self.pers["team"] == "allies")
self openMenu(game["menu_weapon_allies"]);
else if(self.pers["team"] == "axis")
self openMenu(game["menu_weapon_axis"]);
break;

case "changeteam":
self closeMenu();
self closeInGameMenu();
self openMenu(game["menu_team"]);
break;

case "muteplayer":
self closeMenu();
self closeInGameMenu();
self openMenu(game["menu_muteplayer"]);
break;

case "callvote":
self closeMenu();
self closeInGameMenu();
self openMenu(game["menu_callvote"]);
break;

default:
//add default action here
break;
}
</pre>
The first part of the code is where the variable is defined. The game waits until a menu has been activated. The variables recieved are "menu" (the name of the menu activated) and "response" (what option was chosen from the menu). "Response" is the key variable for the 'Switch'.

After the variables have been defined, the Switch function is called. It then checks every "Case" (case is the term used for the possible outcomes of the variable) to find a match, if no match is found, the "Default" case is used. (if you do not have a default case, the script will crash - you can just add an empty one.)

If a match is found, then the function will do ALL the events from that point onwards, which is why you MUST add "break;" at the end of every case, if the break is not existent, then all other case functions will run also.

To use the above example, I shall input my own values to show how the example works...

When I open the menu ingame, I choose the option "changeteam".
The code kicks in and the variable "response" becomes equal to "changeteam".
The switch statement will now look at every case for a positive match.

Once the match is found, everything after the case will happen:
* self closeMenu(); //current menu closes
* self closeInGameMenu(); //close any other ingame menus
* self openMenu(game["menu_team"]); //will open the team menu
* break; //the rest of the switch statement is ended and the code continues

You can also make the script perform the same actions in multiple cases. For example:
<pre>
self waittill("menuresponse", menu, response);

switch(response)
{

case "changeweapon":
case "changeteam":
case "muteplayer":
case "callvote":
function();
break;

default:
//add default action here
break;
}
</pre>
This means that if the response variable is: 'changeweapon', 'changeteam', 'muteplayer' or 'callvote', function(); will be called.

== [[Notify / Endon / Waittill]] ==

[[Image:Nutshell.png]] These 3 functions allow you to make a script wait for specific events and then trigger those events in different parts of the scripts.

This one ends the function it is inside when 'thread_restart' is triggered on 'level':

level endon ("thread_restart");

and this triggers the 'killed_player' notification on 'self' (which is a player in this case):

self notify("killed_player");

If you use 'player waittill("x")' or 'player endon("x")', then using a 'level notify("x")' will not trigger either of them - level is not the same entity as player, and all entities' triggers are independant.

Using the functions is easy. Firstly, decide which entity you want to wait for the trigger on. This is a player most of the time, but if you want a global trigger then use 'level'.

Then you must decide which trigger to use. You can choose either "endon" or "waittill" - they are both self explanatory, one will end the function it is running in when triggered, and the other will 'wait' until the specified trigger.

----

Next you decide on a unique name for the trigger. For example...

level endon("a_unique_call");

And to activate this trigger, you use notify on the same entity (level):

level notify("a_unique_call");

You can use as many waittill and endon functions as you want on an entity, in different functions. They will all be triggered by a notify.

Here is a quick example of it in use in multiple threads in the DM gametype...
<pre>
spawnPlayer()
{
self notify("spawned");

/*... Code snipped ... this is another type of
comment that can span multiple lines. */

}

Callback_PlayerKilled(attacker, some other arguments)
{
self endon("spawned"); //this makes callback_playerkilled() terminate when "spawned" is triggered in spawnplayer().
}
</pre>

== [[Scripting hints]] ==

A few useful commands:

To print a large message on the screen:

'''iprintlnbold(stringMessage);'''
or to a specific player:
'''player iprintlnbold(stringMessage);'''

To print a small message on the bottom left of the screen:

'''iprintln(stringMessage);
same as iprintlnbold() to a specific player

To check whether a variable or entity exists:

'''if(isdefined(timetowait))'''
'''wait (timetowait);'''

You can also use functions in if statements, by the returned value:
<pre>
if(checksomething())
//code here

checksomething()
{
if(var == "hi there!") //remember to use == in if statements to check equality, but var1 = var2 to set equality outside them.
return true;
else
return false;
}
</pre>

== Sources ==

[[Image:Geographylogo.png]][http://www.codjumper.com/forums/viewtopic.php?t=4011&sid=ed58d3b3f5bfa32350d4670d35c9f781 From CoDJumper.com]

Notify / Endon / Waittill

2008-10-23T23:40:29Z

Novemberdobby:

== [[Notify / Endon / Waittill]] ==

[[Image:Nutshell.png]] These 3 functions allow you to make a script wait for specific events and then trigger those events in different parts of the scripts.

This one ends the function it is inside when 'thread_restart' is triggered on 'level':

level endon ("thread_restart");

and this triggers the 'killed_player' notification on 'self' (which is a player in this case):

self notify("killed_player");

If you use 'player waittill("x")' or 'player endon("x")', then using a 'level notify("x")' will not trigger either of them - level is not the same entity as player, and all entities' triggers are independant.

Using the functions is easy. Firstly, decide which entity you want to wait for the trigger on. This is a player most of the time, but if you want a global trigger then use 'level'.

Then you must decide which trigger to use. You can choose either "endon" or "waittill" - they are both self explanatory, one will end the function it is running in when triggered, and the other will 'wait' until the specified trigger.

----

Next you decide on a unique name for the trigger. For example...

level endon("a_unique_call");

And to activate this trigger, you use notify on the same entity (level):

level notify("a_unique_call");

You can use as many waittill and endon functions as you want on an entity, in different functions. They will all be triggered by a notify.

Here is a quick example of it in use in multiple threads in the DM gametype...
<pre>
spawnPlayer()
{
self notify("spawned");

/*... Code snipped ... this is another type of
comment that can span multiple lines. */

}

Callback_PlayerKilled(attacker, some other arguments)
{
self endon("spawned"); //this makes callback_playerkilled() terminate when "spawned" is triggered in spawnplayer().
}
</pre>

Switch

2008-10-23T23:39:55Z

Novemberdobby:

== [[Switch]] ==

[[Image:Nutshell.png]] Switch is often used instead of multiple if statements, as it is more efficient and doesn't require you to type as much.

''How to use "Switch".''

Switch can be quite hard to understand at first glance, but after using it, it will become easier.

Here is an example of how it is used. This is taken from the menu scripts, which handles the ingame menus, I have cut the code and also added the commented lines myself.
<pre>
self waittill("menuresponse", menu, response);

switch(response)
{

case "changeweapon":
self closeMenu();
self closeInGameMenu();
if(self.pers["team"] == "allies")
self openMenu(game["menu_weapon_allies"]);
else if(self.pers["team"] == "axis")
self openMenu(game["menu_weapon_axis"]);
break;

case "changeteam":
self closeMenu();
self closeInGameMenu();
self openMenu(game["menu_team"]);
break;

case "muteplayer":
self closeMenu();
self closeInGameMenu();
self openMenu(game["menu_muteplayer"]);
break;

case "callvote":
self closeMenu();
self closeInGameMenu();
self openMenu(game["menu_callvote"]);
break;

default:
//add default action here
break;
}
</pre>
The first part of the code is where the variable is defined. The game waits until a menu has been activated. The variables recieved are "menu" (the name of the menu activated) and "response" (what option was chosen from the menu). "Response" is the key variable for the 'Switch'.

After the variables have been defined, the Switch function is called. It then checks every "Case" (case is the term used for the possible outcomes of the variable) to find a match, if no match is found, the "Default" case is used. (if you do not have a default case, the script will crash - you can just add an empty one.)

If a match is found, then the function will do ALL the events from that point onwards, which is why you MUST add "break;" at the end of every case, if the break is not existent, then all other case functions will run also.

To use the above example, I shall input my own values to show how the example works...

When I open the menu ingame, I choose the option "changeteam".
The code kicks in and the variable "response" becomes equal to "changeteam".
The switch statement will now look at every case for a positive match.

Once the match is found, everything after the case will happen:
* self closeMenu(); //current menu closes
* self closeInGameMenu(); //close any other ingame menus
* self openMenu(game["menu_team"]); //will open the team menu
* break; //the rest of the switch statement is ended and the code continues

You can also make the script perform the same actions in multiple cases. For example:
<pre>
self waittill("menuresponse", menu, response);

switch(response)
{

case "changeweapon":
case "changeteam":
case "muteplayer":
case "callvote":
function();
break;

default:
//add default action here
break;
}
</pre>
This means that if the response variable is: 'changeweapon', 'changeteam', 'muteplayer' or 'callvote', function(); will be called.

Arrays

2008-10-23T23:39:41Z

Novemberdobby:

== [[Arrays]] ==

[[Image:Nutshell.png]] Arrays are objects that store several variables. These can be integers, strings, entities or even other arrays.

Arrays are extremely helpful when it comes to doing the same thing to several different objects, such as moving a few platforms by a certain amount in a map, or storing lots of related variables.

To create an array we simply type...
<pre>
arrayName = [];
</pre>
Now, to add an object/variable to this array, we can simply use:
<pre>
array(array.size) = "a string variable";
</pre>
Whenever you see array.size, the .size does not mean it's dimensions, but the amount of items in the array. So if an array contains 1 piece of data, the array.size is 1. To retrieve an items from an array, you can use array[0] for the first object/var stored in it, and then array[1] and so on for successive items.

Going back to the example above, we could retrieve the data by using array[0]. The first item in an array is listed as 0, the second as 1, and so on. This means that by using array(array.size) = "blah";, we can add new items to it because of the offset of 1.

A common use for an array is to call a function on all of the players in the game. This can be done by using an array with a FOR loop.
To start with we must get our array of players, and instead of using the above method of defining an array and adding custom data, we can use a builtin function.

players = getEntArray("player", "classname");

So, our array has been defined as "players", or more accurately, "players[]".

Inside "players[]" is every player on the server, and now all we need to do is use the array to thread a function to each player.
So, here we have a for loop to do such a thing:
<pre>
for(i = 0; i < players.size; i++)
{
players[i] thread function();
}
</pre>
That's our loop to go through every player and call function(); on them.

Remember, 'i' is a variable not a letter, so 'i' is substitued with the number of the loop.
In the first loop, 'i' equals 0, so:

players[0] thread function();

is executed.

Arrays are a complicated part of scripting, but once you have them understood, they are one of the most useful things in the game.

Creating Functions

2008-10-23T23:39:09Z

Novemberdobby:

== [[Creating Functions]] ==

[[Image:Nutshell.png]] A custom function is a good way to use repeat sections of code more efficiently. For example, if you often use the same sequence of code, you can template them into a custom function. Imagine this is your code...
<pre>
{
wait 1;
brush1 moveZ(320, 5);
brush1 waittill("movedone");
wait 1;
brush2 moveZ(540, 3);
brush2 waittill("movedone");
}
</pre>
This can be simplified using a custom function, lets call this function "_moveEnt" (it is common practice to use an underscore as the first character of a function)

_moveEnt(ent, dist, time)

As the above shows, we are going to need 3 arguements, ent (entity), dist (distance) and time.

Now lets look at the full code with custom function in use...
<pre>
{
_moveEnt(brush1, 320, 5);
_moveEnt(brush2, 540, 3);
}

_moveEnt(ent, dist, time)
{
wait 1;
ent moveZ(dist, time);
ent waittill("movedone");
}
</pre>
As the above code shows, the custom function can simply be called using the required arguements, which are passed along and used in the new function.

Once the custom function has finished, the script returns to the original location from where it was called.

Functions can also return values to the original script, or even entities.

A simple function to calculate volume from the width, height and depth:
<pre>
{
area = _areaEquation(2, 4, 6);
}

_areaEquation(x, y, z)
{
answer = x * y * z;
return answer;
}
</pre>
Once the code calls the function '_areaEquation' the function works out the 'answer', 'answer' is the returned.
This declares a new variable (area). The variable area, is the answer that is returned by the function.

The two lines:

answer = x * y * z;
return answer;

could be replace by

return x * y * z;

for the same effect.

IFs, Loops & Logic

2008-10-23T23:38:53Z

Novemberdobby:

== [[IFs, Loops & Logic]] ==

[[Image:Nutshell.png]] This section will go into a little more detail of how to use 'if' statements and loops.

An 'if' statement is used to verify whether some data satisfies certain conditions, and then to execute code depending on the outcome.

To understand this section, you must first know the operators used to compare data:

<pre>
== :: Equal To
!= :: Not Equal To
! :: Negation (Not equal to)
< :: Less than
> :: Greater than
<= :: Less or Equal to
>= :: Greater or Equal to
&& :: And
|| :: Or
</pre>

Ok, now that we have some operators, lets get started on the statement.

An 'if' statement, requires a minimum of one arguement and usually one operator.

Here are some examples...notice the lack of semicolons at the end of the statements.
<pre>
if(variable) //If variable is true
if(!variable) //If variable is not true
if(variable1 == variable2) //If variable1 is equal to variable2
if(variable1 != variable2) //If variable1 is not equal to variable2
if(integer1 < integer2) //If integer1 is less than integer2
if(integer1 > integer2) //If integer1 is greater than integer2
if(integer1 <= integer2) //If integer1 is less than or equal to integer2
if(integer1 >= integer2) //If integer1 is greater or equal to integer2
if((var1 == var2) && (var3 != var4)) //If var1 is equal to var2 AND var3 is not equal to var4
if((int1 > int2) || (var1 == var2)) //If int1 is greater than int2 OR var1 is equal to var2
</pre>
To use an if statement to determine the movement of the script, you need to use the arguements to move the script in certain directions...
<pre>
if(var1 == var2)
{
//if var1 equals var2, do this code
//everything inside these curly braces
}
//then do this code regardless of the result
</pre>

If the statement above is true, the code inside the curly brackets is processed, if it is not true, the code inside the brackets are skipped.

Whether or not the statement is true, the code outside of the brackets is going to be processed. If this is not what you want, you need to use "Else" after the statement, for example...
<pre>
if(var1 == var2)
{
//if it's true then do this
}
else
{
//if it's false then do this
}
</pre>
You can also use an "else if" in the statement. This is used in a scenario where you want to check multiple comparisons.
<pre>
if(var1 == var2)
{
//if above arguement is true
}
else if(!var1 && var3)
{
//if var1 is false but var3 is true
}
else
{
//if all other if statements were false
}
</pre>
Thats the basics of if's, so let move on to loops.

Loops come in different forms...

'''While''' :: A while loop is a loop that keeps looping WHILE the arguement is true.
'''For''' :: A for loop is a loop that loops a set amount of times

To use a while loop, a condition/some conditions must be stated: "while(conditions)"
Often, this loop is used for infinite loops, which last forever unless specifically stopped. This is done using the arguement of 1 or true (1 is the integer of true)

while(1)
while(true)

A while loop can also be used as a normal loop that loops while the arguement is true, when the arguement becomes false the loop exits automatically (or rather, doesn't begin executing the commands in the loop again but just finishes the loop in progress).
<pre>
int = 0;

while(int < 10)
{
wait 1;
int++;
}
</pre>
The above code will loop while 'int' is less than 10. The loop waits 1 second, and then the loop increments 'int'. Once 'int' is not less than 10, the loop breaks.

The same applies for FOR loops.

A FOR loop requires 3 arguements.

for(declare; while; do)

'''Declare''' is the section which declares a variable for the loop to use.

'''While''' is what determines when the loop breaks

'''Do''' is what the loop should do after each loop.

A common FOR loop looks like this...
<pre>
for(i = 0; i < int; i++)
</pre>
The above code means: (i is 0, while i is smaller than int, add one to i).

Let's replace int with an actual number:
<pre>
for(i = 0; i < 10; i++)
{
wait 1;
thread function();
}
</pre>
This is the sequence of events...

- 'i' = 0
- while i is less than 10, continue the loop
- perform code (wait 1; and function())
- increment 'i' (i++)

The FOR loop can also be used as an "infinite loop" using the "forever loop"

for(;;)

The above will simply keep repeating the code until manually terminated.

The problem with infinite loops is that they will give you an error if you don't allow them to pause at any point - so all infinite loops require a wait statement somewhere in the executed code.

To finish off, we need to know how to manually exit these loops. A common way to exit an infinite loop is to use an IF statement to determine when to 'break' (break is the keyword used to exit a loop) - here is an example of an IF statement breaking an infinite loop...
<pre>
for(;;)
{
wait 1;
if(var1 == var2)
{
break;
}
}
</pre>
The above sequence simply goes...

- wait 1 second
- check if statement...
- if var1 is equal to var2, break out of the loop
- else continue the loop

Maths & Operators

2008-10-23T23:38:06Z

Novemberdobby:

== [[Maths & Operators]] ==

[[Image:Nutshell.png]] Maths is used throughout scripting to get many different values, be it the distance between two objects or to calculate an equation.

For example, a variable can be given data from an equation.

variable = 5 + 1;

Although the above example is pretty pointless, as it adds one constant to another to make a constant, and you can just calculate it yourself and use the answer i.e.

variable = 6;

But variables can be calculated using other variables, for example...

varAnswer = var1 + var2;

varAnswer will be equal to the value of var1 plus the value of var2.

There are several operators that can be used in maths...
<pre>
+ :: Addition
- :: Subtraction
* :: Multiplication
/ :: Division
% :: Modulus
= :: Equals
</pre>
There are also some more little-known operators such as...
<pre>
++ :: Increment (+1)
-- :: Decrement (-1)
+= :: Incrementation (requires number)
-= :: Decrementation (requires number)
</pre>
Example of these in use...
<pre>
var++; //Set var to var + 1
var--; //Set var to var - 1
var += int; //Set var to var + int
var -= int; //Set var to var - int
</pre>

Using Variables

2008-10-23T23:37:15Z

Novemberdobby:

== [[Using Variables]] ==

[[Image:Nutshell.png]] Variables can be used in several ways, but in all cases they are used to store some data for the duration of the game. Variables come in different forms: integers, floats, entities, strings, arrays and booleans, there are also several different ways variables can be stored.

A simple variable is simply declared using

variable = data;

This variable can be used in the current function and any function that passes it as an argument, or is called on it (so it'd be used as 'self').

Variables can be global (which can be used in all threads without needing to be called) by using the

level.variable = data;

or they can be assigned to entities individually

entity.variable = data;

for things like player.health (integer, already built-in, but can be modified) and level.teamBased (boolean).

Getting Started

2008-10-23T23:35:53Z

Novemberdobby:

== [[Getting Started]] ==

This section will include several things you need to know before you start scripting.

[[Image:Nutshell.png]] All scripts are contained within simple text files that contain no formatting, so programs such as Word are not to be used. The file format used for scripts within the Call of Duty series is 'GSC' (.gsc). It is recommended you use a simple but effective editor for programming, such programs include [http://www.crimsoneditor.com/ Crimson Editor], [http://http://www.pnotepad.org/ Programmers Notepad] and [http://www.editplus.com/ Editplus].

A few things you need to know before reading any further are a few common words used within scripting.

'''Variables:''' variables are data storage locations which are assigned a name. For example...
<pre>
integerthing = 1; //by the way, comments like this can be made using //, and are ignored by the game.
floatthing = 0.5;
stringthing = "Text and symbols 1234567890";
booleanthing = true; //another thing, almost every line must have a ; at the end or the script won't work. More on that later.
</pre>
The variables are declared on the left, and assigned a value such as an integer (whole number), a float (a number containing a decimal), a string (text and symbols) or a boolean (true/false).

'''Entities:''' These are objects that are used in maps, and can be referenced in the script. Entities include players, dropped guns, objectives, script_models, etc.

They can be referenced using their their targetname or classname that has been set within the map.

'''Functions:''' an action or procedure that can be called or threaded and can return a value. For example...
<pre>
funcMove()
{
self moveY(320, 3);
}
</pre>
The main function in the above code is '''funcMove()''', and it will perform the actions inside the curly braces when it runs. There is also another function, '''moveY''', which is a built-in function inside COD4, and moves an entity on the Y axis.

'''Arguements:''' These are key piece of information that are passed along to functions, and can be any type of object (entity, string, boolean etc). The function that was passed the arguments can then reference them.

For example, if a function is shown as
<pre>
function(arg1, arg2)
</pre>
The function is asking for two arguements to be sent to the function. An example of this in use...
<pre>
someotherstuff()
{
ent function(320, 5);
thing function(320, 5);
}

function(distance, time)
{
ent moveZ(distance, time);
}
</pre>
As you can see, function() is called on both 'ent' and 'thing', and the two arguments '320' and '5' are passed to the new function as 'distance' and 'time'. Then moveZ is called on the entities.

'''Calling/Threading:''' these are used with functions. Functions can be threaded or called sequentially.

If a function is threaded, then that function is performed while the script continues, whereas if a function is called sequentially, the script waits until the function is completed before it continues. Examples...
<pre>
function(); //the script will stop at this line and carry out function() before going down to...
thread function(); //this will start function() and carry on to execute 'ent moveZ'
ent moveZ(350, 5);
</pre>
'''Self:''' If you call a function on an entity e.g 'unnamedent thread dostuff()', then within the function dostuff(), you can refer to unnamedent as 'self'.

For example...
<pre>
something()
{
ent = getent("ent","targetname");
ent function();
}

function()
{
self moveZ(150, 5);
}
</pre>

Call of Duty 4: Introduction

2008-10-23T23:34:14Z

Novemberdobby:

[[Category:Call of Duty 4]]
[[Category:Modding]]
Here is a very good tutorial on COD coding that my mate Danny Redford (hence - Drofder, as its Redford
backwards :))
wrote back in 2006, which is a succint introduction to a very complex thing. '''Tally;'''

[[Image:Code.png|left]]
'''By Drofder2004'''

Ok, this is my own guide for scripting, it is incomplete and lacks a lot of formatting (I will try and get round to that soon). It was written in 2.5 hours and contains a lot of basic and slightly advanced guides on several base topics. Some areas contain more detail than others depending on relevance and difficulty.

When I get more time, I will add to this guide. Once I have pretty much finished the majority of the guide I will provide several new scripts using several advanced functions.

This guide should be used as a small starting guide for people new to scripting, and reference for those who know some scripting. This will provide an insight into how script can improve the fun of maps, and hopefully will help answer questions for those who are stuck.

If you find any problems (be it wrong syntax, spelling or etc) then post.
If you want to request/criticise/compliment or whatever, again post.

Enjoy.

== [[Getting Started]] ==

This section will include several things you need to know before you start scripting.

[[Image:Nutshell.png]] All scripts are contained within simple text files that contain no formatting, so programs such as Word are not to be used. The file format used for scripts within the Call of Duty series is 'GSC' (.gsc). It is recommended you use a simple but effective editor for programming, such programs include [http://www.crimsoneditor.com/ Crimson Editor], [http://http://www.pnotepad.org/ Programmers Notepad] and [http://www.editplus.com/ Editplus].

A few things you need to know before reading any further are a few common words used within scripting.

'''Variables:''' variables are data storage locations which are assigned a name. For example...
<pre>
integerthing = 1; //by the way, comments like this can be made using //, and are ignored by the game.
floatthing = 0.5;
stringthing = "Text and symbols 1234567890";
booleanthing = true; //another thing, almost every line must have a ; at the end or the script won't work. More on that later.
</pre>
The variables are declared on the left, and assigned a value such as an integer (whole number), a float (a number containing a decimal), a string (text and symbols) or a boolean (true/false).

'''Entities:''' These are objects that are used in maps, and can be referenced in the script. Entities include players, dropped guns, objectives, script_models, etc.

They can be referenced using their their targetname or classname that has been set within the map.

'''Functions:''' an action or procedure that can be called or threaded and can return a value. For example...
<pre>
funcMove()
{
self moveY(320, 3);
}
</pre>
The main function in the above code is '''funcMove()''', and it will perform the actions inside the curly braces when it runs. There is also another function, '''moveY''', which is a built-in function inside COD4, and moves an entity on the Y axis.

'''Arguements:''' These are key piece of information that are passed along to functions, and can be any type of object (entity, string, boolean etc). The function that was passed the arguments can then reference them.

For example, if a function is shown as
<pre>
function(arg1, arg2)
</pre>
The function is asking for two arguements to be sent to the function. An example of this in use...
<pre>
someotherstuff()
{
ent function(320, 5);
thing function(320, 5);
}

function(distance, time)
{
ent moveZ(distance, time);
}
</pre>
As you can see, function() is called on both 'ent' and 'thing', and the two arguments '320' and '5' are passed to the new function as 'distance' and 'time'. Then moveZ is called on the entities.

'''Calling/Threading:''' these are used with functions. Functions can be threaded or called sequentially.

If a function is threaded, then that function is performed while the script continues, whereas if a function is called sequentially, the script waits until the function is completed before it continues. Examples...
<pre>
function(); //the script will stop at this line and carry out function() before going down to...
thread function(); //this will start function() and carry on to execute 'ent moveZ'
ent moveZ(350, 5);
</pre>
'''Self:''' If you call a function on an entity e.g 'unnamedent thread dostuff()', then within the function dostuff(), you can refer to unnamedent as 'self'.

For example...
<pre>
something()
{
ent = getent("ent","targetname");
ent function();
}

function()
{
self moveZ(150, 5);
}
</pre>
== [[Using Variables]] ==

[[Image:Nutshell.png]] Variables can be used in several ways, but in all cases they are used to store some data for the duration of the game. Variables come in different forms: integers, floats, entities, strings, arrays and booleans, there are also several different ways variables can be stored.

A simple variable is simply declared using

variable = data;

This variable can be used in the current function and any function that passes it as an argument, or is called on it (so it'd be used as 'self').

Variables can be global (which can be used in all threads without needing to be called) by using the

level.variable = data;

or they can be assigned to entities individually

entity.variable = data;

for things like player.health (integer, already built-in, but can be modified) and level.teamBased (boolean).

== Maths & Operators ==

[[Image:Nutshell.png]] Maths is used throughout scripting to get many different values, be it the distance between two objects or to calculate an equation.

For example, a variable can be given data from an equation.

variable = 5 + 1;

Although the above example is pretty pointless, as it adds one constant to another to make a constant, and you can just calculate it yourself and use the answer i.e.

variable = 6;

But variables can be calculated using other variables, for example...

varAnswer = var1 + var2;

varAnswer will be equal to the value of var1 plus the value of var2.

There are several operators that can be used in maths...
<pre>
+ :: Addition
- :: Subtraction
* :: Multiplication
/ :: Division
% :: Modulus
= :: Equals
</pre>
There are also some more little-known operators such as...
<pre>
++ :: Increment (+1)
-- :: Decrement (-1)
+= :: Incrementation (requires number)
-= :: Decrementation (requires number)
</pre>
Example of these in use...
<pre>
var++; //Set var to var + 1
var--; //Set var to var - 1
var += int; //Set var to var + int
var -= int; //Set var to var - int
</pre>
== [[IFs, Loops & Logic]] ==

[[Image:Nutshell.png]] This section will go into a little more detail of how to use 'if' statements and loops.

An 'if' statement is used to verify whether some data satisfies certain conditions, and then to execute code depending on the outcome.

To understand this section, you must first know the operators used to compare data:

<pre>
== :: Equal To
!= :: Not Equal To
! :: Negation (Not equal to)
< :: Less than
> :: Greater than
<= :: Less or Equal to
>= :: Greater or Equal to
&& :: And
|| :: Or
</pre>

Ok, now that we have some operators, lets get started on the statement.

An 'if' statement, requires a minimum of one arguement and usually one operator.

Here are some examples...notice the lack of semicolons at the end of the statements.
<pre>
if(variable) //If variable is true
if(!variable) //If variable is not true
if(variable1 == variable2) //If variable1 is equal to variable2
if(variable1 != variable2) //If variable1 is not equal to variable2
if(integer1 < integer2) //If integer1 is less than integer2
if(integer1 > integer2) //If integer1 is greater than integer2
if(integer1 <= integer2) //If integer1 is less than or equal to integer2
if(integer1 >= integer2) //If integer1 is greater or equal to integer2
if((var1 == var2) && (var3 != var4)) //If var1 is equal to var2 AND var3 is not equal to var4
if((int1 > int2) || (var1 == var2)) //If int1 is greater than int2 OR var1 is equal to var2
</pre>
To use an if statement to determine the movement of the script, you need to use the arguements to move the script in certain directions...
<pre>
if(var1 == var2)
{
//if var1 equals var2, do this code
//everything inside these curly braces
}
//then do this code regardless of the result
</pre>

If the statement above is true, the code inside the curly brackets is processed, if it is not true, the code inside the brackets are skipped.

Whether or not the statement is true, the code outside of the brackets is going to be processed. If this is not what you want, you need to use "Else" after the statement, for example...
<pre>
if(var1 == var2)
{
//if it's true then do this
}
else
{
//if it's false then do this
}
</pre>
You can also use an "else if" in the statement. This is used in a scenario where you want to check multiple comparisons.
<pre>
if(var1 == var2)
{
//if above arguement is true
}
else if(!var1 && var3)
{
//if var1 is false but var3 is true
}
else
{
//if all other if statements were false
}
</pre>
Thats the basics of if's, so let move on to loops.

Loops come in different forms...

'''While''' :: A while loop is a loop that keeps looping WHILE the arguement is true.
'''For''' :: A for loop is a loop that loops a set amount of times

To use a while loop, a condition/some conditions must be stated: "while(conditions)"
Often, this loop is used for infinite loops, which last forever unless specifically stopped. This is done using the arguement of 1 or true (1 is the integer of true)

while(1)
while(true)

A while loop can also be used as a normal loop that loops while the arguement is true, when the arguement becomes false the loop exits automatically (or rather, doesn't begin executing the commands in the loop again but just finishes the loop in progress).
<pre>
int = 0;

while(int < 10)
{
wait 1;
int++;
}
</pre>
The above code will loop while 'int' is less than 10. The loop waits 1 second, and then the loop increments 'int'. Once 'int' is not less than 10, the loop breaks.

The same applies for FOR loops.

A FOR loop requires 3 arguements.

for(declare; while; do)

'''Declare''' is the section which declares a variable for the loop to use.

'''While''' is what determines when the loop breaks

'''Do''' is what the loop should do after each loop.

A common FOR loop looks like this...
<pre>
for(i = 0; i < int; i++)
</pre>
The above code means: (i is 0, while i is smaller than int, add one to i).

Let's replace int with an actual number:
<pre>
for(i = 0; i < 10; i++)
{
wait 1;
thread function();
}
</pre>
This is the sequence of events...

- 'i' = 0
- while i is less than 10, continue the loop
- perform code (wait 1; and function())
- increment 'i' (i++)

The FOR loop can also be used as an "infinite loop" using the "forever loop"

for(;;)

The above will simply keep repeating the code until manually terminated.

The problem with infinite loops is that they will give you an error if you don't allow them to pause at any point - so all infinite loops require a wait statement somewhere in the executed code.

To finish off, we need to know how to manually exit these loops. A common way to exit an infinite loop is to use an IF statement to determine when to 'break' (break is the keyword used to exit a loop) - here is an example of an IF statement breaking an infinite loop...
<pre>
for(;;)
{
wait 1;
if(var1 == var2)
{
break;
}
}
</pre>
The above sequence simply goes...

- wait 1 second
- check if statement...
- if var1 is equal to var2, break out of the loop
- else continue the loop

== [[Creating Functions]] ==

[[Image:Nutshell.png]] A custom function is a good way to use repeat sections of code more efficiently. For example, if you often use the same sequence of code, you can template them into a custom function. Imagine this is your code...
<pre>
{
wait 1;
brush1 moveZ(320, 5);
brush1 waittill("movedone");
wait 1;
brush2 moveZ(540, 3);
brush2 waittill("movedone");
}
</pre>
This can be simplified using a custom function, lets call this function "_moveEnt" (it is common practice to use an underscore as the first character of a function)

_moveEnt(ent, dist, time)

As the above shows, we are going to need 3 arguements, ent (entity), dist (distance) and time.

Now lets look at the full code with custom function in use...
<pre>
{
_moveEnt(brush1, 320, 5);
_moveEnt(brush2, 540, 3);
}

_moveEnt(ent, dist, time)
{
wait 1;
ent moveZ(dist, time);
ent waittill("movedone");
}
</pre>
As the above code shows, the custom function can simply be called using the required arguements, which are passed along and used in the new function.

Once the custom function has finished, the script returns to the original location from where it was called.

Functions can also return values to the original script, or even entities.

A simple function to calculate volume from the width, height and depth:
<pre>
{
area = _areaEquation(2, 4, 6);
}

_areaEquation(x, y, z)
{
answer = x * y * z;
return answer;
}
</pre>
Once the code calls the function '_areaEquation' the function works out the 'answer', 'answer' is the returned.
This declares a new variable (area). The variable area, is the answer that is returned by the function.

The two lines:

answer = x * y * z;
return answer;

could be replace by

return x * y * z;

for the same effect.

== [[Arrays]] ==

[[Image:Nutshell.png]] Arrays are objects that store several variables. These can be integers, strings, entities or even other arrays.

Arrays are extremely helpful when it comes to doing the same thing to several different objects, such as moving a few platforms by a certain amount in a map, or storing lots of related variables.

To create an array we simply type...
<pre>
arrayName = [];
</pre>
Now, to add an object/variable to this array, we can simply use:
<pre>
array(array.size) = "a string variable";
</pre>
Whenever you see array.size, the .size does not mean it's dimensions, but the amount of items in the array. So if an array contains 1 piece of data, the array.size is 1. To retrieve an items from an array, you can use array[0] for the first object/var stored in it, and then array[1] and so on for successive items.

Going back to the example above, we could retrieve the data by using array[0]. The first item in an array is listed as 0, the second as 1, and so on. This means that by using array(array.size) = "blah";, we can add new items to it because of the offset of 1.

A common use for an array is to call a function on all of the players in the game. This can be done by using an array with a FOR loop.
To start with we must get our array of players, and instead of using the above method of defining an array and adding custom data, we can use a builtin function.

players = getEntArray("player", "classname");

So, our array has been defined as "players", or more accurately, "players[]".

Inside "players[]" is every player on the server, and now all we need to do is use the array to thread a function to each player.
So, here we have a for loop to do such a thing:
<pre>
for(i = 0; i < players.size; i++)
{
players[i] thread function();
}
</pre>
That's our loop to go through every player and call function(); on them.

Remember, 'i' is a variable not a letter, so 'i' is substitued with the number of the loop.
In the first loop, 'i' equals 0, so:

players[0] thread function();

is executed.

Arrays are a complicated part of scripting, but once you have them understood, they are one of the most useful things in the game.

== [[Switch]] ==

[[Image:Nutshell.png]] Switch is often used instead of multiple if statements, as it is more efficient and doesn't require you to type as much.

''How to use "Switch".''

Switch can be quite hard to understand at first glance, but after using it, it will become easier.

Here is an example of how it is used. This is taken from the menu scripts, which handles the ingame menus, I have cut the code and also added the commented lines myself.
<pre>
self waittill("menuresponse", menu, response);

switch(response)
{

case "changeweapon":
self closeMenu();
self closeInGameMenu();
if(self.pers["team"] == "allies")
self openMenu(game["menu_weapon_allies"]);
else if(self.pers["team"] == "axis")
self openMenu(game["menu_weapon_axis"]);
break;

case "changeteam":
self closeMenu();
self closeInGameMenu();
self openMenu(game["menu_team"]);
break;

case "muteplayer":
self closeMenu();
self closeInGameMenu();
self openMenu(game["menu_muteplayer"]);
break;

case "callvote":
self closeMenu();
self closeInGameMenu();
self openMenu(game["menu_callvote"]);
break;

default:
//add default action here
break;
}
</pre>
The first part of the code is where the variable is defined. The game waits until a menu has been activated. The variables recieved are "menu" (the name of the menu activated) and "response" (what option was chosen from the menu). "Response" is the key variable for the 'Switch'.

After the variables have been defined, the Switch function is called. It then checks every "Case" (case is the term used for the possible outcomes of the variable) to find a match, if no match is found, the "Default" case is used. (if you do not have a default case, the script will crash - you can just add an empty one.)

If a match is found, then the function will do ALL the events from that point onwards, which is why you MUST add "break;" at the end of every case, if the break is not existent, then all other case functions will run also.

To use the above example, I shall input my own values to show how the example works...

When I open the menu ingame, I choose the option "changeteam".
The code kicks in and the variable "response" becomes equal to "changeteam".
The switch statement will now look at every case for a positive match.

Once the match is found, everything after the case will happen:
* self closeMenu(); //current menu closes
* self closeInGameMenu(); //close any other ingame menus
* self openMenu(game["menu_team"]); //will open the team menu
* break; //the rest of the switch statement is ended and the code continues

You can also make the script perform the same actions in multiple cases. For example:
<pre>
self waittill("menuresponse", menu, response);

switch(response)
{

case "changeweapon":
case "changeteam":
case "muteplayer":
case "callvote":
function();
break;

default:
//add default action here
break;
}
</pre>
This means that if the response variable is: 'changeweapon', 'changeteam', 'muteplayer' or 'callvote', function(); will be called.

== [[Notify / Endon / Waittill]] ==

[[Image:Nutshell.png]] These 3 functions allow you to make a script wait for specific events and then trigger those events in different parts of the scripts.

This one ends the function it is inside when 'thread_restart' is triggered on 'level':

level endon ("thread_restart");

and this triggers the 'killed_player' notification on 'self' (which is a player in this case):

self notify("killed_player");

If you use 'player waittill("x")' or 'player endon("x")', then using a 'level notify("x")' will not trigger either of them - level is not the same entity as player, and all entities' triggers are independant.

Using the functions is easy. Firstly, decide which entity you want to wait for the trigger on. This is a player most of the time, but if you want a global trigger then use 'level'.

Then you must decide which trigger to use. You can choose either "endon" or "waittill" - they are both self explanatory, one will end the function it is running in when triggered, and the other will 'wait' until the specified trigger.

----

Next you decide on a unique name for the trigger. For example...

level endon("a_unique_call");

And to activate this trigger, you use notify on the same entity (level):

level notify("a_unique_call");

You can use as many waittill and endon functions as you want on an entity, in different functions. They will all be triggered by a notify.

Here is a quick example of it in use in multiple threads in the DM gametype...
<pre>
spawnPlayer()
{
self notify("spawned");

/*... Code snipped ... this is another type of
comment that can span multiple lines. */

}

Callback_PlayerKilled(attacker, some other arguments)
{
self endon("spawned"); //this makes callback_playerkilled() terminate when "spawned" is triggered in spawnplayer().
}
</pre>

== [[Random stuff]] ==

A few useful commands:

To print a large message on the screen:

'''iprintlnbold(stringMessage);'''
or to a specific player:
'''player iprintlnbold(stringMessage);'''

To print a small message on the bottom left of the screen:

'''iprintln(stringMessage);
same as iprintlnbold() to a specific player

To check whether a variable or entity exists:

'''if(isdefined(timetowait))'''
'''wait (timetowait);'''

You can also use functions in if statements, by the returned value:
<pre>
if(checksomething())
//code here

checksomething()
{
if(var == "hi there!") //remember to use == in if statements to check equality, but var1 = var2 to set equality outside them.
return true;
else
return false;
}
</pre>

== Sources ==

[[Image:Geographylogo.png]][http://www.codjumper.com/forums/viewtopic.php?t=4011&sid=ed58d3b3f5bfa32350d4670d35c9f781 From CoDJumper.com]

Call of Duty 4: Introduction

2008-10-23T23:28:22Z

Novemberdobby: Lots of changes.

[[Category:Call of Duty 4]]
[[Category:Modding]]
Here is a very good tutorial on COD coding that my mate Danny Redford (hence - Drofder, as its Redford
backwards :))
wrote back in 2006, which is a succint introduction to a very complex thing. '''Tally;'''

[[Image:Code.png|left]]
'''By Drofder2004'''

Ok, this is my own guide for scripting, it is incomplete and lacks a lot of formatting (I will try and get round to that soon). It was written in 2.5 hours and contains a lot of basic and slightly advanced guides on several base topics. Some areas contain more detail than others depending on relevance and difficulty.

When I get more time, I will add to this guide. Once I have pretty much finished the majority of the guide I will provide several new scripts using several advanced functions.

This guide should be used as a small starting guide for people new to scripting, and reference for those who know some scripting. This will provide an insight into how script can improve the fun of maps, and hopefully will help answer questions for those who are stuck.

If you find any problems (be it wrong syntax, spelling or etc) then post.
If you want to request/criticise/compliments or whatever, again post.

Enjoy.

== [[Getting Started]] ==

This section will include serveral things you need to know before you start scripting.

[[Image:Nutshell.png]] All scripts are contained within simple text files that contain no formatting, so programs such as Word are not to be used. The file format used for scripts within the Call of Duty series is 'GSC' (.gsc). It is recommended you use a simple but effective editor for programming, such programs include [http://www.crimsoneditor.com/ Crimson Editor], [http://http://www.pnotepad.org/ Programmers Notepad] and [http://www.editplus.com/ Editplus].

A few things you need to know before reading any further are a few common words used within scripting.

'''Variables:''' variables are data storage locations which are assigned a name. For example...

integerthing = 1; //by the way, comments like this can be made using //, and are ignored by the game.
floatthing = 0.5;
stringthing = "Text and symbols 1234567890";
booleanthing = true; //another thing, almost every line must have a ; at the end or the script won't work. More on that later.

The variables are declared on the left, and assigned a value such as an integer (whole number), a float (a number containing a decimal), a string (text and symbols) or a boolean (true/false).

'''Entities:''' These are objects that are used in maps, and can be referenced in the script. Entities include players, dropped guns, objectives, script_models, etc.

They can be referenced using their their targetname or classname that has been set within the map.

'''Functions:''' an action or procedure that can be called or threaded and can return a value. For example...

funcMove()
{
self moveY(320, 3);
}

The main function in the above code is '''funcMove()''', and it will perform the actions inside the curly braces when it runs. There is also another function, '''moveY''', which is a built-in function inside COD4, and moves an entity on the Y axis.

'''Arguements:''' These are key piece of information that are passed along to functions, and can be any type of object (entity, string, boolean etc). The function that was passed the arguments can then reference them.

For example, if a function is shown as

function(arg1, arg2)

The function is asking for two arguements to be sent to the function. An example of this in use...

someotherstuff()
{
ent function(320, 5);
thing function(320, 5);
}

function(distance, time)
{
ent moveZ(distance, time);
}

As you can see, function() is called on both 'ent' and 'thing', and the two arguments '320' and '5' are passed to the new function as 'distance' and 'time'. Then moveZ is called on the entities.

'''Calling/Threading:''' these are used with functions. Functions can be threaded or called sequentially.

If a function is threaded, then that function is performed while the script continues, whereas if a function is called sequentially, the script waits until the function is completed before it continues. Examples...

function(); //the script will stop at this line and carry out function() before going down to...
thread function(); //this will start function() and carry on to execute 'ent moveZ'
ent moveZ(350, 5);

'''Self:''' If you call a function on an entity e.g 'unnamedent thread dostuff()', then within the function dostuff(), you can refer to unnamedent as 'self'.

For example...

something()
{
ent = getent("ent","targetname");
ent function();
}

function()
{
self moveZ(150, 5);
}

== [[Using Variables]] ==

[[Image:Nutshell.png]] Variables can be used in several ways, but in all cases they are used to store some data for the duration of the game. Variables come in different forms: integers, floats, entities, strings, arrays and booleans, there are also several different ways variables can be stored.

A simple variable is simply declared using

variable = data;

This variable can be used in the current function and any function that passes it as an argument, or is called on it (so it'd be used as 'self').

Variables can be global (which can be used in all threads without needing to be called) by using the

level.variable = data;

or they can be assigned to entities individually

entity.variable = data;

for things like player.health (integer, already built-in, but can be modified) and level.teamBased (boolean).

== Maths & Operators ==

[[Image:Nutshell.png]] Maths is used throughout scripting to get many different values, be it the distance between two objects or to calculate an equation.

For example, a variable can be given data from an equation.

variable = 5 + 1;

Although the above example is pretty pointless, as it adds one constant to another to make a constant, and you can just calculate it yourself and use the answer i.e.

variable = 6;

But variables can be calculated using other variables, for example...

varAnswer = var1 + var2;

varAnswer will be equal to the value of var1 plus the value of var2.

There are several operators that can be used in maths...
<pre>
+ :: Addition
- :: Subtraction
* :: Multiplication
/ :: Division
% :: Modulus
= :: Equals
</pre>
There are also some more little-known operators such as...
<pre>
++ :: Increment (+1)
-- :: Decrement (-1)
+= :: Incrementation (requires number)
-= :: Decrementation (requires number)
</pre>
Example of these in use...

var++; //Set var to var + 1
var--; //Set var to var - 1
var += int; //Set var to var + int
var -= int; //Set var to var - int

== [[IFs, Loops & Logic]] ==

[[Image:Nutshell.png]] This section will go into a little more detail of how to use 'if' statements and loops.

An 'if' statement is used to verify whether some data satisfies certain conditions, and then to execute code depending on the outcome.

To understand this section, you must first know the operators used to compare data:

<pre>
== :: Equal To
!= :: Not Equal To
! :: Negation (Not equal to)
< :: Less than
> :: Greater than
<= :: Less or Equal to
>= :: Greater or Equal to
&& :: And
|| :: Or
</pre>

Ok, now that we have some operators, lets get started on the statement.

An 'if' statement, requires a minimum of one arguement and usually one operator.

Here are some examples...notice the lack of semicolons at the end of the statements.

if(variable) //If variable is true
if(!variable) //If variable is not true
if(variable1 == variable2) //If variable1 is equal to variable2
if(variable1 != variable2) //If variable1 is not equal to variable2
if(integer1 < integer2) //If integer1 is less than integer2
if(integer1 > integer2) //If integer1 is greater than integer2
if(integer1 <= integer2) //If integer1 is less than or equal to integer2
if(integer1 >= integer2) //If integer1 is greater or equal to integer2
if((var1 == var2) && (var3 != var4)) //If var1 is equal to var2 AND var3 is not equal to var4
if((int1 > int2) || (var1 == var2)) //If int1 is greater than int2 OR var1 is equal to var2

To use an if statement to determine the movement of the script, you need to use the arguements to move the script in certain directions...

if(var1 == var2)
{
//if var1 equals var2, do this code
//everything inside these curly braces
}
//then do this code regardless of the result

If the statement above is true, the code inside the curly brackets is processed, if it is not true, the code inside the brackets are skipped.

Whether or not the statement is true, the code outside of the brackets is going to be processed. If this is not what you want, you need to use "Else" after the statement, for example...

if(var1 == var2)
{
//if it's true then do this
}
else
{
//if it's false then do this
}

You can also use an "else if" in the statement. This is used in a scenario where you want to check multiple comparisons.

if(var1 == var2)
{
//if above arguement is true
}
else if(!var1 && var3)
{
//if var1 is false but var3 is true
}
else
{
//if all other if statements were false
}

Thats the basics of if's, so let move on to loops.

Loops come in different forms...

'''While''' :: A while loop is a loop that keeps looping WHILE the arguement is true.
'''For''' :: A for loop is a loop that loops a set amount of times

To use a while loop, a condition/some conditions must be stated: "while(conditions)"
Often, this loop is used for infinite loops, which last forever unless specifically stopped. This is done using the arguement of 1 or true (1 is the integer of true)

while(1)
while(true)

A while loop can also be used as a normal loop that loops while the arguement is true, when the arguement becomes false the loop exits automatically (or rather, doesn't begin executing the commands in the loop again but just finishes the loop in progress).

int = 0;

while(int < 10)
{
wait 1;
int++;
}

The above code will loop while 'int' is less than 10. The loop waits 1 second, and then the loop increments 'int'. Once 'int' is not less than 10, the loop breaks.

The same applies for FOR loops.

A FOR loop requires 3 arguements.

for(declare; while; do)

'''Declare''' is the section which declares a variable for the loop to use.

'''While''' is what determines when the loop breaks

'''Do''' is what the loop should do after each loop.

A common FOR loop looks like this...

for(i = 0; i < int; i++)

The above code means: (i is 0, while i is smaller than int, add one to i).

Let's replace int with an actual number:

for(i = 0; i < 10; i++)
{
wait 1;
thread function();
}

This is the sequence of events...

- 'i' = 0
- while i is less than 10, continue the loop
- perform code (wait 1; and function())
- increment 'i' (i++)

The FOR loop can also be used as an "infinite loop" using the "forever loop"

for(;;)

The above will simply keep repeating the code until manually terminated.

The problem with infinite loops is that they will give you an error if you don't allow them to pause at any point - so all infinite loops require a wait statement somewhere in the executed code.

To finish off, we need to know how to manually exit these loops. A common way to exit an infinite loop is to use an IF statement to determine when to 'break' (break is the keyword used to exit a loop) - here is an example of an IF statement breaking an infinite loop...

for(;;)
{
wait 1;
if(var1 == var2)
{
break;
}
}

The above sequence simply goes...

- wait 1 second
- check if statement...
- if var1 is equal to var2, break out of the loop
- else continue the loop

== [[Creating Functions]] ==

[[Image:Nutshell.png]] A custom function is a good way to use repeat sections of code more efficiently. For example, if you often use the same sequence of code, you can template them into a custom function. Imagine this is your code...

{
wait 1;
brush1 moveZ(320, 5);
brush1 waittill("movedone");
wait 1;
brush2 moveZ(540, 3);
brush2 waittill("movedone");
}

This can be simplified using a custom function, lets call this function "_moveEnt" (it is common practice to use an underscore as the first character of a function)

_moveEnt(ent, dist, time)

As the above shows, we are going to need 3 arguements, ent (entity), dist (distance) and time.

Now lets look at the full code with custom function in use...

{
_moveEnt(brush1, 320, 5);
_moveEnt(brush2, 540, 3);
}

_moveEnt(ent, dist, time)
{
wait 1;
ent moveZ(dist, time);
ent waittill("movedone");
}

As the above code shows, the custom function can simply be called using the required arguements, which are passed along and used in the new function.

Once the custom function has finished, the script returns to the original location from where it was called.

Functions can also return values to the original script, or even entities.

A simple function to calculate volume from the width, height and depth:

{
area = _areaEquation(2, 4, 6);
}

_areaEquation(x, y, z)
{
answer = x * y * z;
return answer;
}

Once the code calls the function '_areaEquation' the function works out the 'answer', 'answer' is the returned.
This declares a new variable (area). The variable area, is the answer that is returned by the function.

The two lines:

answer = x * y * z;
return answer;

could be replace by

return x * y * z;

for the same effect.

== [[Arrays]] ==

[[Image:Nutshell.png]] Arrays are objects that store several variables. These can be integers, strings, entities or even other arrays.

Arrays are extremely helpful when it comes to doing the same thing to several different objects, such as moving a few platforms by a certain amount in a map, or storing lots of related variables.

To create an array we simply type...

arrayName = [];

Now, to add an object/variable to this array, we can simply use:

array(array.size) = "a string variable";

Whenever you see array.size, the .size does not mean it's dimensions, but the amount of items in the array. So if an array contains 1 piece of data, the array.size is 1. To retrieve an items from an array, you can use array[0] for the first object/var stored in it, and then array[1] and so on for successive items.

Going back to the example above, we could retrieve the data by using array[0]. The first item in an array is listed as 0, the second as 1, and so on. This means that by using array(array.size) = "blah";, we can add new items to it because of the offset of 1.

A common use for an array is to call a function on all of the players in the game. This can be done by using an array with a FOR loop.
To start with we must get our array of players, and instead of using the above method of defining an array and adding custom data, we can use a builtin function.

players = getEntArray("player", "classname");

So, our array has been defined as "players", or more accurately, "players[]".

Inside "players[]" is every player on the server, and now all we need to do is use the array to thread a function to each player.
So, here we have a for loop to do such a thing:

for(i = 0; i < players.size; i++)
{
players[i] thread function();
}

That's our loop to go through every player and call function(); on them.

Remember, 'i' is a variable not a letter, so 'i' is substitued with the number of the loop.
In the first loop, 'i' equals 0, so:

players[0] thread function();

is executed.

Arrays are a complicated part of scripting, but once you have them understood, they are one of the most useful things in the game.

== [[Switch]] ==

[[Image:Nutshell.png]] Switch is often used instead of multiple if statements, as it is more efficient and doesn't require you to type as much.

''How to use "Switch".''

Switch can be quite hard to understand at first glance, but after using it, it will become easier.

Here is an example of how it is used. This is taken from the menu scripts, which handles the ingame menus, I have cut the code and also added the commented lines myself.

self waittill("menuresponse", menu, response);

switch(response)
{

case "changeweapon":
self closeMenu();
self closeInGameMenu();
if(self.pers["team"] == "allies")
self openMenu(game["menu_weapon_allies"]);
else if(self.pers["team"] == "axis")
self openMenu(game["menu_weapon_axis"]);
break;

case "changeteam":
self closeMenu();
self closeInGameMenu();
self openMenu(game["menu_team"]);
break;

case "muteplayer":
self closeMenu();
self closeInGameMenu();
self openMenu(game["menu_muteplayer"]);
break;

case "callvote":
self closeMenu();
self closeInGameMenu();
self openMenu(game["menu_callvote"]);
break;

default:
//add default action here
break;
}

The first part of the code is where the variable is defined. The game waits until a menu has been activated. The variables recieved are "menu" (the name of the menu activated) and "response" (what option was chosen from the menu). "Response" is the key variable for the 'Switch'.

After the variables have been defined, the Switch function is called. It then checks every "Case" (case is the term used for the possible outcomes of the variable) to find a match, if no match is found, the "Default" case is used. (if you do not have a default case, the script will crash - you can just add an empty one.)

If a match is found, then the function will do ALL the events from that point onwards, which is why you MUST add "break;" at the end of every case, if the break is not existent, then all other case functions will run also.

To use the above example, I shall input my own values to show how the example works...

When I open the menu ingame, I choose the option "changeteam".
The code kicks in and the variable "response" becomes equal to "changeteam".
The switch statement will now look at every case for a positive match.

Once the match is found, everything after the case will happen:
* self closeMenu(); //current menu closes
* self closeInGameMenu(); //close any other ingame menus
* self openMenu(game["menu_team"]); //will open the team menu
* break; //the rest of the switch statement is ended and the code continues

You can also make the script perform the same actions in multiple cases. For example:

self waittill("menuresponse", menu, response);

switch(response)
{

case "changeweapon":
case "changeteam":
case "muteplayer":
case "callvote":
function();
break;

default:
//add default action here
break;
}

This means that is the response variable is: 'changeweapon', 'changeteam', 'muteplayer' or 'callvote', function(); will be called.

== [[Notify / Endon / Waittill]] ==

[[Image:Nutshell.png]] These 3 functions allow you to make a script wait for specific events and then trigger those events in different parts of the scripts.

This one ends the function it is inside when 'thread_restart' is triggered on 'level':

level endon ("thread_restart");

and this triggers the 'killed_player' notification on 'self' (which is a player in this case):

self notify("killed_player");

If you use 'player waittill("x")' or 'player endon("x")', then using a 'level notify("x")' will not trigger either of them - level is not the same entity as player, and all entities' triggers are independant.

Using the functions is easy. Firstly, decide which entity you want to wait for the trigger on. This is a player most of the time, but if you want a global trigger then use 'level'.

Then you must decide which trigger to use. You can choose either "endon" or "waittill" - they are both self explanatory, one will end the function it is running in when triggered, and the other will 'wait' until the specified trigger.

----

Next you decide on a unique name for the trigger. For example...

level endon("a_unique_call");

And to activate this trigger, you use notify on the same entity (level):

level notify("a_unique_call");

You can use as many waittill and endon functions as you want on an entity, in different functions. They will all be triggered by a notify.

Here is a quick example of it in use in multiple threads in the DM gametype...

spawnPlayer()
{
self notify("spawned");

/*... Code snipped ... this is another type of
comment that can span multiple lines. */

}

Callback_PlayerKilled(attacker, some other arguments)
{
self endon("spawned"); //this makes callback_playerkilled() terminate when "spawned" is triggered in spawnplayer().
}

== Random stuff ==

A few useful commands:

To print a large message on the screen:

'''iprintlnbold(stringMessage);'''
or to a specific player:
'''player iprintlnbold(stringMessage);'''

To print a small message on the bottom left of the screen:

'''iprintln(stringMessage);
same as iprintlnbold() to a specific player

To check whether a variable or entity exists:

'''if(isdefined(timetowait))'''
'''wait (timetowait);'''

You can also use functions in if statements, by the returned value:

if(checksomething())
//code here

checksomething()
{
if(var == "hi there!") //remember to use == in if statements to check equality, but var1 = var2 to set equality outside them.
return true;
else
return false;
}

== Sources ==

[[Image:Geographylogo.png]][http://www.codjumper.com/forums/viewtopic.php?t=4011&sid=ed58d3b3f5bfa32350d4670d35c9f781 From CoDJumper.com]

Call of Duty 4: Modding

2008-10-23T20:44:27Z

Novemberdobby:

== Call of Duty 4 Modern Warfare Modding ==

[[Image:Code.png|right]]
* [[Call of Duty 4: Introduction|Introduction to Scripting By Drofder2004]]
**[[Getting Started]]
**[[Using Variables]]
**[[Maths & Operators]]
**[[IFs, Loops & Logic]]
**[[Creating Functions]]
**[[Arrays]]
**[[Switch]]
**[[Notify / Endon / Waittill]]
* [[Call of Duty 4: Models imports|Models Imports]]
* [[Call of Duty 4: Skinning|Skinning]]
* [[Call of Duty 4: Custom Dvars|Custom Dvars]]

== Modding Utils ==
[[Image:Data.png|right]]
* [[Call of Duty 4: Rank Creator|Dobby's Rank Creator]]
* [[Call of Duty 4: Demo Player|Demo Player]]
* [[Call of Duty 4: Skinning Tools|Skinning/Image Tool]]
* [[Call of Duty 4: Xmodel Exporter|Xmodel Exporter]]

== Technical References COD series ==
[[Image:Articles.png|right]]
* [[Call of Duty 4: Scripting Reference|Scripting Reference]]
* [[Call of Duty 4: d3dbsp|The D3DBSP File format]]
* [[Call of Duty 4: MAP file structure|.MAP file structure]]

Call of Duty 4: Modding

2008-10-23T20:43:37Z

Novemberdobby: Undo revision 1834 by Novemberdobby (Talk)

== Call of Duty 4 Modern Warfare Modding ==

[[Image:Code.png|right]]
* [[Call of Duty 4: Introduction|Introduction to Modding By Drofder2004]]
**[[Getting Started]]
**[[Using Variables]]
**[[Maths & Operators]]
**[[IFs, Loops & Logic]]
**[[Creating Functions]]
**[[Arrays]]
**[[Switch]]
**[[Notify / Endon / Waittill]]
* [[Call of Duty 4: Models imports|Models Imports]]
* [[Call of Duty 4: Skinning|Skinning]]
* [[Call of Duty 4: Custom Dvars|Custom Dvars]]

== Modding Utils ==
[[Image:Data.png|right]]
* [[Call of Duty 4: Rank Creator|Dobby's Rank Creator]]
* [[Call of Duty 4: Demo Player|Demo Player]]
* [[Call of Duty 4: Skinning Tools|Skinning/Image Tool]]
* [[Call of Duty 4: Xmodel Exporter|Xmodel Exporter]]

== Technical References COD series ==
[[Image:Articles.png|right]]
* [[Call of Duty 4: Scripting Reference|Scripting Reference]]
* [[Call of Duty 4: d3dbsp|The D3DBSP File format]]
* [[Call of Duty 4: MAP file structure|.MAP file structure]]

Call of Duty 4: Modding

2008-10-23T20:42:04Z

Novemberdobby:

== Call of Duty 4 Modern Warfare Modding ==

[[Image:Code.png|right]]
* [[Call of Duty 4: Introduction|Introduction to Scripting By Drofder2004]]
**[[Getting Started]]
**[[Using Variables]]
**[[Maths & Operators]]
**[[IFs, Loops & Logic]]
**[[Creating Functions]]
**[[Arrays]]
**[[Switch()]]
**[[Notify / Endon / Waittill]]
* [[Call of Duty 4: Importing models|Importing models]]
* [[Call of Duty 4: Skinning|Skinning]]
* [[Call of Duty 4: Custom Dvars|Custom Dvars]]

== Modding Utils ==
[[Image:Data.png|right]]
* [[Call of Duty 4: Rank Maker|Dobby's Rank Maker]]
* [[Call of Duty 4: Demo Player|Demo Player]]
* [[Call of Duty 4: Skinning Tools|Skinning/Image Tool]]
* [[Call of Duty 4: Xmodel Exporter|Xmodel Exporter]]

== Technical References COD series ==
[[Image:Articles.png|right]]
* [[Call of Duty 4: Scripting Reference|Scripting Reference]]
* [[Call of Duty 4: d3dbsp|The D3DBSP File format]]
* [[Call of Duty 4: MAP file structure|.MAP file structure]]

Call of Duty 4: Bobbing Models

2008-10-23T18:37:13Z

Novemberdobby: Fixed some stuff and a crash in the code.

[[Category:Call of Duty 4]]
[[Category:Modtools]]
[[Category:Radiant]]
[[Category:Advanced Editing]]
[[Category:Scripting]]
{{warning_forpro}}
[[Image:Nutshell.png]] This tutorial shows how to create 'bobbing' models in water to give a floating movement impression. I got the script from a COD2 tutorials by ''BR3NT''

2 models are animated in this example:

com_bottle4
me_plastic_crate1

[[Image:bobbing_1.png|600px|center]]

== In Radiant ==

Place the 2 models how we want them with their top surface slightly (2/3 units) over the water patch.

[[Image:bobbing_4.png]]

Select the first model, right clic in the 2D window and select ''Script'' then ''Script_model''

[[Image:bobbing_5.png]]

Then witht the first model still selected press 'n' to bring up the entity window and enter the following key/values:

targetname bobbing_obj

Do the same steps for the second model using those:

targetname bobbing_obj2

The result should be:

[[Image:bobbing_2.png]]

and

[[Image:bobbing_3.png]]

== In Script ==

* Create a new file under /raw/maps/mp/ called _bobbing_obj.gsc and insert the following:

<pre>
main()
{
thread bobbing_think();
}

bobbing_think()
{
obj1 = getent("bobbing_obj","targetname"); //get the script_model entity
obj2 = getent("bobbing_obj2","targetname"); //get the other script_model entity

wait (randomfloat (1.5)); //generate a random number of seconds between bobs

org1 = (-83, -895, 688); //define origin or location of your boat/script_model
org2 = (29, -897.1, 683); //define origin or location of your boat/script_model
timer = 1; //bobbing speed - higher number = slower bobbing

while (1)
{
obj1 moveto (org1 + (0,0,2), timer, timer * 0.5, timer * 0.5); // 2 is num. of units to go over Orig.
obj2 moveto (org2 + (0,0,-1), timer, timer * 0.5, timer * 0.5);
wait (timer);
obj1 moveto (org1 + (0,0,-2), timer, timer * 0.5, timer * 0.5); // 2 is num. of units to go over Orig.
obj2 moveto (org2 + (0,0,1), timer, timer * 0.5, timer * 0.5);
wait (timer);
}
}
</pre>

In your main mp GSC, after ''maps\mp\_load::main();'' add this line:

maps\mp\_bobbing_obj::main();

Now, add this to your Zone File:

rawfile,maps/mp/_bobbing_obj.gsc

Compile and test!

--[[User:Zeroy|Zeroy.]] 14:18, 16 October 2008 (UTC)