Custom Map Makers Wiki - User contributions [en-gb]

Bots:Issues

2011-08-25T18:57:57Z

V3nd3tta:

== General ==

It's been made clear that Urban Terror bots are un-supported. Official advice is to not use bots unless you know what you're doing.

== Server use of bots ==

Some server owners like to use bots as a way of enticing players onto an empty server so there is interest in using bots.

A lot of advice for running bots applies mostly to server operators. General rules if you want to run bots.

*Only include 1 or possibly 2 3rd party maps in your maps folder
*Remove all unused .'''pk3''' files from your '''q3ut4''' folder - only include maps that you will use
*Kick all bots after each map and replace them at the start of the next map
*Use the 64-bit binary if possible (64-bit ubuntu is probably the best platform for a bot server)
*If your server isn't capable of running TDM or CTF with 4 bots on casa - don't bother
*Only certain maps support bots
*Add bots one at a time
*Include a large delay between bots entering the server

Bots in Urban Terror are not all that happy. Not all weapons are configured to be used by bots and only ffa, tdm and ctf are understood gametypes

Bots will not use ladders.

Bots will be attracted to dropped weapons over other goals, insist on carrying the flag randomly and sometimes team kill.

== Adding bots ==

Bots are added to the server using the '''addbot''' command. In order to enable bots you will first need to set the server var '''bot_enable=1'''.

Your server will need to be restarted after issuing this command, to do this exec '''server.cfg'''

The addbot command supports the following options

*bot type

*bot level (1-5)

*team (red or blue)

*delay in microseconds before adding this bot

*ingame name

For example : '''addbot boa 4 red 1000 REDBOA'''

Will add a bot with the playername of REDBOA which is a level 4 to the red team after waiting 1000 microseconds (1 second).

=== From RCON ===

The sequence of commands you should issue to add a bot to your server using the /rcon commands.

/rcon bot_enable 1
/rcon exec reload
/rcon addbot boa 3 red 1000 Redboa

Will add a bot tot the red team called Redboa.

=== Using a bot script===

If possible it's generally preferable to create a small text file on your server which will help automate adding bots.

Create a file called '''addbots.cfg''' in your servers '''q3ut4''' folder

bot_enable 1
kick allbots
addbot boa 3 red 1000 RedBoa
addbot boa 4 red 2000 HappyBoa
addbot mantis 3 red 3000 RedMantis

You will be able to execute this script from rcon using

/rcon exec addbots.cfg

=== Automatically adding bots when your server starts ===

Having created the server script above and copying this to your server q3ut4 folder add the following to the end of your server.cfg

exec addbots.cfg

== Bot types ==

*boa
*cheetah
*chicken
*cobra
*cockroach
*cougar
*goose
*mantis
*penguin
*puma
*python
*raven
*scarab
*scorpion
*tiger
*widow

===Bot load out===

Name: Boa
Primary: ZM LR300 ML
Secondary: H&K MP5K
Sidearm: .50 Desert Eagle
Grenades: HE Grenades
Item 1: Kevlar Vest

Name: Cheetah
Primary: Kalashnikov AK103
Secondary: Franchi SPAS-12
Sidearm: .50 Desert Eagle
Grenades: HE Grenades
Item 1: Kevlar Vest

Name: Chicken
Primary: H&K G36
Secondary: H&K MP5K
Sidearm: .50 Desert Eagle
Grenades: HE Grenades
Item 1: Kevlar Vest

Name: Cobra
Primary: ZM LR300 ML
Secondary: H&K MP5K
Sidearm: .50 Desert Eagle
Grenades: Smoke Grenades
Item 1: Kevlar Vest

Name: Cockroach
Primary: H&K UMP45
Secondary: -
Sidearm: Beretta 92G
Grenades: Flash Grenades
Item 1: Kevlar Vest

Name: Cougar
Primary: H&K G36
Secondary: -
Sidearm: Beretta 92G
Grenades: Flash Grenades
Item 1: Silencer
Item 2: Kevlar Vest

Name: Goose
Primary: H&K 69
Secondary: H&K UMP45
Sidearm: .50 Desert Eagle
Grenades: -
Item 1: Extra Ammo
Item 2: Kevlar Vest

Name: Mantis
Primary: ZM LR300 ML
Secondary: -
Sidearm: Beretta 92G
Grenades: -
Item 1: Laser Sight
Item 2: Silencer
Item 3: Kevlar Vest

Name: Penguin
Primary: ZM LR300 ML
Secondary: -
Sidearm: .50 Desert Eagle
Grenades: -
Item 1: Laser Sight
Item 2: Silencer
Item 3: Kevlar Vest

Name: Puma
Primary: ZM LR300 ML
Secondary: -
Sidearm: Beretta 92G
Grenades: -
Item 1: Laser Sight
Item 2: Silencer
Item 3: Kevlar Vest

Name: Python
Primary: H&K G36
Secondary: Franchi SPAS-12
Sidearm: .50 Desert Eagle
Grenades: HE Grenades
Item 1: Kevlar Vest

Name: Raven
Primary: H&K PSG-1
Secondary: H&K MP5K
Sidearm: .50 Desert Eagle
Grenades: -
Item 1: Kevlar Vest
Item 2: Silencer

Name: Scarab
Primary: H&K G36
Secondary: H&K MP5K
Sidearm: .50 Desert Eagle
Grenades: -
Item 1: Kevlar Vest
Item 2: Silencer

Name: Scorpion
Primary: Remington SR8
Secondary: H&K MP5K
Sidearm: Beretta 92G
Grenades: HE Grenades
Item 1: Kevlar Vest

Name: Tiger
Primary: Kalashnikov AK103
Secondary: -
Sidearm: Beretta 92G
Grenades: HE Grenades
Item 1: Medkit
Item 2: Kevlar Vest

Name: Widow
Primary: ZM LR300 ML
Secondary: H&K MP5K
Sidearm: Beretta 92G
Grenades: -
Item 1: Kevlar Vest
Item 2: Laser Sight

== Making maps with bots ==

=== Attracting Bots to walk ===
Simplify map, put info_botroam in areas which you want the bots to be more.

They will most likely if they see the botroam go there and walk somehow around it,

if you guide the bots very good with botroams and donotenter brushes,

you can archieve maybe somehow your goal of creating a game flow for the bots.

=== Making Bots work easier ===

Botclip all complex structures they should not access, like clipping a complex fountain or some trees and Mapmodels with a wider box.

Botclip stairs with a ramp to make it easier for them to walk on the stairs.

Put common/donotenter in areas where bots should not go in - they will most likely not go in there, but if they are in the brush they behave normally.

Very useful to stop bots going around in spawns with spawn-doors, or buggy corners and such.

Also putting in your map some areaportals let the bot not load the complete map at one, they can think easier (heh did I just say they think lol?).

This may lower the the Processing Power needed by the Server or the Local Game to process the Bot's Actions.

 [[Category:Bots]]

User talk:V3nd3tta

2011-08-25T18:57:31Z

V3nd3tta: Created page with "[25/08/2011] v3nd3tta: Call me V"

[25/08/2011] v3nd3tta: Call me V

Bots:Issues

2011-08-25T18:56:27Z

V3nd3tta:

== General ==

It's been made clear that Urban Terror bots are un-supported. Official advice is to not use bots unless you know what you're doing.

== Server use of bots ==

Some server owners like to use bots as a way of enticing players onto an empty server so there is interest in using bots.

A lot of advice for running bots applies mostly to server operators. General rules if you want to run bots.

*Only include 1 or possibly 2 3rd party maps in your maps folder
*Remove all unused .'''pk3''' files from your '''q3ut4''' folder - only include maps that you will use
*Kick all bots after each map and replace them at the start of the next map
*Use the 64-bit binary if possible (64-bit ubuntu is probably the best platform for a bot server)
*If your server isn't capable of running TDM or CTF with 4 bots on casa - don't bother
*Only certain maps support bots
*Add bots one at a time
*Include a large delay between bots entering the server

Bots in Urban Terror are not all that happy. Not all weapons are configured to be used by bots and only ffa, tdm and ctf are understood gametypes

Bots will not use ladders.

Bots will be attracted to dropped weapons over other goals, insist on carrying the flag randomly and sometimes team kill.

== Adding bots ==

Bots are added to the server using the '''addbot''' command. In order to enable bots you will first need to set the server var '''bot_enable=1'''.

Your server will need to be restarted after issuing this command, to do this exec '''server.cfg'''

The addbot command supports the following options

*bot type

*bot level (1-5)

*team (red or blue)

*delay in microseconds before adding this bot

*ingame name

For example : '''addbot boa 4 red 1000 REDBOA'''

Will add a bot with the playername of REDBOA which is a level 4 to the red team after waiting 1000 microseconds (1 second).

=== From RCON ===

The sequence of commands you should issue to add a bot to your server using the /rcon commands.

/rcon bot_enable 1
/rcon exec reload
/rcon addbot boa 3 red 1000 Redboa

Will add a bot tot the red team called Redboa.

=== Using a bot script===

If possible it's generally preferable to create a small text file on your server which will help automate adding bots.

Create a file called '''addbots.cfg''' in your servers '''q3ut4''' folder

bot_enable 1
kick allbots
addbot boa 3 red 1000 RedBoa
addbot boa 4 red 2000 HappyBoa
addbot mantis 3 red 3000 RedMantis

You will be able to execute this script from rcon using

/rcon exec addbots.cfg

=== Automatically adding bots when your server starts ===

Having created the server script above and copying this to your server q3ut4 folder add the following to the end of your server.cfg

exec addbots.cfg

== Bot types ==

*boa
*cheetah
*chicken
*cobra
*cockroach
*cougar
*goose
*mantis
*penguin
*puma
*python
*raven
*scarab
*scorpion
*tiger
*widow

===Bot load out===

Name: Boa
Primary: ZM LR300 ML
Secondary: H&K MP5K
Sidearm: .50 Desert Eagle
Grenades: HE Grenades
Item 1: Kevlar Vest

Name: Cheetah
Primary: Kalashnikov AK103
Secondary: Franchi SPAS-12
Sidearm: .50 Desert Eagle
Grenades: HE Grenades
Item 1: Kevlar Vest

Name: Chicken
Primary: H&K G36
Secondary: H&K MP5K
Sidearm: .50 Desert Eagle
Grenades: HE Grenades
Item 1: Kevlar Vest

Name: Cobra
Primary: ZM LR300 ML
Secondary: H&K MP5K
Sidearm: .50 Desert Eagle
Grenades: Smoke Grenades
Item 1: Kevlar Vest

Name: Cockroach
Primary: H&K UMP45
Secondary: -
Sidearm: Beretta 92G
Grenades: Flash Grenades
Item 1: Kevlar Vest

Name: Cougar
Primary: H&K G36
Secondary: -
Sidearm: Beretta 92G
Grenades: Flash Grenades
Item 1: Silencer
Item 2: Kevlar Vest

Name: Goose
Primary: H&K 69
Secondary: H&K UMP45
Sidearm: .50 Desert Eagle
Grenades: -
Item 1: Extra Ammo
Item 2: Kevlar Vest

Name: Mantis
Primary: ZM LR300 ML
Secondary: -
Sidearm: Beretta 92G
Grenades: -
Item 1: Laser Sight
Item 2: Silencer
Item 3: Kevlar Vest

Name: Penguin
Primary: ZM LR300 ML
Secondary: -
Sidearm: .50 Desert Eagle
Grenades: -
Item 1: Laser Sight
Item 2: Silencer
Item 3: Kevlar Vest

Name: Puma
Primary: ZM LR300 ML
Secondary: -
Sidearm: Beretta 92G
Grenades: -
Item 1: Laser Sight
Item 2: Silencer
Item 3: Kevlar Vest

Name: Python
Primary: H&K G36
Secondary: Franchi SPAS-12
Sidearm: .50 Desert Eagle
Grenades: HE Grenades
Item 1: Kevlar Vest

Name: Raven
Primary: H&K PSG-1
Secondary: H&K MP5K
Sidearm: .50 Desert Eagle
Grenades: -
Item 1: Kevlar Vest
Item 2: Silencer

Name: Scarab
Primary: H&K G36
Secondary: H&K MP5K
Sidearm: .50 Desert Eagle
Grenades: -
Item 1: Kevlar Vest
Item 2: Silencer

Name: Scorpion
Primary: Remington SR8
Secondary: H&K MP5K
Sidearm: Beretta 92G
Grenades: HE Grenades
Item 1: Kevlar Vest

Name: Tiger
Primary: Kalashnikov AK103
Secondary: -
Sidearm: Beretta 92G
Grenades: HE Grenades
Item 1: Medkit
Item 2: Kevlar Vest

Name: Widow
Primary: ZM LR300 ML
Secondary: H&K MP5K
Sidearm: Beretta 92G
Grenades: -
Item 1: Kevlar Vest
Item 2: Laser Sight

== Making maps with bots ==

=== Attracting Bots to walk ===
Simplify map, put info_botroam in areas which you want the bots to be more.
They will most likely if they see the botroam go there and walk somehow around it,
if you guide the bots very good with botroams and donotenter brushes,
you can archieve maybe somehow your goal of creating a game flow for the bots.

=== Making Bots work easier ===

Botclip all complex structures they should not access, like clipping a complex fountain or some trees and Mapmodels with a wider box.

Botclip stairs with a ramp to make it easier for them to walk on the stairs.

Put common/donotenter in areas where bots should not go in - they will most likely not go in there, but if they are in the brush they behave normally.

Very useful to stop bots going around in spawns with spawn-doors, or buggy corners and such.

Also putting in your map some areaportals let the bot not load the complete map at one, they can think easier (heh did I just say they think lol?).

This may lower the the Processing Power needed by the Server or the Local Game to process the Bot's Actions.

 [[Category:Bots]]

Bots:Issues

2011-08-25T18:51:31Z

V3nd3tta:

== General ==

It's been made clear that Urban Terror bots are un-supported. Official advice is to not use bots unless you know what you're doing.

== Server use of bots ==

Some server owners like to use bots as a way of enticing players onto an empty server so there is interest in using bots.

A lot of advice for running bots applies mostly to server operators. General rules if you want to run bots.

*Only include 1 or possibly 2 3rd party maps in your maps folder
*Remove all unused .'''pk3''' files from your '''q3ut4''' folder - only include maps that you will use
*Kick all bots after each map and replace them at the start of the next map
*Use the 64-bit binary if possible (64-bit ubuntu is probably the best platform for a bot server)
*If your server isn't capable of running TDM or CTF with 4 bots on casa - don't bother
*Only certain maps support bots
*Add bots one at a time
*Include a large delay between bots entering the server

Bots in Urban Terror are not all that happy. Not all weapons are configured to be used by bots and only ffa, tdm and ctf are understood gametypes

Bots will not use ladders.

Bots will be attracted to dropped weapons over other goals, insist on carrying the flag randomly and sometimes team kill.

== Adding bots ==

Bots are added to the server using the '''addbot''' command. In order to enable bots you will first need to set the server var '''bot_enable=1'''.

Your server will need to be restarted after issuing this command, to do this exec '''server.cfg'''

The addbot command supports the following options

*bot type

*bot level (1-5)

*team (red or blue)

*delay in microseconds before adding this bot

*ingame name

For example : '''addbot boa 4 red 1000 REDBOA'''

Will add a bot with the playername of REDBOA which is a level 4 to the red team after waiting 1000 microseconds (1 second).

=== From RCON ===

The sequence of commands you should issue to add a bot to your server using the /rcon commands.

/rcon bot_enable 1
/rcon exec reload
/rcon addbot boa 3 red 1000 Redboa

Will add a bot tot the red team called Redboa.

=== Using a bot script===

If possible it's generally preferable to create a small text file on your server which will help automate adding bots.

Create a file called '''addbots.cfg''' in your servers '''q3ut4''' folder

bot_enable 1
kick allbots
addbot boa 3 red 1000 RedBoa
addbot boa 4 red 2000 HappyBoa
addbot mantis 3 red 3000 RedMantis

You will be able to execute this script from rcon using

/rcon exec addbots.cfg

=== Automatically adding bots when your server starts ===

Having created the server script above and copying this to your server q3ut4 folder add the following to the end of your server.cfg

exec addbots.cfg

== Bot types ==

*boa
*cheetah
*chicken
*cobra
*cockroach
*cougar
*goose
*mantis
*penguin
*puma
*python
*raven
*scarab
*scorpion
*tiger
*widow

===Bot load out===

Name: Boa
Primary: ZM LR300 ML
Secondary: H&K MP5K
Sidearm: .50 Desert Eagle
Grenades: HE Grenades
Item 1: Kevlar Vest

Name: Cheetah
Primary: Kalashnikov AK103
Secondary: Franchi SPAS-12
Sidearm: .50 Desert Eagle
Grenades: HE Grenades
Item 1: Kevlar Vest

Name: Chicken
Primary: H&K G36
Secondary: H&K MP5K
Sidearm: .50 Desert Eagle
Grenades: HE Grenades
Item 1: Kevlar Vest

Name: Cobra
Primary: ZM LR300 ML
Secondary: H&K MP5K
Sidearm: .50 Desert Eagle
Grenades: Smoke Grenades
Item 1: Kevlar Vest

Name: Cockroach
Primary: H&K UMP45
Secondary: -
Sidearm: Beretta 92G
Grenades: Flash Grenades
Item 1: Kevlar Vest

Name: Cougar
Primary: H&K G36
Secondary: -
Sidearm: Beretta 92G
Grenades: Flash Grenades
Item 1: Silencer
Item 2: Kevlar Vest

Name: Goose
Primary: H&K 69
Secondary: H&K UMP45
Sidearm: .50 Desert Eagle
Grenades: -
Item 1: Extra Ammo
Item 2: Kevlar Vest

Name: Mantis
Primary: ZM LR300 ML
Secondary: -
Sidearm: Beretta 92G
Grenades: -
Item 1: Laser Sight
Item 2: Silencer
Item 3: Kevlar Vest

Name: Penguin
Primary: ZM LR300 ML
Secondary: -
Sidearm: .50 Desert Eagle
Grenades: -
Item 1: Laser Sight
Item 2: Silencer
Item 3: Kevlar Vest

Name: Puma
Primary: ZM LR300 ML
Secondary: -
Sidearm: Beretta 92G
Grenades: -
Item 1: Laser Sight
Item 2: Silencer
Item 3: Kevlar Vest

Name: Python
Primary: H&K G36
Secondary: Franchi SPAS-12
Sidearm: .50 Desert Eagle
Grenades: HE Grenades
Item 1: Kevlar Vest

Name: Raven
Primary: H&K PSG-1
Secondary: H&K MP5K
Sidearm: .50 Desert Eagle
Grenades: -
Item 1: Kevlar Vest
Item 2: Silencer

Name: Scarab
Primary: H&K G36
Secondary: H&K MP5K
Sidearm: .50 Desert Eagle
Grenades: -
Item 1: Kevlar Vest
Item 2: Silencer

Name: Scorpion
Primary: Remington SR8
Secondary: H&K MP5K
Sidearm: Beretta 92G
Grenades: HE Grenades
Item 1: Kevlar Vest

Name: Tiger
Primary: Kalashnikov AK103
Secondary: -
Sidearm: Beretta 92G
Grenades: HE Grenades
Item 1: Medkit
Item 2: Kevlar Vest

Name: Widow
Primary: ZM LR300 ML
Secondary: H&K MP5K
Sidearm: Beretta 92G
Grenades: -
Item 1: Kevlar Vest
Item 2: Laser Sight

== Making maps with bots ==

Simplify map, info_botroam
Botclip all complex structures they should not access, like clipping a complex fountain with a wider box.
Botclip stairs with a ramp to make it easier for them to walk on the stairs.
Put common/donotenter in areas where bots should not go in - they will most likely not go in there, but if they are in the brush they behave normally.
Very useful to stop bots going around in spawns with spawn-doors, or buggy corners and such.
Also putting in your map some areaportals let the bot not load the complete map at one, they can think easier (heh did I just say they think lol?).

 [[Category:Bots]]

IRC

2011-08-23T13:30:48Z

V3nd3tta:

== IRC ==

The CustomMapMakers.org Team has an IRC Channel to support You in Real-Time per Text-Chat.

If you do not know what IRC (Internet Relay Chat) is, head over to [http://en.wikipedia.org/wiki/Internet_Relay_Chat Wikipedia]

== CMM @ IRC ==

The CustomMapMakers Community is sitting mostly 24/7 in the '''FreeNode''' IRC Network in the Channel '''#cmm'''

You can join via [http://webchat.freenode.net/?channels=cmm Webchat] or connect with the IRC Program of your choice to one of FreeNode's Servers.

The Servers are listed all [http://freenode.net/irc_servers.shtml here], or you can simply just connect to their random rotation, 'chat.freenode.net'.

The Ports are IRC-standarded, you can connect to Port 6665-6667 (6667 is the default used by all irc Programs, you can leave it blank) or Port 7000 for SSL. More Information on pots can be found [http://freenode.net/irc_servers.shtml here].

Our registered channel ''''#cmm'''' can be joined per typing '/join #cmm' or any other way you tell your program to join the Channel '#cmm'.

We do not have Password Protection, however we may set a password temporally if someone thinks to troll our well-behaved Community.

The FreeNode Network offers Nick Registration based on a account system, you can find all information [http://freenode.net/faq.shtml#userregistration here], however there are some simple things you can do for some extra protection.

You may use SASL & SSL as well as cloak your Hostname (and IP) - for more information contact one of the '''OPs''' of '''#cmm''' or '/query v3nd3tta``' (what opens a private chat to me, v3nd3tta).

== Guidelines ==

You have to apply to the [http://freenode.net/policy.shtml Freenode Policy], the [http://freenode.net/channel_guidelines.shtml Freenode Channel Guidelines] and the [http://freenode.net/philosophy.shtml Freenode Philosophy].

Also if you do a [http://freenode.net/catalysts.shtml Catalyst Role] we might give you special Privilegues, but everything we give you we can revert at any time.

If you do not apply the above Rules or do not chat in a matter under the [http://www.ubuntu.com/community/conduct Code of Conduct] the '''OPs''' are allowed to take any action to reinforce these Rules.

This includes Remenbering you of the [http://www.custommapmakers.org/wiki/index.php?title=Resources:IRC#Guidelines Guidelines], Muting, Kicking, (Temp-)Banning as well as in heavy cases Perm-Banning.

== Channel Operators ==

The Operating users for the '''CMM Freenode IRC Channel''' are at the Moment the users:

* 'v3nd3tta``'
* 'Rylius'
* 'JohnnyEnglish'

You may always ask them for help publicy in the Channel, or PM (/query <name>) them - as long as you stay in the Guidelines - but they may always Ignore you or sometimes be AFK, so be patient.

The List of Operators and their Privilegues may always change, so do not Rely on this basic list.

== Disclaimer ==
 
 
 
The Contents of this Page may always be changed by the Operators and Adminstrators of the CustomMapMakers Community.
 
All Rights Reserved, 2011 The CustomMapMakers.org Community.

IRC

2011-08-23T13:29:09Z

V3nd3tta:

== IRC ==

The CustomMapMakers.org Team has an IRC Channel to support You in Real-Time per Text-Chat.

If you do not know what IRC (Internet Relay Chat) is, head over to [http://en.wikipedia.org/wiki/Internet_Relay_Chat Wikipedia]

== CMM @ IRC ==

The CustomMapMakers Community is sitting mostly 24/7 in the '''FreeNode''' IRC Network in the Channel '''#cmm'''

You can join via [http://webchat.freenode.net/?channels=cmm Webchat] or connect with the IRC Program of your choice to one of FreeNode's Servers.

The Servers are listed all [http://freenode.net/irc_servers.shtml here], or you can simply just connect to their random rotation, 'chat.freenode.net'.

The Ports are IRC-standarded, you can connect to Port 6665-6667 (6667 is the default used by all irc Programs, you can leave it blank) or Port 7000 for SSL. More Information on pots can be found [http://freenode.net/irc_servers.shtml here].

Our registered channel ''''#cmm'''' can be joined per typing '/join #cmm' or any other way you tell your program to join the Channel '#cmm'.

We do not have Password Protection, however we may set a password temporally if someone thinks to troll our well-behaved Community.

The FreeNode Network offers Nick Registration based on a account system, you can find all information [http://freenode.net/faq.shtml#userregistration here], however there are some simple things you can do for some extra protection.

You may use SASL & SSL as well as cloak your Hostname (and IP) - for more information contact one of the '''OPs''' of '''#cmm''' or '/query v3nd3tta``' (what opens a private chat to me, v3nd3tta).

== Guidelines ==

You have to apply to the [http://freenode.net/policy.shtml Freenode Policy], the [http://freenode.net/channel_guidelines.shtml Freenode Channel Guidelines] and the [http://freenode.net/philosophy.shtml Freenode Philosophy].

Also if you do a [http://freenode.net/catalysts.shtml Catalyst Role] we might give you special Privilegues, but everything we give you we can revert at any time.

If you do not apply the above Rules or do not chat in a matter under the [http://www.ubuntu.com/community/conduct Code of Conduct] the '''OPs''' are allowed to take any action to reinforce these Rules.

This includes Remenbering you of the [http://www.custommapmakers.org/wiki/index.php?title=Resources:IRC#Guidelines Guidelines] Muting, Kicking, (Temp-)Banning as well as in heavy cases Perm-Banning.

== Channel Operators ==

The Operating users for the '''CMM Freenode IRC Channel''' are at the Moment the users:

* 'v3nd3tta``'
* 'Rylius'
* 'JohnnyEnglish'

You may always ask them for help publicy in the Channel, or PM (/query <name>) them - as long as you stay in the Guidelines - but they may always Ignore you or sometimes be AFK, so be patient.

The List of Operators and their Privilegues may always change, so do not Rely on this basic list.

== Disclaimer ==
 
 
 
The Contents of this Page may always be changed by the Operators and Adminstrators of the CustomMapMakers Community.
 
All Rights Reserved, 2011 The CustomMapMakers.org Community.

IRC

2011-08-23T13:28:24Z

V3nd3tta: moved Resources:IRC to IRC: Moved to own

{{Template:Stub}}
== IRC ==

The CustomMapMakers.org Team has an IRC Channel to support You in Real-Time per Text-Chat.

If you do not know what IRC (Internet Relay Chat) is, head over to [http://en.wikipedia.org/wiki/Internet_Relay_Chat Wikipedia]

== CMM @ IRC ==

The CustomMapMakers Community is sitting mostly 24/7 in the '''FreeNode''' IRC Network in the Channel '''#cmm'''

You can join via [http://webchat.freenode.net/?channels=cmm Webchat] or connect with the IRC Program of your choice to one of FreeNode's Servers.

The Servers are listed all [http://freenode.net/irc_servers.shtml here], or you can simply just connect to their random rotation, 'chat.freenode.net'.

The Ports are IRC-standarded, you can connect to Port 6665-6667 (6667 is the default used by all irc Programs, you can leave it blank) or Port 7000 for SSL. More Information on pots can be found [http://freenode.net/irc_servers.shtml here].

Our registered channel ''''#cmm'''' can be joined per typing '/join #cmm' or any other way you tell your program to join the Channel '#cmm'.

We do not have Password Protection, however we may set a password temporally if someone thinks to troll our well-behaved Community.

The FreeNode Network offers Nick Registration based on a account system, you can find all information [http://freenode.net/faq.shtml#userregistration here], however there are some simple things you can do for some extra protection.

You may use SASL & SSL as well as cloak your Hostname (and IP) - for more information contact one of the '''OPs''' of '''#cmm''' or '/query v3nd3tta``' (what opens a private chat to me, v3nd3tta).

== Guidelines ==

You have to apply to the [http://freenode.net/policy.shtml Freenode Policy], the [http://freenode.net/channel_guidelines.shtml Freenode Channel Guidelines] and the [http://freenode.net/philosophy.shtml Freenode Philosophy].

Also if you do a [http://freenode.net/catalysts.shtml Catalyst Role] we might give you special Privilegues, but everything we give you we can revert at any time.

If you do not apply the above Rules or do not chat in a matter under the [http://www.ubuntu.com/community/conduct Code of Conduct] the '''OPs''' are allowed to take any action to reinforce these Rules.

This includes Remenbering you of the [http://www.custommapmakers.org/wiki/index.php?title=Resources:IRC#Guidelines Guidelines] Muting, Kicking, (Temp-)Banning as well as in heavy cases Perm-Banning.

== Channel Operators ==

The Operating users for the '''CMM Freenode IRC Channel''' are at the Moment the users:

* 'v3nd3tta``'
* 'Rylius'
* 'JohnnyEnglish'

You may always ask them for help publicy in the Channel, or PM (/query <name>) them - as long as you stay in the Guidelines - but they may always Ignore you or sometimes be AFK, so be patient.

The List of Operators and their Privilegues may always change, so do not Rely on this basic list.

== Disclaimer ==
 
 
 
The Contents of this Page may always be changed by the Operators and Adminstrators of the CustomMapMakers Community.
 
All Rights Reserved, 2011 The CustomMapMakers.org Community.

Resources:IRC

2011-08-23T13:28:24Z

V3nd3tta: moved Resources:IRC to IRC: Moved to own

#REDIRECT [[IRC]]

IRC

2011-08-23T13:27:23Z

V3nd3tta: Made a basic IRC tut & disclaimers n sht

Main Page

2011-08-23T11:47:29Z

V3nd3tta: /* Further reading */

__NOTOC__
== Introduction ==
Welcome to the '''Custom Map Makers wiki''' - a repository for all information relating to mapping for the popular first person shooter [http://www.urbanterror.info/ Urban Terror].

If you feel you'd like to contribute to this wiki, please email '''john@custommapmakers.org''' for more information.

The wiki is divided into the following sections, each of these contains further sub-topics. You can also search the wiki using the search box on the top.

== Beginning ==
{| cellspacing="5" width="100%"

|
{{RyMainPageBox|radiant.png|[[:Category:Radiant|Radiant]]|
* [[Radiant:MacRadiant|MacRadiant]]
* [[Radiant:ZeroRadiant|ZeroRadiant]]
* [[Radiant:NetRadiant|NetRadiant]]
* [[Radiant:Shortcuts|Keyboard shortcuts]]
* [[Radiant:Using|Using Radiant]]
|HEIGHT=200px}}

|
{{RyMainPageBox|mapping.png|[[:Category:Mapping|Mapping]]|
* [[Mapping:Brushwork|Brushes]]
* [[Mapping:VIS|VIS]]
* [[Mapping:Patch meshes|Patch Meshes]]
* [[Mapping:Models|Models]]
* [[Mapping:Sky|Sky]]
* [[Mapping:Terrain|Terrain]]
* [[Compiling:Healthy_Map|Healthy Map]]
|HEIGHT=200px}}

|
{{RyMainPageBox|textures.png|[[:Category:Textures|Textures]]|
* [[Textures:Texturing|Texturing]]
* [[Textures:Shaders|Shaders]]
* [[Textures:Sites|Websites]]
* [[Textures:Formats|Formats]]
* [[Textures:Advanced Normal Maps Creation|Normal Maps]]
|HEIGHT=200px}}

|-

|
{{RyMainPageBox|lighting.png|[[:Category:Lighting|Lighting]]|
* [[Lighting:General|General]]
* [[Lighting:Leaks|Light leaks]]
* [[Lighting:Painting|Annoying FrankieV]]
* [[Lighting:Light Style|Light Style]]
|HEIGHT=176px}}

|
{{RyMainPageBox|entities.png|[[:Category:Entities|Entities]]|
* [[Entities:Func|func_*]]
* [[Entities:Info|info_*]]
* [[Entities:Target|target_*]]
* [[Entities:Trigger|trigger_*]]
* [[Entities:Misc|misc_*]]
* [[Entities:UT|ut_*]]
|HEIGHT=176px}}

|
{{RyMainPageBox|compiling.png|[[:Category:Compiling|Compiling]]|
* [[Compiling:q3map2|q3map2]]
* [[Compiling:Commands|Commands]]
* [[Compiling:Surface sounds|Surface sounds]]
* [[Compiling:Setup|Setup]]
* [[Compiling:Batch Files|Batch Files]]
* [[Compiling:Scripts|Scripts]]
|HEIGHT=176px}}

|}

== Advanced ==
{| cellspacing="5" width="100%"

|
{{RyMainPageBox|packaging.png|[[:Category:Packaging|Packaging]]|
* [[Packaging:Levelshot|Making a levelshot]]
* [[Packaging:Minimap|Making a minimap]]
* [[:Category:Packaging|Packaging]]
|HEIGHT=128px}}

|
{{RyMainPageBox|bots.png|[[:Category:Bots|Bots]]|
* [[Bots:Adding bots to your map|Adding bots]]
* [[Bots:Issues|Issues]]
* [[Bots:Advanced|Advanced topics]]
|HEIGHT=128px}}

|
{{RyMainPageBox|urt_hd.png|[[:Category:UrTHD|Urban Terror HD]]|
* [[UrTHD:Setup|Setup]]
* [[UrTHD:Mapping|Mapping]]
|HEIGHT=128px}}

|
{{RyMainPageBox|layout.png|[[:Category:Layout|Layout]]|
* [[Layout:Bens Bible|Ben's small bible]]
|HEIGHT=128px}}

|}
== Further reading ==
{| cellspacing="5" width="100%"

|
{{RyMainPageBox|modelling.png|[[:Category:Models|Modelling]]|
* [[Models:Programs|Programs]]
* [[Models:Exporting|Exporting]]
* [[Models:Texturing|Texturing]]
* [[Models:Resources|Resouces]]
|HEIGHT=176px}}

|
{{RyMainPageBox|resources.png|[[:Category:Resources|Resources]]|
* [[Resources:Tips|Tips and tricks]]
* [[:Category:Inspiration|Inspiration]]
* [[Resources:Tools|Tools]]
* [[Resources:Links|Links]]
* [[Resources:IRC|The CMM IRC Channel]]
|HEIGHT=176px}}

|
{{RyMainPageBox|funstuff.png|[[:Category:Funstuff|Funstuff]]|
* [[Funstuff:Creating|Creating]]
|HEIGHT=176px}}

|
{{RyMainPageBox|xreal.png|[[:Category:XreaL|XreaL]]|
* [[XreaL:About|About]]
* [[XreaL:Setup|Setup]]
* [[XreaL:Games|Games]]
|HEIGHT=176px}}
|}

Main Page

2011-08-23T11:46:00Z

V3nd3tta: /* Further reading */

__NOTOC__
== Introduction ==
Welcome to the '''Custom Map Makers wiki''' - a repository for all information relating to mapping for the popular first person shooter [http://www.urbanterror.info/ Urban Terror].

If you feel you'd like to contribute to this wiki, please email '''john@custommapmakers.org''' for more information.

The wiki is divided into the following sections, each of these contains further sub-topics. You can also search the wiki using the search box on the top.

== Beginning ==
{| cellspacing="5" width="100%"

|
{{RyMainPageBox|radiant.png|[[:Category:Radiant|Radiant]]|
* [[Radiant:MacRadiant|MacRadiant]]
* [[Radiant:ZeroRadiant|ZeroRadiant]]
* [[Radiant:NetRadiant|NetRadiant]]
* [[Radiant:Shortcuts|Keyboard shortcuts]]
* [[Radiant:Using|Using Radiant]]
|HEIGHT=200px}}

|
{{RyMainPageBox|mapping.png|[[:Category:Mapping|Mapping]]|
* [[Mapping:Brushwork|Brushes]]
* [[Mapping:VIS|VIS]]
* [[Mapping:Patch meshes|Patch Meshes]]
* [[Mapping:Models|Models]]
* [[Mapping:Sky|Sky]]
* [[Mapping:Terrain|Terrain]]
* [[Compiling:Healthy_Map|Healthy Map]]
|HEIGHT=200px}}

|
{{RyMainPageBox|textures.png|[[:Category:Textures|Textures]]|
* [[Textures:Texturing|Texturing]]
* [[Textures:Shaders|Shaders]]
* [[Textures:Sites|Websites]]
* [[Textures:Formats|Formats]]
* [[Textures:Advanced Normal Maps Creation|Normal Maps]]
|HEIGHT=200px}}

|-

|
{{RyMainPageBox|lighting.png|[[:Category:Lighting|Lighting]]|
* [[Lighting:General|General]]
* [[Lighting:Leaks|Light leaks]]
* [[Lighting:Painting|Annoying FrankieV]]
* [[Lighting:Light Style|Light Style]]
|HEIGHT=176px}}

|
{{RyMainPageBox|entities.png|[[:Category:Entities|Entities]]|
* [[Entities:Func|func_*]]
* [[Entities:Info|info_*]]
* [[Entities:Target|target_*]]
* [[Entities:Trigger|trigger_*]]
* [[Entities:Misc|misc_*]]
* [[Entities:UT|ut_*]]
|HEIGHT=176px}}

|
{{RyMainPageBox|compiling.png|[[:Category:Compiling|Compiling]]|
* [[Compiling:q3map2|q3map2]]
* [[Compiling:Commands|Commands]]
* [[Compiling:Surface sounds|Surface sounds]]
* [[Compiling:Setup|Setup]]
* [[Compiling:Batch Files|Batch Files]]
* [[Compiling:Scripts|Scripts]]
|HEIGHT=176px}}

|}

== Advanced ==
{| cellspacing="5" width="100%"

|
{{RyMainPageBox|packaging.png|[[:Category:Packaging|Packaging]]|
* [[Packaging:Levelshot|Making a levelshot]]
* [[Packaging:Minimap|Making a minimap]]
* [[:Category:Packaging|Packaging]]
|HEIGHT=128px}}

|
{{RyMainPageBox|bots.png|[[:Category:Bots|Bots]]|
* [[Bots:Adding bots to your map|Adding bots]]
* [[Bots:Issues|Issues]]
* [[Bots:Advanced|Advanced topics]]
|HEIGHT=128px}}

|
{{RyMainPageBox|urt_hd.png|[[:Category:UrTHD|Urban Terror HD]]|
* [[UrTHD:Setup|Setup]]
* [[UrTHD:Mapping|Mapping]]
|HEIGHT=128px}}

|
{{RyMainPageBox|layout.png|[[:Category:Layout|Layout]]|
* [[Layout:Bens Bible|Ben's small bible]]
|HEIGHT=128px}}

|}
== Further reading ==
{| cellspacing="5" width="100%"

|
{{RyMainPageBox|modelling.png|[[:Category:Models|Modelling]]|
* [[Models:Programs|Programs]]
* [[Models:Exporting|Exporting]]
* [[Models:Texturing|Texturing]]
* [[Models:Resources|Resouces]]
|HEIGHT=176px}}

|
{{RyMainPageBox|resources.png|[[:Category:Resources|Resources]]|
* [[Resources:Tips|Tips and tricks]]
* [[:Category:Inspiration|Inspiration]]
* [[Resources:Tools|Tools]]
* [[Resources:Links|Links]]
* [[Resources:IRC|The CMM IRC]]
|HEIGHT=176px}}

|
{{RyMainPageBox|funstuff.png|[[:Category:Funstuff|Funstuff]]|
* [[Funstuff:Creating|Creating]]
|HEIGHT=176px}}

|
{{RyMainPageBox|xreal.png|[[:Category:XreaL|XreaL]]|
* [[XreaL:About|About]]
* [[XreaL:Setup|Setup]]
* [[XreaL:Games|Games]]
|HEIGHT=176px}}
|}

Compiling:Healthy Map

2011-08-23T11:35:20Z

V3nd3tta:

{{WIP}}

The fact that your map compiles fine and it's playable, doesn't mean your map is 'good'. There are several factors which define your map as healthy or unhealthy. An unhealthy map has poor fps, huge .pk3 size and takes longer to load. Your objective is to create a map as small as possible, as fast as possible. In order to do that, make sure you do the right things.
 
 
 
 
 ALL texture sizes must be power of 2 (64,128,256,512,1024 etc).

It will save pk3 space by not wasting texture data. Moreover, it affects your textures quality in game [[[http://www.gotdelirium.com/site/articles_9.html Delirium's Article]]]
 
 
 Don't include .md3 or .qc model files.

 These files are "baked" into .bsp file during compilation, so they are not needed in pk3. This will reduce pk3 size.
 
 Don't create shaders for standard textures:
 

<pre>textures/infiltration/bunkerwall3
{
{
map $lightmap
}
{
map textures/infiltration/bunkerwall3.jpg
blendFunc filter
}
}</pre>

 This shader represents completely normal, common, solid wall. Don't write shaders for them, because texture *lightmap is the standard format. It will save loading time and pk3 space.
 
 Remove unused shaders from shader file.
 
 During developing process you will test many shaders in your shader file. Some of them you will not use in the end. Remove them from shader file.
 
 
 Remove unused textures from pk3
 
 Like above - some textures are dropped in final version. You stop using them for many reasons - make sure you don't put them in final .pk3. It will reduce .pk3 size.
 
 
 Use areaportals to cull rooms hat have all their doors shut.
 
 Learn how to use areaportals and use them in rooms with doors. It will slightly increase FPS on your map.
 
 Don't leave textured surfaces on invisible brushes sides.
 
 Player won't see everything during gameplay - make sure you texture these surfaces with caulk.
 
 This is what player see during game. He sees building, but not complete roof:
 
 [[File:Healthy map 02.jpg]]
 
 
 In ghost mode you can see, that mapper textured roof top with caulk texture:
 
 [[File:Healthy map 01.jpg]]
 
 Roof top cannot be seen during gameplay, so it does not need to be textured. Keep that rule in your mind, it will increase FPS count on your map.

Compiling:Healthy Map

2011-08-23T11:34:43Z

V3nd3tta:

{{WIP}}

The fact that your map compiles fine and it's playable, doesn't mean your map is 'good'. There are several factors which define your map as healthy or unhealthy. An unhealthy map has poor fps, huge .pk3 size and takes longer to load. Your objective is to create a map as small as possible, as fast as possible. In order to do that, make sure you do the right things.
 
 
 
 
 ALL texture sizes must be power of 2 (64,128,256,512,1024 etc).

It will save pk3 space by not wasting texture data. Moreover, it affects your textures quality in game <a href="http://www.gotdelirium.com/site/articles_9.html">Delirium's Article</a>
 
 
 Don't include .md3 or .qc model files.

 These files are "baked" into .bsp file during compilation, so they are not needed in pk3. This will reduce pk3 size.
 
 Don't create shaders for standard textures:
 

<pre>textures/infiltration/bunkerwall3
{
{
map $lightmap
}
{
map textures/infiltration/bunkerwall3.jpg
blendFunc filter
}
}</pre>

 This shader represents completely normal, common, solid wall. Don't write shaders for them, because texture *lightmap is the standard format. It will save loading time and pk3 space.
 
 Remove unused shaders from shader file.
 
 During developing process you will test many shaders in your shader file. Some of them you will not use in the end. Remove them from shader file.
 
 
 Remove unused textures from pk3
 
 Like above - some textures are dropped in final version. You stop using them for many reasons - make sure you don't put them in final .pk3. It will reduce .pk3 size.
 
 
 Use areaportals to cull rooms hat have all their doors shut.
 
 Learn how to use areaportals and use them in rooms with doors. It will slightly increase FPS on your map.
 
 Don't leave textured surfaces on invisible brushes sides.
 
 Player won't see everything during gameplay - make sure you texture these surfaces with caulk.
 
 This is what player see during game. He sees building, but not complete roof:
 
 [[File:Healthy map 02.jpg]]
 
 
 In ghost mode you can see, that mapper textured roof top with caulk texture:
 
 [[File:Healthy map 01.jpg]]
 
 Roof top cannot be seen during gameplay, so it does not need to be textured. Keep that rule in your mind, it will increase FPS count on your map.

Compiling:Healthy Map

2011-08-23T11:34:17Z

V3nd3tta:

{{WIP}}

The fact that your map compiles fine and it's playable, doesn't mean your map is 'good'. There are several factors which define your map as healthy or unhealthy. An unhealthy map has poor fps, huge .pk3 size and takes longer to load. Your objective is to create a map as small as possible, as fast as possible. In order to do that, make sure you do the right things.
 
 
 
 
 ALL texture sizes must be power of 2 (64,128,256,512,1024 etc).

It will save pk3 space by not wasting texture data. Moreover, it affects your textures quality in game [url=http://www.gotdelirium.com/site/articles_9.html]Delirium's Article[/url]
 
 
 Don't include .md3 or .qc model files.

 These files are "baked" into .bsp file during compilation, so they are not needed in pk3. This will reduce pk3 size.
 
 Don't create shaders for standard textures:
 

<pre>textures/infiltration/bunkerwall3
{
{
map $lightmap
}
{
map textures/infiltration/bunkerwall3.jpg
blendFunc filter
}
}</pre>

 This shader represents completely normal, common, solid wall. Don't write shaders for them, because texture *lightmap is the standard format. It will save loading time and pk3 space.
 
 Remove unused shaders from shader file.
 
 During developing process you will test many shaders in your shader file. Some of them you will not use in the end. Remove them from shader file.
 
 
 Remove unused textures from pk3
 
 Like above - some textures are dropped in final version. You stop using them for many reasons - make sure you don't put them in final .pk3. It will reduce .pk3 size.
 
 
 Use areaportals to cull rooms hat have all their doors shut.
 
 Learn how to use areaportals and use them in rooms with doors. It will slightly increase FPS on your map.
 
 Don't leave textured surfaces on invisible brushes sides.
 
 Player won't see everything during gameplay - make sure you texture these surfaces with caulk.
 
 This is what player see during game. He sees building, but not complete roof:
 
 [[File:Healthy map 02.jpg]]
 
 
 In ghost mode you can see, that mapper textured roof top with caulk texture:
 
 [[File:Healthy map 01.jpg]]
 
 Roof top cannot be seen during gameplay, so it does not need to be textured. Keep that rule in your mind, it will increase FPS count on your map.

Mapping:Terrain

2011-08-22T16:16:44Z

V3nd3tta:

{{Stub}}
== External Tools ==
See [[Resources:Tools#Terrain_generation]]

== Patch Meshes ==
Patch Meshes might seem very easy to do Terrain, but it's mostly always not suited for the purpose of walkable grass Terrain or something like that.
You can use Patch Meshes for small simple things like pots of plants which don't really need any great terrain form.
It's really recommended not really use patch meshes where a player can walk - it can be very buggy in movement ways. ;)
Also Patch Meshes have LevelOfDetail and are very bad to handle in that way - phong shaders can be buggy etc.
Just don't use them.

== Trisouping ==

[[Category:Mapping]]

Packaging:Levelshot

2011-08-22T15:55:25Z

V3nd3tta:

== The Template==
At first, you need the Levelshot Template, download it [http://www.urbanterror.info/downloads/static/docs/tutorials/leveldesign/levelshot.zip here].
Edit it with a Pictureditor like Gimp or Photoshop.

== The Screenshot for the Levelshot ==
Look at the best place on your map or the place you want, and make the screenshot with F11(which you add into the template), finally you find it under "q3ut4/screenshots".
It is recommended to make the screenshot with these references:

cg_draw2D 0 -This will remove the GUI
cg_drawHands 0 -This hides the gun
fov 90 -Yes 90, distortion isn't a pretty thing.
r_gamma 1 -Anything other than 1 will make your screenshot look horrible.
r_picmip 0 -Highest quality textures.
r_simpleshaders 0 -If your using the latest renderer, this enables all the new effects.
r_bloom X -Season with bloom to taste; I find r_bloom 4 a nice setting.
r_fancywater 1 -If applicable, enable fancy water.

== Saving the Screenshot ==
Save the levelshot under "q3ut4/levelshots/YOURMAPNAME.tga" and pack it with the right folderpath (levelshots should be the name of the folder) into the .pk3-file from your map.

== Notes ==
* The usual resolution is 1024x1024
* If Possible, enable antialiasing for a sharper screenshot.
[[Category:Packaging]]

Main Page

2011-08-21T15:56:00Z

V3nd3tta:

__NOTOC__
== Introduction ==
Welcome to the '''Custom Map Makers wiki''' - a repository for all information relating to mapping for the popular first person shooter [http://www.urbanterror.info/ Urban Terror].

If you feel you'd like to contribute to this wiki, please email '''john@custommapmakers.org''' for more information.

The wiki is divided into the following sections, each of these contains further sub-topics. You can also search the wiki using the search box on the top.

== Beginning ==
{| cellspacing="5" width="100%"

|
{{RyMainPageBox|radiant.png|[[:Category:Radiant|Radiant]]|
* [[Radiant:MacRadiant|MacRadiant]]
* [[Radiant:ZeroRadiant|ZeroRadiant]]
* [[Radiant:NetRadiant|NetRadiant]]
* [[Radiant:Shortcuts|Keyboard shortcuts]]
* [[Radiant:Using|Using Radiant]]
|HEIGHT=200px}}

|
{{RyMainPageBox|mapping.png|[[:Category:Mapping|Mapping]]|
* [[Mapping:Brushwork|Brushes]]
* [[Mapping:VIS|VIS]]
* [[Mapping:Patch meshes|Patch Meshes]]
* [[Mapping:Models|Models]]
* [[Mapping:Sky|Sky]]
* [[Mapping:Terrain|Terrain]]
* [[Compiling:Healthy_Map|Healthy Map]]
|HEIGHT=200px}}

|
{{RyMainPageBox|textures.png|[[:Category:Textures|Textures]]|
* [[Textures:Texturing|Texturing]]
* [[Textures:Shaders|Shaders]]
* [[Textures:Sites|Websites]]
* [[Textures:Formats|Formats]]
* [[Textures:Advanced Normal Maps Creation|Normal Maps]]
|HEIGHT=200px}}

|-

|
{{RyMainPageBox|lighting.png|[[:Category:Lighting|Lighting]]|
* [[Lighting:General|General]]
* [[Lighting:Leaks|Light leaks]]
* [[Lighting:Painting|Annoying FrankieV]]
* [[Lighting:Light Style|Light Style]]
|HEIGHT=176px}}

|
{{RyMainPageBox|entities.png|[[:Category:Entities|Entities]]|
* [[Entities:Func|func_*]]
* [[Entities:Info|info_*]]
* [[Entities:Target|target_*]]
* [[Entities:Trigger|trigger_*]]
* [[Entities:Misc|misc_*]]
* [[Entities:UT|ut_*]]
|HEIGHT=176px}}

|
{{RyMainPageBox|compiling.png|[[:Category:Compiling|Compiling]]|
* [[Compiling:q3map2|q3map2]]
* [[Compiling:Commands|Commands]]
* [[Compiling:Surface sounds|Surface sounds]]
* [[Compiling:Setup|Setup]]
* [[Compiling:Batch Files|Batch Files]]
* [[Compiling:Scripts|Scripts]]
|HEIGHT=176px}}

|}

== Advanced ==
{| cellspacing="5" width="100%"

|
{{RyMainPageBox|packaging.png|[[:Category:Packaging|Packaging]]|
* [[Packaging:Levelshot|Making a levelshot]]
* [[Packaging:Minimap|Making a minimap]]
* [[:Category:Packaging|Packaging]]
|HEIGHT=128px}}

|
{{RyMainPageBox|bots.png|[[:Category:Bots|Bots]]|
* [[Bots:Adding bots to your map|Adding bots]]
* [[Bots:Issues|Issues]]
* [[Bots:Advanced|Advanced topics]]
|HEIGHT=128px}}

|
{{RyMainPageBox|urt_hd.png|[[:Category:UrTHD|Urban Terror HD]]|
* [[UrTHD:Setup|Setup]]
* [[UrTHD:Mapping|Mapping]]
|HEIGHT=128px}}

|
{{RyMainPageBox|layout.png|[[:Category:Layout|Layout]]|
* [[Layout:Bens Bible|Ben's small bible]]
|HEIGHT=128px}}

|}
== Further reading ==
{| cellspacing="5" width="100%"

|
{{RyMainPageBox|modelling.png|[[:Category:Models|Modelling]]|
* [[Models:Programs|Programs]]
* [[Models:Exporting|Exporting]]
* [[Models:Texturing|Texturing]]
* [[Models:Resources|Resouces]]
|HEIGHT=176px}}

|
{{RyMainPageBox|resources.png|[[:Category:Resources|Resources]]|
* [[Resources:Tips|Tips and tricks]]
* [[:Category:Inspiration|Inspiration]]
* [[Resources:Tools|Tools]]
* [[Resources:Links|Links]]
* [[Resources:IRC|IRC]]
|HEIGHT=176px}}

|
{{RyMainPageBox|funstuff.png|[[:Category:Funstuff|Funstuff]]|
* [[Funstuff:Creating|Creating]]
|HEIGHT=176px}}

|
{{RyMainPageBox|xreal.png|[[:Category:XreaL|XreaL]]|
* [[XreaL:About|About]]
* [[XreaL:Setup|Setup]]
* [[XreaL:Games|Games]]
|HEIGHT=176px}}
|}

Main Page

2011-08-21T15:54:53Z

V3nd3tta:

__NOTOC__
== Introduction ==
Welcome to the '''Custom Map Makers wiki''' - a repository for all information relating to mapping for the popular first person shooter [http://www.urbanterror.info/ Urban Terror].

If you feel you'd like to contribute to this wiki, please email '''john@custommapmakers.org''' for more information.

The wiki is divided into the following sections, each of these contains further sub-topics. You can also search the wiki using the search box on the top.

== Beginning ==
{| cellspacing="5" width="100%"

|
{{RyMainPageBox|radiant.png|[[:Category:Radiant|Radiant]]|
* [[Radiant:MacRadiant|MacRadiant]]
* [[Radiant:ZeroRadiant|ZeroRadiant]]
* [[Radiant:NetRadiant|NetRadiant]]
* [[Radiant:Shortcuts|Keyboard shortcuts]]
* [[Radiant:Using|Using Radiant]]
|HEIGHT=200px}}

|
{{RyMainPageBox|mapping.png|[[:Category:Mapping|Mapping]]|
* [[Mapping:Brushwork|Brushes]]
* [[Mapping:VIS|VIS]]
* [[Mapping:Patch meshes|Patch Meshes]]
* [[Mapping:Models|Models]]
* [[Mapping:Sky|Sky]]
* [[Mapping:Terrain|Terrain]]
* [[Compiling:Healthy_Map|Healthy Map]]
|HEIGHT=200px}}

|
{{RyMainPageBox|textures.png|[[:Category:Textures|Textures]]|
* [[Textures:Texturing|Texturing]]
* [[Textures:Shaders|Shaders]]
* [[Textures:Sites|Websites]]
* [[Textures:Formats|Formats]]
* [[Textures:Advanced Normal Maps Creation|Normal Maps]]
|HEIGHT=200px}}

|-

|
{{RyMainPageBox|lighting.png|[[:Category:Lighting|Lighting]]|
* [[Lighting:General|General]]
* [[Lighting:Leaks|Light leaks]]
* [[Lighting:Painting|Annoying FrankieV]]
* [[Lighting:Light Style|Light Style]]
|HEIGHT=176px}}

|
{{RyMainPageBox|entities.png|[[:Category:Entities|Entities]]|
* [[Entities:Func|func_*]]
* [[Entities:Info|info_*]]
* [[Entities:Target|target_*]]
* [[Entities:Trigger|trigger_*]]
* [[Entities:Misc|misc_*]]
* [[Entities:UT|ut_*]]
|HEIGHT=176px}}

|
{{RyMainPageBox|compiling.png|[[:Category:Compiling|Compiling]]|
* [[Compiling:q3map2|q3map2]]
* [[Compiling:Commands|Commands]]
* [[Compiling:Surface sounds|Surface sounds]]
* [[Compiling:Setup|Setup]]
* [[Compiling:Batch Files|Batch Files]]
* [[Compiling:Scripts|Scripts]]
|HEIGHT=176px}}

|}

== Advanced ==
{| cellspacing="5" width="100%"

|
{{RyMainPageBox|packaging.png|[[:Category:Packaging|Packaging]]|
* [[Packaging:Levelshot|Making a levelshot]]
* [[Packaging:Minimap|Making a minimap]]
* [[:Category:Packaging|Packaging]]
|HEIGHT=128px}}

|
{{RyMainPageBox|bots.png|[[:Category:Bots|Bots]]|
* [[Bots:Adding bots to your map|Adding bots]]
* [[Bots:Issues|Issues]]
* [[Bots:Advanced|Advanced topics]]
|HEIGHT=128px}}

|
{{RyMainPageBox|urt_hd.png|[[:Category:UrTHD|Urban Terror HD]]|
* [[UrTHD:Setup|Setup]]
* [[UrTHD:Mapping|Mapping]]
|HEIGHT=128px}}

|
{{RyMainPageBox|layout.png|[[:Category:Layout|Layout]]|
* [[Layout:Bens Bible|Ben's small bible]]
|HEIGHT=128px}}

|}
== Further reading ==
{| cellspacing="5" width="100%"

|
{{RyMainPageBox|modelling.png|[[:Category:Models|Modelling]]|
* [[Models:Programs|Programs]]
* [[Models:Exporting|Exporting]]
* [[Models:Texturing|Texturing]]
* [[Models:Resources|Resouces]]
|HEIGHT=144px}}

|
{{RyMainPageBox|resources.png|[[:Category:Resources|Resources]]|
* [[Resources:Tips|Tips and tricks]]
* [[:Category:Inspiration|Inspiration]]
* [[Resources:Tools|Tools]]
* [[Resources:Links|Links]]
* [[Resources:IRC|IRC]]
|HEIGHT=144px}}

|
{{RyMainPageBox|funstuff.png|[[:Category:Funstuff|Funstuff]]|
* [[Funstuff:Creating|Creating]]
|HEIGHT=144px}}

|
{{RyMainPageBox|xreal.png|[[:Category:XreaL|XreaL]]|
* [[XreaL:About|About]]
* [[XreaL:Setup|Setup]]
* [[XreaL:Games|Games]]
|HEIGHT=144px}}

|}

Textures:Shaders

2011-08-21T15:47:55Z

V3nd3tta:

{{WIP}}

== Shaders ==

=== Basics ===
A shader is a short text string, that defines the properties of a texture. Using texture in Radiant on solid brush which has to be a simple wall doesn't require to write a shader for it. Every other surface with special attribute - it does. Shaders tells Q3 engine what kind of surface it has to deal with. Wall, water, sky, mirror, etc. You can have sky texture, but it wont act as a 'real' sky in game until you write a shader for it.

Your main shader file should always be named as your map: ut4_mymap.shader. You should keep it in your /scripts folder and also make sure, it's in your shaderlist.txt file, which is also in /scripts folder. You can call shaderlist.txt 'the main list of shaders'. If it is not on the main list, it will not be on the list in the GTK Radiant Level Editor.

You must understand the difference between shader '''file''' and '''shader'''. ut4_yourmap.shader file consists shaders - it might sound complicated, but mappers use term "shader" for every single one texture with special attributes. So when someone speaks about 'shader', he speaks about a particular fragment of your shader file.

Let's use example:

<pre>
textures/ut_subway/plant_bush01

{
qer_editorimage textures/ut_subway/w2k_bush1.tga
surfaceparm trans
surfaceparm nonsolid
//DeformVertexes autosprite2
cull none
nopicmip
{
map textures/ut_subway/w2k_bush1.tga
blendFunc GL_ONE GL_ZERO
alphaFunc GE128
depthWrite
rgbGen identity
}
{
map $lightmap
rgbGen identity
blendFunc GL_DST_COLOR GL_ZERO
depthFunc equal
}
}

textures/ut_subway/chain_link
{
qer_editorimage textures/ut_subway/fence.tga
surfaceparm trans
//surfaceparm nonsolid
//DeformVertexes autosprite2
cull none
nopicmip
{
map textures/ut_subway/fence.tga
blendFunc GL_ONE GL_ZERO
alphaFunc GE128
depthWrite
rgbGen identity
}
{
map $lightmap
rgbGen identity
blendFunc GL_DST_COLOR GL_ZERO
depthFunc equal
}
}
</pre>

This is fragment of shader file for "ut4_subway" map. I pasted 2 shaders from it - for plant_bush01 and chain_link. Your shader file will also consists several shaders written by you.

The most basic shader will consist at least one texture and one script for it. By the time You will learn to create complicated ones, to achieve special and unique effects for your map.
Complete manual explaining all the parameters, strings and variables is here: [http://www.custommapmakers.org/wiki/shaders/index.html here]

== Understanding ==

Shaders are written in a syntax that is really important.

First you write the line how the shader is named - at which "shader" you call it in Radiant.
For Example plant_brush01

<pre>
textures/ut_subway/plant_bush01
</pre>

The Following we can conclude out of the Shader:
It's in the folder 'textures' in the map-specific folder 'ut_subway' - If you have your own textures and your own shader it should be in that folder.
The Path only accepts forward slashes and single slashes - also I heard something like it should always be shorter than 64 signs... so complete sentences as shadername are a no-go :)

(Also some restrictions: Max of 4096 Shader Files, 16384 "shaders" in the Whole Game, 8 Stages, 8 Texture Animations, 4 Texture Modifiers, 3 Deformations and 64 chars for the whole "shader-name-line". Big Shoutout to [[User:Rylius]] for looking it up in the Quake 3 Arena Source. - some Values might have changed but that's basically it what you have to care for.)

You should always name your shaders like your textures, however not _exactly_ the same as I got personally into some bugs with the Images.
Also you should have an own shader name - don't simply copy another shader 1:1 and just change some options. That breaks the Compatibility to one of the two.
So 'textures/<map-specific-folder>/<unique-shader-name>'.

== Conclusion ==

Like famous Rayne said once: 'It's all in the shaders'.

== Good Free Shaders ==

== Common Mistakes ==

 Most common mistakes, which stop shaders from working are:

 Badly written syntax. 

 

For example:

<pre> textures/sky/box374
{
    surfaceparm noimpact
    surfaceparm nomarks
    surfaceparm nolightmap
    surfaceparm sky
    q3map_lightimage textures/sky/box374.tga
    qer_editorimage textures/sky/box374.tga
    q3map_surfacelight 250 //80 mobb2
    //q3map_lightsubdivide 1024
    //q3map_globaltexture
    q3map_sun 1.0 0.55 0.1 725 180 30 //0.85 0.55 0.65 //0.005 0.0 0.0 25 350 20 mobb2
    skyparms env/box374/box374 - -  
</pre>

You see? There is no parenthesis at the end of shader! Very common mistake! It will stop shader from working.

 Bad paths.
 

Same shader, different mistake:

<pre> textures/sky/box374
{
    surfaceparm noimpact
    surfaceparm nomarks
    surfaceparm nolightmap
    surfaceparm sky
    q3map_lightimage textures/WOOOOOOOOT????/box374.tga
    qer_editorimage textures/sky/box374.tga
    q3map_surfacelight 250 //80 mobb2
    //q3map_lightsubdivide 1024
    //q3map_globaltexture
    q3map_sun 1.0 0.55 0.1 725 180 30 //0.85 0.55 0.65 //0.005 0.0 0.0 25 350 20 mobb2
    skyparms env/box374/box374 - - 
}
</pre>
Sometimes you write wrong path to the textures used in a shader. That will also make your shader not work.
 

 [[Category:Textures]]

Custom Map Makers Wiki:General disclaimer

2011-08-20T19:49:11Z

V3nd3tta:

Some of the icons by http://www.fatcow.com/free-icons licensed under Creative Commons Attribution 3.0

We do NOT track any other user data that would be tracked by a pure html-website based http server.

Cookies are set by the Software but you are free to "deny" them - You just can not log in without them.

You are free to link to this Wiki but we don't like to see that you simply "steal" all the contents or parts of it.

If you use a tutorial from this Wiki we would be happy if you backlink to this Wiki in your creation's description.

Custom Map Makers Wiki:General disclaimer

2011-08-20T19:48:29Z

V3nd3tta:

Some icons by http://www.fatcow.com/free-icons licensed under Creative Commons Attribution 3.0
We do NOT track any other user data that would be tracked by a pure html-website based http server.
Cookies are set by the Software but you are free to "deny" them - You just can not log in without them.
You are free to link to this Wiki but we don't like to see that you simply "steal" all the contents or parts of it.
If you use a tutorial from this Wiki we would be happy if you backlink to this Wiki in your creation's description.

Custom Map Makers Wiki:Privacy policy

2011-08-20T19:32:51Z

V3nd3tta:

This Wiki is very similar to the "Bigger Sister" Wikipedia.

You can view their Privacy Policy at the following Page.

http://simple.wikipedia.org/wiki/Wikipedia:Privacy_policy

This Site does not feature manual user registration without Administrator interaction.

So If you have an account you automatically apply to this policy - If you don't you are free to leave.
Just notify one of the Administrators and they will delete your user account.

Your Contents though are under the License of the CMM Wiki from the second you publish them.

Custom Map Makers Wiki:Privacy policy

2011-08-20T19:32:36Z

V3nd3tta:

This Wiki is very similar to the "Bigger Sister" Wikipedia.

You can view their Privacy Policy at the following Page.
http://simple.wikipedia.org/wiki/Wikipedia:Privacy_policy
This Site does not feature manual user registration without Administrator interaction.
So If you have an account you automatically apply to this policy - If you don't you are free to leave.
Just notify one of the Administrators and they will delete your user account.
Your Contents though are under the License of the CMM Wiki from the second you publish them.

Custom Map Makers Wiki:Privacy policy

2011-08-20T19:29:48Z

V3nd3tta: Created page with "This Wiki is very similar to the "Bigger Sister" Wikipedia. You can view their Privacy Policy [url=http://simple.wikipedia.org/wiki/Wikipedia:Privacy_policy]Here[/url] - but this..."

This Wiki is very similar to the "Bigger Sister" Wikipedia.
You can view their Privacy Policy [url=http://simple.wikipedia.org/wiki/Wikipedia:Privacy_policy]Here[/url] - but this Site does not feature manual user registration without Administrator interaction.
So If you have an account you automatically apply to this policy - If you don't you are free to leave.
Just notify one of the Administrators and they will delete your user account.
Your Contents though are under the License of the CMM Wiki from the second you publish them.

Custom Map Makers Wiki:About

2011-08-20T18:22:52Z

V3nd3tta:

'''The custom map makers wiki''' - a repository for mapping for urban terror knowledge

[[File:Custom Map Makers.jpg|600px]]

Custom Map Makers Wiki:About

2011-08-20T18:22:38Z

V3nd3tta:

'''The custom map makers wiki''' - a repository for mapping for urban terror knowledge
&nbsp
[[File:Custom Map Makers.jpg|600px]]

Mapping:Create your first room

2011-08-20T16:46:11Z

V3nd3tta:

==Introduction==
This tutorial aims to help you create your first room and, your first map. The tutorial isn't meant to be "the best way", it's been created to introduce you to good practice, neat brushwork and a consideration of a 10 year old engine (soon to be given a new lease of life).

==Before we begin==
I'm assuming before this tutorial begins that you have a correctly configured radiant, it doesn't matter which, the principles are pretty similar in all versions.

If you've not yet configured radiant please see one of the sections about installing

*links to installing

==First steps==
Before you begin any mapping project you should choose a name for the project and create an empty folder in your textures folder with that name. For the purpose of this tutorial our map is called '''myfirstmap''', it's short and snappy and easy to remember.

Create a folder in your ''mapping/textures'' folder called ''myfirstmap''

Find your '''shaderlist.txt''' file, normally this will be in the ''mapping/scripts'' folder. Open this with a text editor.

Somewhere in this file, add the single line

myfirstmap

Save the file and close the editor

==Textures / images==
For the purpose of this tutorial you'll need a couple of images. Download these 2 files and save them to your mapping/textures/myfirstmap folder

[[File:Plaster.jpg|128px]] [[File:Bricks.jpg|128px]]

Save these files as plaster.jpg and bricks.jpg

File:Xreal.png

2011-08-20T16:30:37Z

Textures:Shaders

2011-08-20T16:03:38Z

V3nd3tta:

{{WIP}}

== Shaders ==

=== Basics ===
A shader is a short text string, that defines the properties of a texture. Using texture in Radiant on solid brush which has to be a simple wall doesn't require to write a shader for it. Every other surface with special attribute - it does. Shaders tells Q3 engine what kind of surface it has to deal with. Wall, water, sky, mirror, etc. You can have sky texture, but it wont act as a 'real' sky in game until you write a shader for it.

Your main shader file should always be named as your map: ut4_mymap.shader. You should keep it in your /scripts folder and also make sure, it's in your shaderlist.txt file, which is also in /scripts folder. You can call shaderlist.txt 'the main list of shaders'. If it is not on the main list, it will not be on the list in the GTK Radiant Level Editor.

You must understand the difference between shader '''file''' and '''shader'''. ut4_yourmap.shader file consists shaders - it might sound complicated, but mappers use term "shader" for every single one texture with special attributes. So when someone speaks about 'shader', he speaks about a particular fragment of your shader file.

Let's use example:

<pre>
textures/ut_subway/plant_bush01

{
qer_editorimage textures/ut_subway/w2k_bush1.tga
surfaceparm trans
surfaceparm nonsolid
//DeformVertexes autosprite2
cull none
nopicmip
{
map textures/ut_subway/w2k_bush1.tga
blendFunc GL_ONE GL_ZERO
alphaFunc GE128
depthWrite
rgbGen identity
}
{
map $lightmap
rgbGen identity
blendFunc GL_DST_COLOR GL_ZERO
depthFunc equal
}
}

textures/ut_subway/chain_link
{
qer_editorimage textures/ut_subway/fence.tga
surfaceparm trans
//surfaceparm nonsolid
//DeformVertexes autosprite2
cull none
nopicmip
{
map textures/ut_subway/fence.tga
blendFunc GL_ONE GL_ZERO
alphaFunc GE128
depthWrite
rgbGen identity
}
{
map $lightmap
rgbGen identity
blendFunc GL_DST_COLOR GL_ZERO
depthFunc equal
}
}
</pre>

This is fragment of shader file for "ut4_subway" map. I pasted 2 shaders from it - for plant_bush01 and chain_link. Your shader file will also consists several shaders written by you.

The most basic shader will consist at least one texture and one script for it. By the time You will learn to create complicated ones, to achieve special and unique effects for your map.
Complete manual explaining all the parameters, strings and variables is here: [http://www.custommapmakers.org/wiki/shaders/index.html here]

== Understanding ==

Shaders are written in a syntax that is really important.

First you write the line how the shader is named - at which "shader" you call it in Radiant.
For Example plant_brush01

<pre>
textures/ut_subway/plant_bush01
</pre>

The Following we can conclude out of the Shader:
It's in the folder 'textures' in the map-specific folder 'ut_subway' - If you have your own textures and your own shader it should be in that folder.
The Path only accepts forward slashes and single slashes - also I heard something like it should always be shorter than 64 signs... so complete sentences as shadername are a no-go :)

(Also some restrictions: Max of 4096 Shader Files, 16384 "shaders" in the Whole Game, 8 Stages, 8 Texture Animations, 4 Texture Modifiers, 3 Deformations and 64 chars for the whole "shader-name-line". Big Shoutout to [User:Rylius] for looking it up in the Quake 3 Arena Source. - some Values might have changed but that's basically it what you have to care for.)

You should always name your shaders like your textures, however not _exactly_ the same as I got personally into some bugs with the Images.
Also you should have an own shader name - don't simply copy another shader 1:1 and just change some options. That breaks the Compatibility to one of the two.
So 'textures/<map-specific-folder>/<unique-shader-name>'.

== Conclusion ==

Like famous Rayne said once: 'It's all in the shaders'.

== Good Free Shaders ==

== Common Mistakes ==

[[Category:Textures]]

Textures:Shaders

2011-08-20T15:54:45Z

V3nd3tta:

{{WIP}}

== Shaders ==

=== Basics ===
A shader is a short text string, that defines the properties of a texture. Using texture in Radiant on solid brush which has to be a simple wall doesn't require to write a shader for it. Every other surface with special attribute - it does. Shaders tells Q3 engine what kind of surface it has to deal with. Wall, water, sky, mirror, etc. You can have sky texture, but it wont act as a 'real' sky in game until you write a shader for it.

Your main shader file should always be named as your map: ut4_mymap.shader. You should keep it in your /scripts folder and also make sure, it's in your shaderlist.txt file, which is also in /scripts folder. You can call shaderlist.txt 'the main list of shaders'. If it is not on the main list, it will not be on the list in the GTK Radiant Level Editor.

You must understand the difference between shader '''file''' and '''shader'''. ut4_yourmap.shader file consists shaders - it might sound complicated, but mappers use term "shader" for every single one texture with special attributes. So when someone speaks about 'shader', he speaks about a particular fragment of your shader file.

Let's use example:

<pre>
textures/ut_subway/plant_bush01

{
qer_editorimage textures/ut_subway/w2k_bush1.tga
surfaceparm trans
surfaceparm nonsolid
//DeformVertexes autosprite2
cull none
nopicmip
{
map textures/ut_subway/w2k_bush1.tga
blendFunc GL_ONE GL_ZERO
alphaFunc GE128
depthWrite
rgbGen identity
}
{
map $lightmap
rgbGen identity
blendFunc GL_DST_COLOR GL_ZERO
depthFunc equal
}
}

textures/ut_subway/chain_link
{
qer_editorimage textures/ut_subway/fence.tga
surfaceparm trans
//surfaceparm nonsolid
//DeformVertexes autosprite2
cull none
nopicmip
{
map textures/ut_subway/fence.tga
blendFunc GL_ONE GL_ZERO
alphaFunc GE128
depthWrite
rgbGen identity
}
{
map $lightmap
rgbGen identity
blendFunc GL_DST_COLOR GL_ZERO
depthFunc equal
}
}
</pre>

This is fragment of shader file for "ut4_subway" map. I pasted 2 shaders from it - for plant_bush01 and chain_link. Your shader file will also consists several shaders written by you.

The most basic shader will consist at least one texture and one script for it. By the time You will learn to create complicated ones, to achieve special and unique effects for your map. Complete manual explaining all the parameters, strings and variables is here: [http://www.custommapmakers.org/wiki/shaders/index.html here]

== Understanding ==

Shaders are written in a syntax that is really important.

First you write the line how the shader is named - at which "shader" you call it in Radiant.
For Example plant_brush01

<pre>
textures/ut_subway/plant_bush01
</pre>

The Following we can conclude out of the Shader:
It's in the folder 'textures' in the map-specific folder 'ut_subway' - If you have your own textures and your own shader it should be in that folder.
The Path only accepts forward slashes and single slashes - also I heard something like it should always be shorter than 64 signs... so complete sentences as shadername are a no-go :)

(Also some restrictions: Max of 4096 Shader Files, 16384 "shaders" in the Whole Game, 8 Stages, 8 Texture Animations, 4 Texture Modifiers, 3 Deformations and 64 chars for the whole "shader-name-line". Big Shoutout to [User:Rylius] for looking it up in the Quake 3 Arena Source. - some Values might have changed but that's basically it what you have to care for.)

You should always name your shaders like your textures, however not _exactly_ the same as I got personally into some bugs with the Images.
Also you should have an own shader name - don't simply copy another shader 1:1 and just change some options. That breaks the Compatibility to one of the two.
So 'textures/<map-specific-folder>/<unique-shader-name>'.

== Conclusion ==

Like famous Rayne said once: 'It's all in the shaders'.

== Good Free Shaders ==

== Common Mistakes ==

[[Category:Textures]]

Textures:Shaders

2011-08-20T15:53:33Z

V3nd3tta: /* Understanding */

{{WIP}}

== Shaders ==

=== Basics ===
A shader is a short text string, that defines the properties of a texture. Using texture in Radiant on solid brush which has to be a simple wall doesn't require to write a shader for it. Every other surface with special attribute - it does. Shaders tells Q3 engine what kind of surface it has to deal with. Wall, water, sky, mirror, etc. You can have sky texture, but it wont act as a 'real' sky in game until you write a shader for it.

Your main shader file should always be named as your map: ut4_mymap.shader. You should keep it in your /scripts folder and also make sure, it's in your shaderlist.txt file, which is also in /scripts folder. You can call shaderlist.txt 'the main list of shaders'. If it is not on the main list, it will not be on the list in the GTK Radiant Level Editor.

You must understand the difference between shader '''file''' and '''shader'''. ut4_yourmap.shader file consists shaders - it might sound complicated, but mappers use term "shader" for every single one texture with special attributes. So when someone speaks about 'shader', he speaks about a particular fragment of your shader file.

Let's use example:

<pre>
textures/ut_subway/plant_bush01

{
qer_editorimage textures/ut_subway/w2k_bush1.tga
surfaceparm trans
surfaceparm nonsolid
//DeformVertexes autosprite2
cull none
nopicmip
{
map textures/ut_subway/w2k_bush1.tga
blendFunc GL_ONE GL_ZERO
alphaFunc GE128
depthWrite
rgbGen identity
}
{
map $lightmap
rgbGen identity
blendFunc GL_DST_COLOR GL_ZERO
depthFunc equal
}
}

textures/ut_subway/chain_link
{
qer_editorimage textures/ut_subway/fence.tga
surfaceparm trans
//surfaceparm nonsolid
//DeformVertexes autosprite2
cull none
nopicmip
{
map textures/ut_subway/fence.tga
blendFunc GL_ONE GL_ZERO
alphaFunc GE128
depthWrite
rgbGen identity
}
{
map $lightmap
rgbGen identity
blendFunc GL_DST_COLOR GL_ZERO
depthFunc equal
}
}
</pre>

This is fragment of shader file for "ut4_subway" map. I pasted 2 shaders from it - for plant_bush01 and chain_link. Your shader file will also consists several shaders written by you.

The most basic shader will consist at least one texture and one script for it. By the time You will learn to create complicated ones, to achieve special and unique effects for your map. Complete manual explaining all the parameters, strings and variables is here: [http://www.custommapmakers.org/wiki/shaders/index.html here]

=== Understanding ===

Shaders are written in a syntax that is really important.

First you write the line how the shader is named - at which "shader" you call it in Radiant.
For Example plant_brush01

<pre>
textures/ut_subway/plant_bush01
</pre>

The Following we can conclude out of the Shader:
It's in the folder 'textures' in the map-specific folder 'ut_subway' - If you have your own textures and your own shader it should be in that folder.
The Path only accepts forward slashes and single slashes - also I heard something like it should always be shorter than 64 signs... so complete sentences as shadername are a no-go :)

(Also some restrictions: Max of 4096 Shader Files, 16384 "shaders" in the Whole Game, 8 Stages, 8 Texture Animations, 4 Texture Modifiers, 3 Deformations and 64 chars for the whole "shader-name-line". Big Shoutout to [User:Rylius] for looking it up in the Quake 3 Arena Source. - some Values might have changed but that's basically it what you have to care for.)

You should always name your shaders like your textures, however not _exactly_ the same as I got personally into some bugs with the Images.
Also you should have an own shader name - don't simply copy another shader 1:1 and just change some options. That breaks the Compatibility to one of the two.
So 'textures/<map-specific-folder>/<unique-shader-name>'.

== Conclusion ==

Like famous Rayne said once: 'It's all in the shaders'.

== Good Free Shaders ==

== Common Mistakes ==

[[Category:Textures]]

Textures:Shaders

2011-08-20T15:52:19Z

V3nd3tta: saving my work - formatting and additions

{{WIP}}

== Shaders ==

=== Basics ===
A shader is a short text string, that defines the properties of a texture. Using texture in Radiant on solid brush which has to be a simple wall doesn't require to write a shader for it. Every other surface with special attribute - it does. Shaders tells Q3 engine what kind of surface it has to deal with. Wall, water, sky, mirror, etc. You can have sky texture, but it wont act as a 'real' sky in game until you write a shader for it.

Your main shader file should always be named as your map: ut4_mymap.shader. You should keep it in your /scripts folder and also make sure, it's in your shaderlist.txt file, which is also in /scripts folder. You can call shaderlist.txt 'the main list of shaders'. If it is not on the main list, it will not be on the list in the GTK Radiant Level Editor.

You must understand the difference between shader '''file''' and '''shader'''. ut4_yourmap.shader file consists shaders - it might sound complicated, but mappers use term "shader" for every single one texture with special attributes. So when someone speaks about 'shader', he speaks about a particular fragment of your shader file.

Let's use example:

<pre>
textures/ut_subway/plant_bush01

{
qer_editorimage textures/ut_subway/w2k_bush1.tga
surfaceparm trans
surfaceparm nonsolid
//DeformVertexes autosprite2
cull none
nopicmip
{
map textures/ut_subway/w2k_bush1.tga
blendFunc GL_ONE GL_ZERO
alphaFunc GE128
depthWrite
rgbGen identity
}
{
map $lightmap
rgbGen identity
blendFunc GL_DST_COLOR GL_ZERO
depthFunc equal
}
}

textures/ut_subway/chain_link
{
qer_editorimage textures/ut_subway/fence.tga
surfaceparm trans
//surfaceparm nonsolid
//DeformVertexes autosprite2
cull none
nopicmip
{
map textures/ut_subway/fence.tga
blendFunc GL_ONE GL_ZERO
alphaFunc GE128
depthWrite
rgbGen identity
}
{
map $lightmap
rgbGen identity
blendFunc GL_DST_COLOR GL_ZERO
depthFunc equal
}
}
</pre>

This is fragment of shader file for "ut4_subway" map. I pasted 2 shaders from it - for plant_bush01 and chain_link. Your shader file will also consists several shaders written by you.

The most basic shader will consist at least one texture and one script for it. By the time You will learn to create complicated ones, to achieve special and unique effects for your map. Complete manual explaining all the parameters, strings and variables is here: [http://www.custommapmakers.org/wiki/shaders/index.html here]

=== Understanding ===

Shaders are written in a syntax that is really important.

First you write the line how the shader is named - at which "shader" you call it in Radiant.
For Example plant_brush01

<pre>
textures/ut_subway/plant_bush01
</pre>

The Following we can conclude out of the Shader:
It's in the folder 'textures' in the map-specific folder 'ut_subway' - If you have your own textures and your own shader it should be in that folder.
The Path only accepts forward slashes and single slashes - also I heard something like it should always be shorter than 64 signs... so complete sentences as shadername are a no-go :)

(Also some restrictions: Max of 4096 Shader Files, 16384 "shaders" in the Whole Game, 8 Stages, 8 Texture Animations, 4 Texture Modifiers, 3 Deformations and 64 chars for the whole "shader-name-line". Big Shoutout to [User:Rylius] for looking it up in the Quake 3 Arena Source. - some Values might have changed but that's basically it what you have to care for.)

You should always name your shaders like your textures, however not _exactly_ the same as I got personally into some bugs with the Images.
Also you should have an own shader name - don't simply copy another shader 1:1 and just change some options. That breaks the Compatibility to one of the two.
So 'textures/<map-specific-folder>/<unique-shader-name>'.

Like famous Rayne said once: 'It's all in the shaders'.

[[Category:Textures]]

User:Rylius

2011-08-20T15:22:54Z

V3nd3tta:

Le me

Edit by v3nd3tta: OMFG IT'S RYLIUS.
If you don't know him you will defenitely get to know him.

If you're not doing everything wrong he may like you... or not. (yeah sorry it's his decision)

Also don't feel bad to be trolled by him. He will do it. Don't ask why. Don't ask when. But be prepared.

User:V3nd3tta

2011-08-20T15:20:14Z

V3nd3tta: Created page with "Call me V"

Call me V

Textures:Shaders

2011-08-20T15:16:45Z

V3nd3tta:

Radiant:ZeroRadiant

2011-08-19T16:30:58Z

V3nd3tta: /* For linux */

==Installation==

===For linux===
[[http://daffy.nerius.com/radiant/ Installing ZeroRadiant for Linux]]

===For windows===
[[Radiant:Install ZeroRadiant Windows]]

[[Category:Radiant]]

Radiant:ZeroRadiant

2011-08-19T16:30:46Z

V3nd3tta: /* For linux */

==Installation==

===For linux===
[[http://daffy.nerius.com/radiant/ |Installing ZeroRadiant for Linux]]

===For windows===
[[Radiant:Install ZeroRadiant Windows]]

[[Category:Radiant]]

File:Modelling.png

2011-08-19T13:11:20Z

V3nd3tta: The Blender Icon - Copyright by the Blender.org Team

The Blender Icon - Copyright by the Blender.org Team

File:Urt hd.png

2011-08-19T13:10:08Z