http://www.urbanterrorhd.info/guidesx/shooting/

Overview of CTF

CTF in Urban Terror is very similar to the real life version of CTF, except you can’t hide your flag up in a tree. If you’ve never played CTF, the gist of it is there are two teams: red and blue. Each team has a flag which is close to their team’s spawn. To score points, you run over to the enemy’s base, grab their flag, and run back with it to your flag. Typically the majority of a team plays on offense, trying to capture the enemy’s flag. One or two players will play as defense, guarding their team’s flag. CTF is played with 5-8 players per team. Anything over that and CTF stands for something else, perhaps involving the word “cluster.” This guide is geared toward newcomers to CTF, and pub play (where half your team will have no clue what’s going on). The original, unposted version of this guide focused more on strategy for organized play, but I decided to change that. I may write a more advanced CTF guide in the future. I am still including advice from a competitive perspective, since I’ve always found it helpful to know what an experience person does in a given situation. It’s difficult to discuss strategy when newcomers may be unfamiliar with the flow of maps. Once you’ve got a few dozen games under your belt, you will be able to apply your experience to your gameplay and become a much greater asset to your team.

Disclaimer: This guide is written by a player experienced with non-wave respawn CTF. There are significant gameplay differences between wave respawn and non-wave respawn, but I don’t feel they are big enough to make this basic CTF guide irrelevant for wave respawn.

There are two primary roles in CTF: offense and defense. The majority of your team should be on offense. Offense should always be pushing up, and should stay in the base as little as necessary. If the offense needs to group back up, this should be done at a forward position, and not in the base (unless you’re getting spawn camped, in which case clearing the base is the #1 priority). How defense is played depends on the map, but generally a defender will sit close to the flag in order to always have a view of it. They will not leave the base or general vicinity of the flag, unless there is a standoff (both teams have the enemy’s flag holed up in their own base), in which case they still might not leave the base, instead choosing to guard their team’s flag carrier from attack (the goal of a standoff is to recover your own flag from the enemy’s base and flag carrier). Defense typically plays from a covered position, such as behind a box, if such a position is available on a map. Defense has the secondary objective of keeping the base clear of spawn campers.

So you’re playing offense

Let’s first decide where you’re going. Have a look at your minimap. Are there any routes which have no arrows? Likely there will be a bunch of arrows going up the middle of the map, and few, if any, at the sides. Whether you want to do something about that depends on what you want to do. If you want to, and think you can, help your team by covering unattended routes of the map, is up to you. By going to undertrafficked routes, you can head off enemies trying to skirt around the main battle in the middle of the map (typically the most trafficked route is the middle, but for some maps this is different) and trying to get a sneaky grab in, and you can also do the same. This is typically referred to as soloing, as you are grabbing the flag with little help. On most servers and maps, it is very easy to reach the enemy’s flag by going through a side route, because few people do this. Your success at grabbing the flag and getting a capture depends on your skill level and whether your teammates are actually making progress with that big firefight in the middle. On more skilled servers, you will probably not find this as easy, as more players will be paying attention to the side routes. A variation of this tactic is called flanking, and all that really means is you’re waiting to grab the flag until your team is in place to help you get out safely. I recommend playing the side routes if you have a decent knowledge of the map and can handle killing enemies without assistance. As I said, this role is typically unfilled or underfilled, so you will be helping your team.

If you are playing with marginally capable players, you may want to consider grouping up with some of them. A group of skilled players in a pub will have a tremendous impact. It doesn’t have to be an official pact, you can just follow someone around and help them out. Two guns are better than one. Having a teammate or two around you is very helpful when dealing with multiple defenders. Often times you wll find several enemy players just sitting on their flag, and it’s hard to kill 3 people shooting at you no matter how bad they are. Finding the competent players on your team is not hard; in any given pub, at least half of the players will never bother to move toward the flag. They just hang around the middle of the map and only occasionally reach the enemy flag. The arrows which are consistently advancing on the enemy flag are the ones you want to be with. If you don’t think you can hang with them in the killing department, take a medpack and keep them full of life. Just don’t be an overzealous medic.

Basic tips for playing alongside another player:

- Keep your distance. Don’t be right behind him blocking him every time he tries to move. On the other hand, don’t be so far away you can’t give cover.

- Split up sometimes. Is he climbing some stairs on Abbey? Stay on the ground and cover him. By taking a different angle, you can provide greater cover by filling in for his weaknesses in position.

- Know his arrow/armband color. Some servers have retarded settings and make everyone the same arrow color, but most don’t, so you can memorize his color.

- Provide cover when he grabs the flag. This applies whether or not you’re grouping up with another player. Any time a teammate grabs the flag, give him cover. I’ll discuss this more under flag running.

Most of the time, on offense, you’ll die before reaching the flag. But sometimes you’ll reach the flag. What do you do?!

Flag running

If you’re the only person by the flag, take it and go. If you have teammates around, do a quick check of who has the most health. The healthiest player should grab. In an organized match with VOIP, it might be beneficial to do a quick poll of who has the most stamina (= longest initial range after the grab), but I don’t think any clan ever does this.:P Anyway, the healthiest person grabs, unless they’re not paying attention, in which case you should just grab as by reading this guide, you’ll be better equipped to handle the flag run than some random newbie!

First, let’s discuss a teammate grabbing. Have a look at the minimap. If you have teammates in place to cover him back to the base, you should stay at the enemy’s base and hold them back. If your flag carrier has no cover once he leaves the enemy’s base, you should go with him. Keep him safe. The same rules apply as working with a teammate, except you might want to follow closer or go ahead of him. Whether you lead or follow depends on whether the enemy will be on your tail or not. If they’re stuck in their base dealing with your teammates, lead, in case there are enemies waiting to ambush you ahead. If their base is clear, they’ll be able to chase after you full speed, in which case it’s better if you’re the first person they shoot. Oh, and obviously if you have an oblivious flag carrier who doesn’t know any of this, you’ll just have to do whatever you can to chauffer him back. A good knowledge of the map and its routes will aide you in covering your teammate. I often run ahead of my teammate to “checkpoints” where the enemy can converge on our route, making sure any resistance is dead before the FC is in danger.

If you are the one to grab the flag, you have to decide where to go. If you have teammates nearby, head toward them. Otherwise I advise going back the route you came, to be safe. This should be your default exit strategy, which is modified if you’re doing something crafty, or you have teammates holding down an area/exit. If you’re a fast player, you might want to do something really crazy like head past the enemy’s spawn to an exit which leads to greater cover. Typically, though, you will want to either head back the way you came, or go to a low-traffic route (the market on Casa, for example). You should be getting out of the enemy’s base as fast as possible. They have a stamina and range advantage because they spawn with a full health bar. You need to get as much distance as possible between you in order to reach your teammates or reach a diverging path to throw the enemy off your trail. Sometimes you can hide in a corner and let the enemies run past, but experienced players are smart enough to check hiding places. I probably have something like a 95% success rate at killing “crafty” flag carriers who think they can just let me blunder past. Just run home as fast as you can.

What should I wear on offense?

This could also be titled “Do I need a vest?”

Depends on your play style. I guess that’s a copout answer, but it really does. I have always worn a vest in CTF and always will. You are useless if you die or get heavily wounded. CTF is all about speed (not necessarily range), and even if the vest limits your range, you can at least move in bursts. The vest makes it easier to keep your stamina supply up, because your available stamina depends on your health. Sometimes I will drop my vest after grabbing the flag, but this is maybe 15-25% of the time. If I know I have good cover (= enemy is pushed back into their spawn), I drop the vest and go for a fast cap. Otherwise I leave it on because it’s so easy to get legged by some spamming idiot and then your extra range is useless. If I have a vest, I stand a very high chance of killing an attacker. It also depends on the map. For example, on Casa, when I am grabbing the red flag, I prefer to drop my vest as I can make it home at full speed with a full stamina bar and no vest. If I wear a vest, I run to weapon crates from the fountain because my range is too short to make it all the way to the blue flag. On Abbey I also drop my vest so I can make quick caps. Even wounded I can make it from the blue flag to the red flag through the middle in just seconds. Red to blue is just possible with a full bar of stamina and the vest, but it’s such a small map you will probably be wounded once you reach a flag, that you may need to drop the vest to have enough range. If you can’t jump fast, don’t even bother dropping your vest. The only time you should even consider dropping the vest is if you can make more use of the extra stamina than the extra protection. As for going completely vestless (i.e., not even spawning with one), I personally don’t recommend it, but some players might. In my experience, there are no top players who are more effective without a vest than with one. This section doesn’t apply to wave respawn CTF, where dying isn’t such a big deal.

Of course you can play without a vest if you enjoy that. I just assume people reading guides are looking for ways to be more effective and a better player, and my recommendation is to wear a vest.

So you’re stuck on defense

Defense is a thankless job and is most of the time not something people are clamoring to play. It can be really boring and really nerve wracking because you have a lot of responsibility, and sometimes no backup. And most of the time you’re just standing around trying to pick up on any enemies before they know where you are. That said, someone needs to play on defense, and all the better if that person has actually bothered to educate themselves on how.

First off, you’re going to find somewhere to camp. Preferably with some cover. I’ve attached a list of nice/common defense spots for various popular maps. Your goal obviously is to not let that flag move outside of the base. Letting people steal it is fine as long as they are promptly going to drop it on the ground after you kill them. Don’t worry, your team will help you out with this because some of the offensive players will have to pass through the flag area, and hopefully they’re also making a good effort to stop enemies from getting anywhere near your base. As the defender, you are the last line of defense preventing your flag from leaving the base.

Your camping spotS should have good cover and a clear view of the flag. Being oriented so that you are aiming mostly parallel to routes taken by fast grabs (i.e., the runner is traveling at a decent speed) is also good, because you have longer to shoot a fast grabber, and you also get a better target by shooting their back. Your biggest challenge will be the fast grabbers who come from out of nowhere (probably by flanking past your teammates who failed in covering a side route). Ideally, if a large force advances on your flag, it will be because your teammates died, and said teammates will respawn very soon.

If you have chosen a good spot, you will have several seconds before a flag carrier is out of your sight. If a flag carrier gets away, it’s your decision to judge whether or not to give chase. Again, it depends on the map and situation. If you have teammates alive, and in a position to intercept (i.e., they’re not in your base), it’s best to hang back and let someone else return the flag. If you’re the only one alive and you think you can catch the carrier, give chase. It’s very important to wound them as much as you can before they are out of your sight, because that will decrease their stamina and a leg shot will slow them down, allowing you to catch up. It also depends on map geography. A map like Casa will give you a very good chance of catching your prey, as it is very open in the middle. A map like Sanc makes it much harder, as there are a lot of corners and rooms. If you are not right on their tail, you might not ever catch them, especially if they have some stamina and didn’t do something dumb like hiding in a corner. Checking corners does not take a lot of time, and especially in pubs, a lot of players like to do silly things with the flag. If your prey took a bad route which will cost them time, you should take a faster one to intercept. Like if someone runs to market from red base, you can just run to New Alley and intercept them. Once you do catch the flag carrier, you should turn on your tunnel vision and go straight for them, ignoring any of their teammates (unless the teammates are significantly closer to you than you are to the carrier). It’s suicidal, but you will be surprised how many times it works. I’ve done this several times even against top teams. There is a slight delay after standing on the flag to it actually returning. The flag has to fall to the ground first, and during this brief fall, you can’t return it. It must be on the ground. This is such a stupid bug, but it is what it is, and you have to take that into account. It’s still very possible to get a return from a group of enemies, because there is also a delay of sorts for picking the flag up once it falls from a teammate. This might sound a bit kamikaze, but if you take out the enemies one by one, you’ll usually just die unless they’re really low on health.

It’s VERY important to call out which way the flag went. EVERYONE should do this if they see the enemy flag carrier. Have 3 binds, left, right, and middle.

/bind u “say_team FLAG LEFT”
/bind I “say_team FLAG MIDDLE”
/bind o “say_team FLAG RIGHT”

Don’t do radio binds because they’re really annoying.

Even if you are unable to catch up to the carrier (or you were killed in your base before even giving chase), someone else might be able to intercept the carrier. But only if they actually know the flag is coming. I’ve had it happen often that a flag carrier sneaks up behind me and kills me because I was laying in wait for him from another route.

Standoffs

Quick section. A standoff is when both teams have the enemy flag, so nobody can cap until a flag is returned. Unless your team is down on points late in the game, there should always be one person with your flag carrier, to guard them. The defender is of course the natural choice, but especially in pubs, nobody really wants to guard the carrier. If your team is losing late in the game, it’s imperative to return the flag and make a capture. Vice versa, if your team has a small lead late in the game, you should have a stronger defense for the carrier. Returning a flag is quite easy, and I find it works best just to sneak past all the enemy offensive players, so you don’t risk getting shot/killed. The suicidal push I described in the Defense section works well here too. Just run right for the carrier and kill them. If you time it right, the flag will be on the ground by the time you reach it. Just do this over and over until you get a return. If the enemy has really heavy defense, it’s best to wait for some of your teammates to make it across the map, but I find that most of the time, most players just do dumb things like throw smoke grenades or try to kill spawnprotected enemies. Of course if their chaos lets you sneak past…

Useful binds for CTF

/bind x “say_team FLAG LEFT”
/bind x “say_team FLAG MIDDLE”
/bind x “say_team FLAG RIGHT”
/bind x “say_team FLAG FLAG FLAG”
/bind x “ut_itemdrop flag; say_team DROPPING FLAG”
/bind x “ut_itemdrop kevlar”

Popular defense positions

1. Set a clear objective

At the beginning of your gaming session, set an objective for yourself to be acomplished at the end of the same session. Set the objective that you feel more comfortable with. It shouldn’t be “WIN” or “PWN EVERYONE” since they are too generic and you will forget them soon. Set a more specific objective like “Get at least 15 headshots” or “Kill 5 opponents with the DE” or “Kill 5 opponents with the Grenades” and so on. This objective will work as a milestone for your mind and will help you being more focused.

2. Eliminate distractions

Sometimes getting a kill is a matter of a fraction of a second. If you get distracted by something you can’t just go back to the game. If you stop for writing something you will need at least 10 or 15 seconds to get mentally back to the game. Try to eliminate as much sources of distractions as possible. For example:

• Set up your HUD correctly.
  If chat messages are distracting you, disable them. At least in important matches. The net graph also can be a source of distraction, along with the data from the hits and so on.
• Play with earphones.
  Earphones can give you a huge boost in concentration, especially if they have noise cancelling. They will help you getting into the game and being more reactive to sounds.
• Set up your playing zone
  You can’t think about getting frags and not hitting the table lamp with the mouse at the same time. Make order. You have to be comfortable and effective at the same time. Instead of yelling to the old 486 mouse, why not getting a new one?

3. Give yourself a deadline

Run against something. Usually I use the timelimit of the map. In that 15 minutes I must accomplish my objective. Don’t fight against your opponents. Fight against the timer. This will help you in two ways:

• It will make you more focused on your objective.
• It will raise a sense of urgency in you, wich will increase your will for success.

4. Think

At the beginning you have to think. You have to write some schemes into your brain. Like the first time you played Turnpike. You didn’t have a clue on where to go or which were the best spots for your Sr-8. Then it became natural for you. Also you have to overwrite some bad schemes that you have already set. For example maybe you’re not circle jumping in the correct way. When you face an opponent, think counciously on what to do. Give a quick command to your brain: “Headshot”. Then your brain and body will focus on getting the headshot. If you give yourself the command “OMG I hope he doesn’t PWN me” you won’t go that far.

5. Don’t think

This might sound awkward. But as you play you must concentrate on thinking less and acting more.

Empty your mind, be formless. Shapeless, like water. If you put water into a cup, it becomes the cup. You put water into a bottle and it becomes the bottle. You put it in a teapot it becomes the teapot. Now, water can flow or it can crash. Be water my friend.
- Bruce Lee

You must free yourself from patterns. Find unusal spots. React according to what is your enemy doing. Be ready to adapt and react. If your enemy is far away consider dropping your LR-300 and pick up the SR-8 from the ground in front of you.

6. Take Breaks

Sometimes you just need a break to be more effective. Feel free to rest when you like. If you are facing an important match incoming (like a league final), just take a rest and be calm. Get there with your mind fresh and ready.

7. Be calm, no negative thinking

If you are nervous, if you think that things are not going as they are supposed to, if someone is annoying you just be calm and relax. Negative thinking like “I’m not hitting anything” or “He’s just going to frag me” will not get you that far. Sometimes player are not just lucky. Sometimes they just will to succeed. Feel free to take a break and be optimistic on your results.
So what do you think? Do you think that this tips can help you? Tell us in the comments. Also, do you have any particular experience? Tell us!

It’s important to define what bad hits is. Bad hits is when you are doing everything right (aiming well, shooting in bursts to keep recoil down, moving intelligently), but for some reason that isn’t working as well as normal. You’re struggling to land successive hits on opponents who aren’t any better than your normal opponents. This is most evident in clan matches when you swap servers and suddenly you can’t hit anything. No one is quite sure what causes this, but the fact remains there are servers on which people just plain can’t hit well. This guide is an action plan for what to do when you encounter bad hits.

Check your connection

Pull down the console and type /cg_lagometer 1. This enables the net graph, which is a visual representation of your connection quality. Ideally, it will look like this:

If it looks similar to any of the following, there’s a problem.

– mild antiwarp

– severe antiwarp

– moderately fluctuating ping

– heavy packet loss

– delayed client-side packets

For a more indepth look at the above images, refer to the following page:
http://www.getlegitanddip.com/dailynade/lagometer.htm

Plan of Action – Observation

If your netgraph looks fine, there are some things you can try.

Check your aim
Are you actually aiming at the enemy? Thoroughly assess how you’re aiming. Is your crosshair on the enemy consistently, or are you only occasionally aimed at your enemy? Try extra hard for a few minutes to make a conscious effort to aim well. Although you may not normally have to do this, some servers seem to require a little extra aiming effort to get acceptable hits. Watch your crosshair, not the enemy.

Check your shooting
Are you shooting properly? Is your cone of spread consistently small enough to ensure reliable hits? If you’re spamming, you’re not going to be getting hits. In addition to aiming well, try taking extra care while shooting to see if your hits pick up.

Ensure you are using good network settings
Set your rate to 25000 (/rate 25000). Set your maxpackets to 42 (/cl_maxpackets 42). As you saw in the above selection of netgraph images, a low rate can cause data sent to the server to be delayed. Increasing your max packets means there is less of an impact if a packet is delayed.

Consider the skill of your opponents
Are you playing unusually good opponents? I never write a server off as hitting bad unless I know the skill level of my opponents. Veteran players will move more intelligently, thus requiring better aim to track. Of course if you’re in a clan match and suddenly you can’t hit anything after a server switch, you can be pretty sure it’s nothing to do with your opponents’ skill are doing.;) Watch how your opponents play, and if they’re doing things that make it hard to aim at them. Intelligent use of cover, jumping, crouching, and sliding all make it much harder to get a bead on your target.

Give yourself a mental and physical once-over
Are you stressed? Tired? Angry? Emotions have physical manifestations. Anxiety makes you shaky and jumpy. Anger makes you reckless and short tempered. Being sleep deprived makes your reaction times slower. Physical exhaustion makes your reactions and movements slower and sometimes shaky. Unless you’re rested and relaxed, you’re not going to be playing at top form. Take a good look at yourself and decide whether you’re physically and mentally in the zone. If not, gtfo and take a break!

Plan of Action – Execution

So you’re doing everything right and you’re still hitting like garbage. Now it’s time to try to do something about it!

LEAVE
Vote with your feet. Find a new server. No sense playing on a lousy server, not getting proper hits, and as a result, not having any fun. This is a game, games are about fun. Of course if you’re in an organized clan match, you can’t just up and leave! In a match, try not to whine about hits too much; it brings morale down.

Switch to a different role
In my experience, the SR8 does not suffer from bad hits like the automatics, probably because less data is required to be processed for one bullet every few seconds. In some cases you may be able to contribute to your team more with the SR8, even if you are fulfilling the same position as you were with the auto. It’s generally a good idea to have an automatic when on offense in CTF, but if you can kill more reliably with the SR8, that switch may help. Switching to a defensive role where you can take cover and have a positional advantage can also help because you have more time to kill an enemy.

Switch guns
Instead of an LR, try an M4, AK103, or G36. The different spread patterns might mitigate the bad hits, or the higher damage of the AK103 might make it easier to kill enemies with less hits.

Flank
Instead of facing enemies head on, flank around and shoot them in the back. The surprise advantage should give you enough time to finish them off.

Think positively
Don’t keep blaming bad hits for everything. You’ve established hits aren’t good, so put that out of your mind and work on being an asset to your team. Keep focusing on aiming well and shooting well, and you may find at the end of the round, although you didn’t play as good as you know you can, you at least contributed to your team. Constantly focusing on the bad hits will just make you angry and in turn make you play even worse.

Conclusion

I hope I’ve made it clear that although many servers do have bad hit detection, players share a big part of the blame too. Keep aiming well, make sure your network settings are optimal, and play to maximize your positional advantage and the time you have to kill enemies. Basically, don’t keep doing what you’re doing, because it’s not working. Switch it up. And remember, it’s just a game!

In Quake 3, one can gain speed by moving diagonally. The fastest way to do this in Urban Terror is called circle jumping – aptly named because of the circular arcs that form a circle-jumper’s trajectory. This method is far more useful in Urban Terror (rather than in vanilla Quake) because sprinting forward is miles faster than strafing sideways.

The first few hops cannot curve too much as otherwise your direction will change too quickly to the detriment of your speed. Curve gently while holding forward + sprint as you begin to jump.

When your speed exceeds that of a normal sprint, you would ideally want to hold forward + sprint in the direction perfectly perpendicular to that of your movement, curving your mouselook as your direction changes, to maximize your speed. Try your best to maintain this angle if you wish to jump as fast as you can in any one particular direction. What we have achieved so far is, fundamentally, how one will circle-jump anywhere.

However, you will have to make minor adjustments if you need to navigate the obstacles that normally clutter an Urban Terror map. Power-sliding will also help you maintain most of your speed while giving you a bit of extra distance; this is especially useful when your stamina is running low. As you jump more and more you will gain a feeling for the art. Take a look at jump videos like 2.4f and Mr. Banana’s Curved Speed or Flying-V to see how players navigate skillfully around a map without losing too much speed.

Introduction

I will be examining how various graphical configurations affect framerate on my old computer which was purchased in November 2003. I replaced it over a year and a half ago, but I still keep it around precisely for stuff like this. Pretty much any computer built for $500-700 USD in the past 2-3 years will outperform it with ease. However, prebuilt machines from large manufacturers like Dell or HP often will have proprietary components or just plain wacky configurations which cause them to perform much poorer than their price suggests. If you’re in the old PC or lowend prebuilt boat, this guide should help you improve your gaming experience. I will provide a list of cvars which have an effect on framerate, as well as an already completed graphics config file which you can load from the console.

I may as well spoil it right now, and tell you that there is practically no difference between a high quality configuration and a quickly done low quality configuration. The only noticeable difference (and it’s significant) can be obtained by turning down/off a lot of hidden options through cvars. You can skip the whole article and go straight to the bottom if you just want the config file. The next three sections may be boring/too technical/both.

Urban Terror Graphics

Urban Terror, especially at low resolutions (1024×768 and under), is an example of a CPU bound game. That is, on your average system, in the average in game situation, the CPU will be the limiting factor in getting a higher framerate. The CPU is unable to render its portion of the work any faster, while the GPU (graphics processing unit; found on your video card) can perform all its tasks as fast as the CPU, and then some. In other words, the GPU is waiting for the CPU. This is because Urban Terror’s graphics are quite easy to render in comparison to the physics, player positions, sound, network data, etc. However, this may not always be the case. Many computers, mostly lowend prebuilts, have very weak graphics cards as they are intended for office work. Look at any big box store and you will find quad core CPUs alongside onboard graphics. What is being rendered at a particular moment is, however, the decisive element in determining what component is being “bottlenecked.” A high number of player models on screen, a wide open area on a detailed map, smoke grenades, and a large number of objects (shells, boxes, dropped guns, flags, etc.) on screen, all have a very significant impact on the graphics cards’ ability to render the scene quickly. Conversely, sitting in an enclosed area with few props and no other players on screen will result in the graphics card barely breaking a sweat, while the CPU is still working hard to calculate unseen players’ positions, crunch network data, render sound, etc.

Urban Terror has a hard cap of 125 fps, though the cap can be set lower. Your framerate will not exceed 125 fps. This is due to how the Quake III Engine’s netcode works – it is tied directly to client framerate. The goal of any player should be to get their framerate as STEADY as possible. Reaching 125 fps is all well and good, but it is detrimental to gameplay if as soon as an enemy comes on screen, the framerate plummets to 60. Although a constant framerate of 60 fps might be very playable, the DROP from 125 to 60 fps is extremely noticeable and will make it hard to play, as changes in framerate affect how smoothly the game is seen, aiming, movement (there will be a noticeable delay in input response time if you have FPS drops), and even ping. You have to therefore consider not just maximum frame rate, but minimum frame rate as well. This is what you want to bring up. The difference in an intense firefight between 20 fps and 45 fps is huge, especially if that means a drop of only 15 fps (60 capped dropping to 45) as opposed to 60 fps (uncapped, but running at 80, dropping to 20).

Benchmarks – Hardware Discussion

I will benchmark various configurations and record the results in a chart. The test system will be an Athlon XP 2500+ (Barton core) @ 1.83 ghz (stock speed), 1024 MB DDR333, and an ATI 9600XT 256MB graphics card. For a second set of benchmark runs, the FSB will be underclocked from 166 mhz to 100mhz, resulting in an effective 1.1 ghz for the CPU, and the RAM running at DDR200 rates. A 1.1 ghz Athlon XP would be roughly equivalent to a “1200+” performance rating, when considering the Barton’s 512 kb of L2 cache. A final, third run will be done at 2.2 ghz, equivalent to a 3200+ performance rating. A 3200+ Athlon XP performs on par with a 2.8 ghz Pentium 4.

Benchmarks – Methodology

I am testing 5 graphics configurations.

800×600 stock is simply the default configuration generated by Urban Terror if no configuration file is present. 800×600 is the default resolution.
1024×768 stock is the same configuration, except with the resolution bumped up to 1024×768.
800×600 low is the stock config, but with all the applicable options in the “graphics” tab under the Setup button at the main menu set to their lowest quality setting.
1024×768 high uses Nexu’s movie config file, which is tuned for optimal visual quality.
640×480 very low is a config file I made and turned every visual option to its lowest quality (best performance) setting (generally this means disabled:P). In addition, sound options were set to low quality. On a system with a dedicated sound card, sound quality level will not impact framerate. However, most people have onboard sound, which means the CPU does most of the sound processing work.

I tested each configuration using /timedemo 1 and then replaying a demo of a 6v6 match on Algiers CTF. The demo is approximately 35 minutes long. It contains many firefights, as that is the nature of Algiers, especially against a strong opponent. Smoke grenades are used for approximately one minute. Timedemo records the average framerate of a demo that is played back. Unfortunately minimum FPS is not displayed, but that doesn’t mean we can’t make educated guesses.:) I reloaded Urban Terror between each run. I also deleted all the configuration files in the q3ut4 directory, to allow Urban Terror to regenerate them each run. When a premade config was used, I named it autoexec.cfg, which forces Urban Terror to load cvars from it first, before relying on automatically generated values from q3config.cfg (which are used if a cvar is not present in the autoexec file). A clean install of XP SP3 was installed before testing began.

Benchmarks – Results

FPS testing @ 1830 mhz

Not much difference between the 1024×768 high quality config, and 800×600 with all graphics menu options turned down. In fact it’s a difference of only 7 fps. That’s only 10% worse FPS running with high quality textures and mipmapping (mipmapping determines when a low quality distance texture is swapped for a high quality up close texture; a low quality mipmap setting swaps the textures more abruptly and at closer distances). The difference between 1024×768 stock and 800×600 stock (besides 306,432 pixels less being rendered each frame) is 0.4 fps. However, my special ultra-low quality configuration yielded an astonishing 91.6 fps. That’s almost 20 more fps than the stock configuration! This difference will be seen the most in graphically intense situations, as it is obvious from the other 4 tests that Urban Terror on an Athlon XP 2500+ and 9600XT is CPU bound most of the time. By dropping the graphics quality to extremely low levels, those situations where the graphics card is the bottleneck, become fewer and less intense. It’s better to have a CPU bound game, as in Urban Terror, the CPU’s work load is nearly constant.

FPS testing @ 1100 mhz

The same results are present with only 1100 mhz. Although even the ultra low quality config can’t squeeze an average of 60 fps out of the system, 56.4 fps is better than the 45 fps achieved by the bottom 3 configurations (the high quality config pulling in ~10% less at 40.6 fps). 11 fps may not seem like much, but like I said at the beginning, getting those minimum FPS values up is what we’re after. Most certainly firefights where the FPS was dropping to less than 20 fps, were running at 30-40 fps with the low quality config.

FPS testing @ 2200 mhz

Well, we almost hit 125 fps. The low quality config managed 114.6 FPS average, which means that in many situations, it was running at 125 fps. Intense scenes likely ran around 70-80 FPS. I shelved the 800×600 “low” run, as it was pointless. Instead I did a 1280×1024 run with stock settings…and got the same FPS as 1024×768 stock. That’s great news, as UrT can be run at a 19” LCD’s native resolution at the same speed as 1024×768. Of course to almost completely eliminate the GPU as a bottleneck, you still need to run at super low settings. This 3^rd run is conclusive evidence that UrT is mostly CPU bound, at least on this system. The difference between 1100 mhz and 2200 mhz is literally 100%. And when the CPU is overclocked by ~20%, the results go up around 20%.

CVAR Listening and Breakdown

I’ll list every cvar I changed for my “ultra low” config, write a brief bit of text about it, and give it a rating with regard to how important it is to gameplay (0-5). I am leaving out commands which are by default set to the lowest quality setting and can’t be changed via the menu, since it’s pretty much impossible to change them during routine tweaking. If someone asks me to, though, I’ll make a list of every graphical command that can be changed and try to explain them. I’m also leaving out cvars which are locked by the engine (such as r_vertexlighting). Let’s start with the r_ (renderer) cvars.

r_picmip
Range: 0-2
Default: 1
Recommended: 2

This IS the texture quality cvar. Higher values render blurrier textures. 0 corresponds to High in the menu, 1 to Normal, and 2 to Low. There is a “very low” (3) option in the menu, but this does not work in game, and will be set to the default of 1 if you use it.

Importance: 0 – in fact, many good players will set this to a low value because blurrier textures enhance player model visibility.

r_texturemode
Accepted values: GL_NEAREST, GL_NEAREST_MIPMAP_NEAREST, GL_LINEAR_MIPMAP_NEAREST, GL_NEAREST_MIPMAP_LINEAR, GL_LINEAR_MIPMAP_LINEAR
Default: GL_LINEAR_MIPMAP_NEAREST
Recommended: Maximum FPS, gl_nearest. Otherwise stick to default.

If you’re scratching your head over the values, you’re not alone. gl_linear_mipmap_linear is the best quality, if your video card supports trilinear filtering (it does). gl_nearest is extremely bad quality (so bad in fact the textures are always pixilated and blocky regardless of how close you are) and creates noticeable shimmering and flickering as you get closer to a texture, but I think it’s one of the biggest FPS boosters in my low quality config. gl_nearest_mipmap_nearest is slightly better looking than gl_nearest, but not enough to improve the flickering. So if you want maximum FPS, go for gl_nearest.

Importance: 4 – the low quality ones are headache inducing. I am one of those people who make their graphics ugly in order to increase visibility, but this is just too far. I would only use this if you are in dire need of more frames per second.

r_ext_max_anisotropy
Accepted values: 0-16?
Default: 2
Recommended: 0

To be honest, I’m not sure if this actually matters, as r_ext_texture_filter_anisotropic would logically need to be set to 1 for anisotropy to be active, and it’s by default 0. Most people force anisotropy on via their graphics card’s control panel anyway, if they want to use anisotropic filtering (anisotropic filtering works in conjunction with mipmapping, and causes high quality textures to be used out to an even farther distance). Regardless, there’s no point having this at 2, just in case. Anisotropic filtering is a huge performance hog, especially on low end/older graphics cards.

Importance: 0 – there’s almost no visual difference between even 16x AF and AF disabled, so why take a possible performance hit?

r_ext_multitexture
Accepted values: 0/1
Default: 1
Recommended: 0

Multitexturing makes textures look better at a performance hit for old cards, so why on earth would we leave it on?!

Importance: 0

com_blood
Accepted values: 0/1
Default: 1
Recommended: 1

Although blood can hurt your FPS, especially in a big firefight, blood trails are just too much of a tactical advantage. Well, not if you’re playing TDM. If you play mostly TS and CTF, leave blood on. Otherwise you can turn it off and you probably won’t play any worse.

Importance: 5 – for TS and CTF.
1 – for TDM and FFA

r_stencilbits
Accepted values: 0/8/16
Default: 8
Recommended: 0

This controls the hardware stencil buffer. A stencil buffer can be used to make higher quality shadows and reflections. Shadows already look terrible in Urban Terror, so obviously this doesn’t do a whole lot. Some old video cards don’t even have a stencil buffer, necessitating this be set to “0” in some cases.

Importance: 0

r_roundImagesDown
Accepted values: 0-???
Default: 1
Recommended: 2

I’m not completely sure this even does anything, but you can change the value, and the value will stick (unlike some other commands where the cvar isn’t locked, but the value you set won’t stick). I notice no visual difference between 1 and 4. May as well be safe, I guess.

Importance: 0 – I don’t believe this actually works, so play it safe and set it to 2.

r_detailtextures
Accepted values: 0/1
Default: 1
Recommended: 0

No visual quality difference, again. May as well set it to 0, just in case.

Importance: 0

r_ext_compressed_textures
Accepted values: 0/1
Default: 0
Recommended: 1

Compresses textures, which alleviates bus congestion between the motherboard and the graphics card. In reality, no card will saturate its bus, as the video card industry moved to PCI-e 16x before cards could overwhelm the AGP 8x bus. It may have other effects, though, so set it to 1. There is no visual quality loss.

Importance: 0

r_texturebits
Accepted values: 0/16/32
Default: 32
Recommended: 16

Setting this to 0 will use your desktop’s color depth setting, which is most likely at 32 bit. I believe a 24 bit desktop setting will be interpreted as a 16 bit setting, as Quake III does not support 24 bit color. Don’t leave it up to chance, though – set this to 16.

Importance: 0

r_colorbits
Accepted values: 0/16/32
Default: 32
Recommended: 16

Same as above.

r_mode
Accepted values: 3-9, -1
Default: 4
Recommended: depends

This is the resolution. 3 is 640×480, 4 is 800×600, 5 and 6 are 1024×768, and 8 is 1280×1024. There are more preset resolutions, but those are the most common. -1 allows for a custom resolution using r_customheight and r_customwidth. If you are running a CRT (tube) monitor, you can use any resolution the monitor supports. LCD monitors, however, only look best at their maximum (native) resolution. Lower resolutions on an LCD will be interpolated, and look blurry and boxy. If you are going to use an LCD at a non-native resolution, at least make sure you keep the resolution in proportion to the native resolution. For example, a 19” non-widescreen monitor has a native resolution of 1280×1024. An acceptable non-native resolution, quality-wise, might be 800×640, as both are 62.5% of the native width and height, respectively. Another solution is to use windowed mode (r_fullscreen 0), which allows lower resolutions to be run on an LCD without interpolation. The tradeoff is that the image will not will the screen, and will instead be confined to a small window. This is mostly important for those with weak graphics cards, as my tests revealed resolution has practically no effect on frame rate with the 9600XT.

Importance: 3 – A blocky, interpolated resolution can make it hard to see the action. It’s not too bad, but it’s still worse than the native resolution. If you have a CRT, it doesn’t matter at all as long as you use a 4:3 resolution (take the first number and divide it by the second; if you get 1.3333… you have a 4:3 resolution) for a standard CRT, and a 16:9 resolution for a widescreen CRT (they’re very rare). Lower resolutions on a CRT also allow for a higher refresh rate to be run, reducing eye strain.

r_displayrefresh
Accepted values: 60-85
Default: 60
Recommended: 70-75

This setting is ONLY for CRT users. Refresh rate does not apply to LCD or plasma displays. Everything that proceeds in this paragraph is irrelevant for LCD/plasma displays. The refresh rate for a CRT is how many times per second the screen is redrawn. This is independent on the framerate of the game, as the video card’s RAMDAC is designed to take any framerate and output it at the refresh rate the monitor/software is asking for. However, you can “see” more frames per second with a higher refresh rate. It’s debatable whether you can actually tell the difference between 60 hz and 75 hz (or “fps”) on a monitor, as human eyes don’t work in FPS. The goal of FPS tweaking is to make the game run smoother with regards to enemies not warping around, and having control inputs respond consistently. Anyway, the refresh rate should be around 70-75 hz, as that’s when the flicker disappears for most lighting environments and for most people. In a dark room, you can get away with a lower refresh rate and not see flicker. Most people will see very minimal flicker at 75 hz, and few people can see flicker at 85 hz looking straight on at the monitor. Your peripheral vision has a higher flicker threshold, so if you look at your monitor from the corner of your eye, it might flicker even though it doesn’t when you look straight at it. Higher refresh rates (85hz+) degrade image quality slightly, and besides, many monitors can only run fast refresh rates (75 hz+) at lower resolutions. Few monitors can do over 60 hz at their maximum resolution; that’s the difference between premium monitors like the Sony Trinitrons, and regular CRTs. Make sure the value you set here is supported by your monitor at the resolution you are using!

Importance: 0 – higher refresh rate reduces headache, but won’t really help your game play (besides making it easier to focus on the screen). But it won’t hurt your gameplay in the least. LCD users will not benefit from this setting at all.

cg_sfxMuzzleFlash
Accepted values: 1
Default: 1
Recommended: 1

This is the muzzle flash from guns. The big bright flash when you shoot. It’s really annoying, but there’s a reason many people leave it on – muzzle flashes from other players’ guns are useful. I really don’t think this has any noticeable impact on FPS since most cards handle one or two extra static lights just fine.

Importance: 4 – useful in many situations where you can’t see any enemy but you’ll see the flash of light when they shoot. It’s also very useful when shooting at people through smoke without night vision, as you can still see muzzle flashes.

cg_brassTime / cg_sfxbrasstime
Accepted values: 0-20000
Default: 5000
Recommended: 0

Time in ms for shell casing to stay on the ground. Utterly worthless for gameplay as you can’t even see them at a distance, but they’ll be rendered anyway. Not sure which cvar is active, so set ‘em both to 0.

Importance: 0 – nobody has ever made a kill based off shell casings giving away a position.

g_removeBodyTime
Accepted values: 0-???
Default: 300
Recommended: 300

Just thought I’d put this in here. This does NOTHING, as bodies stay as long as someone is dead, and disappear when they respawn. Unfortunate, as all those corpses have the same number of polygons as a living player. But they’ll be gone quickly anyway.

cg_gunsize
Accepted values: 0/1
Default: 0
Recommended: 1

Smaller gun = less polygons to render. Plus the big gun blocks a ton of screen.

Importance: 0 – in fact it should be -5, as having the big gun is a disadvantage both FPS and gameplay-wise.

cg_drawHands
Accepted values: 0/1
Default: 1
Recommended: 1, unless your FPS is really bad

This controls whether the gun is drawn or not. Obviously no gun means a lot less polygons being rendered, meaning more FPS! However, many players find it difficult to play without the gun being drawn. If you’re one of those players, there’s no point making the game less laggy if you can’t play when you’re all through!

Important: 4 – if you play better with the gun drawn, leave this at 1. Otherwise you can gain a bit of FPS by disabling it.

cg_sfxSurfaceImpacts
Accepted values: 0/1
Default: 1
Recommended: 0

Draws smoke on bullet impacts. This also controls the rendering of sparks when hitting a helmet, as well as the majority of the blood spray from a bullet impact on exposed flesh. If you rely on these effects to know when you hit someone, I recommend leaving this value at 1. If, however, you rely on another method of feedback, you should disable this cvar as it it quite a graphically-intensive process to render smoke.

Importance: 3 – but it depends if you even notice the blood spray and sparks when you hit another player.

cg_sfxParticles
Accepted values: 0/1
Default: 1
Recommended: 0

Draws sparks in addition to smoke on bullet impacts. Again, useless.

Importance: 0

cg_sfxShowDamage
Accepted values: 0/1
Default: 1
Recommended: 0

When players get shot, their skin changes to reflect the damage they received. No point loading even more textures! I personally never pay attention to the damage skins (as they’re called), as it takes too long to look at someone and decide how many times I need to shoot them. Just shoot until it’s dead.

Importance: 0

cg_visiblebleeding
Accepted values: 0/1
Default: 1
Recommended: 0

Even more useless than the above. Makes people visibly bleed when they’re shot. This has even less use than damage skins, if possible. This does not affect blood trails. Blood is one of the biggest hits to FPS, and it’s even worse in a big firefight.

Importance: 0

s_loadas8bit
Accepted values: 0/1
Default: 0
Recommended: 1

If you have onboard sound, 8 bit sound files can give a bit of FPS boost as the CPU has an easier time rendering lower bitrate files. It might sound noticeably worse, but sound in UrT isn’t very good to begin with.

Importance: 2 – only applies with onboard sound, and even then some might rather the default 16 bit sound files.

s_khz
Accepted values: 11/22
Default: 22
Recommended: 11

Lower quality sound as less of the spectrum is processed. Again, only applies for onboard sound, as a sound card is more than capable of running with all of Urban Terror’s sound quality options maxed.

Importance: 2

Finally:
If you change a /r_ setting and it says the setting will not be applied until you restart, do /vid_restart. You can enter a bunch of commands and then do one vid_restart to save time.
If you change a /s_ setting and it says the same thing, do /snd_restart.
It is, however, much easier to edit your configuration file directly. Go to your Urban Terror directory. Go to q3ut4 folder. Copy and paste “q3config.” Rename it to autoexec (autoexec.cfg if extensions are visible). Open it with Wordpad and search for the variables you want to edit. Save when you’re done. Next time you load Urban Terror, the settings will automatically be applied!

Conclusion

Another long article! I hope this will help you tweak your Urban Terror for maximum efficiency. UrT scales extremely well with CPU speed according to my results. I expect if I could overclock further, I’d see even better performance. Unfortunately Athlon XPs don’t overclock very well; once you have to start adding vCORE, they’re running out of steam, and I had to increase core voltage by 0.1 volts. And I don’t really have a good way to cool the CPU either, though I accidentally did all the stock and underclocked runs with the fan unplugged, and never had stability issues. Anyway, it becomes less and less of an issue as Urban Terror becomes older and older. Systems that can run the game smoothly with maximum detail can be had for less than $700 USD. I don’t want to offer upgrade advice, as this article is already way too long, but you can find out which part is slowing your frame rates down with a simple test. Record a demo on a decently crowded server (12-18 people). Run it with /timedemo 1. On the first run set your graphics to low quality settings (low resolution, low detail, etc.). On the second run, set everything as high as you can. If the frame rate does not drop much on the second run, your CPU is the bottleneck. But as I demonstrated in this guy, you can gain as much as 25 FPS over a “low quality” configuration by going beyond the graphics menu.

Here is the completed configuration file.

http://www.getlegitanddip.com/dailynade/lowgfx.cfg

Instructions are inside; open with Notepad or a similar text editor.

Here is a graphics card hierarchy which shows which cards are roughly equal in performance to each other:

http://www.tomshardware.com/reviews/best-graphics-card,2362-6.html

Newer isn’t always faster. The 9600XT is near the bottom middle, though it IS 6 years old!

You will get familiar with Grenades as long as you use them. Especially with timing (the grenade should explode when it touches the ground) and with aiming. They are very powerfull and you should consider them when choosing your equipment.

Techniques shown in this video:

• Short throw
• Long throw
• Fake shot
• Rebound throw
• Pressure with Grenades
• Hit and Run

There are many other techniques and we will cover them up in later posts. For prenades you can check tarquin’s post.
If you have more techniques tell us in the comments!

Pros:

• Automatic shoot from near to far distances (via zoom)
• High precision
• Zoom penalty movement lower than the Sr-8

Cons:

• High spread even after a few rounds shot
• Occasional unhits (sometimes bursts to the chest are not recognized as hits, and this happens more often tha with autos)
• Lower Fire Rate than M4 or LR300

Be careful though. Some maps are not meant to be played with a G36. Maps for rushers like Turnpike or Dressing Room should be played with pure automatics like M4 or Lr300. Big maps like Riyadh or Laneway are the ideal places for Sr-8 and PSG-1. However in the majority of the other maps this weapon might be a good choice.

I personally get better results on Casa, but also in Algeris and Uptown, where there are both close up combat and wide areas and corridors.

How to use the G36?

Let’s start with the choice of the equipment. Since it is an automatic, even if it’s not that fast, you souldn’t choose a secondary weapon (you can always pick up one from a dead opponent or from a dead teamate).
De or Beretta? DE for shure because it will help you in point-blank fights since you don’t have a secondary weapon.
Kevlar AND Helmet? I would say yes, since the G36 is not a weapon to rush with. You have one slot left to choose between Nades, Silencer or Medikit. This depends a lot on your personal taste and also on the situation (maybe in a CW you are forced to choose the Medikit). I personally go with the Nades.

Here we go.

As said before, you don’t rush with G36. The best technique is to move quickly by staying in areas of the map relatively clear, using every cover possible (crates, walls), shooting the enemy from far away.
Avoid long bursts. Especially while zooming bursts should be between 3 and 5 rounds maximum. If your opponent hasn’t seen you yet you can fire single shots and finish him with a final burst. This can be a very good technique.
If your opponent is very close though just shoot longer bursts, without exagerating. If you are caught by an opponent with your zoom on, you will unzoom by instinct but often it is not the ideal choice. By practicing you will learn to not unzoom and just shooting while moving backwards, gaining time and maintaining the enemy always in your field of view.

When should I zoom?

I would say that you should start zooming when targets are at least 50 feets away from you (15 meters). To give you an idea, is the distance between the spawn and the Laundromat roof in Uptown.

How do I use the zoom in close combat?

As usual, start shooting while doing short strafes from left to right. If your opponent is far away and has an auto, stop to avoid the penalty movement and take advantage of your superior precision. If you are facing a sniper never stop before unzooming him, stop to finish him only after the first hit.

Overall

Overall the G36 is a weapon for those who think before shooting and not vice-versa.
Also remember that the silencer can lower the spread, suppresses the fire and the noise and makes you less recognizable. If this is your way of playing, this is the ideal weapon. Instead if your primary objective is to get first to the enemy respawn, leave this weapon where it is.

1. Change your crosshair settings

Your crosshair is very important. Many players will tell you to choose the dot and to choose it as small as possible. Unfortunatly the dot can’t give you feedback about the accuracy of the weapon you are carrying, especially when you are shooting. Choose instead a crosshair that resizes its arms depending on the current accuracy. Refer to Don’s post about hud settings to choose the correct crosshair.

2. Shoot in small bursts

If you use a crosshair that gives you feedback about the current accuracy you will notice that almost every weapon looses accuracy even with a very small burst. The longer the burst the less accurate it will be. Also you have to wait a bit after shooting to let your aim recover as you will notice by your crosshair.

3. Try Semi-Automatic once in a while

Another training method is to play once in a while with semi-automatic. This means you will shoot just one bullet every time you click the fire button. This will make your shoots more accurate but also will force you to adjust the aim more often, just like when you shoot with the DE or the Beretta. When you will get back to full Automatic you will naturally make shorter bursts and you will adjust aim more often and fundamentally hit more bad guys.

4. Adjust your aim settings

We didn’t covered them up yet but there are a lot of aim settings that you can set via console and configurations files. If you aren’t familiar with them just consider sensitivity for now. Try lower the sensitivity as far as you can.
To see how high is your current sensitivity just type \sensitivity in the console. It will give you back the current value. I used to play with a drammatically high value and i lowered it a lot. I lowered it about 7 or 8 points less than what I had previously and helped me a lot.
By doing that you will make more wide movements with your mouse to let’s say turn corners and walljumping but you will have more control on both moving and still targets. However a post about aim settings is coming, so don’t worry.

5. Use the Remington Sr-8

I can’t tell you how much the Sr-8 helped me to increase my accuracy. Not with the Sr-8 itself but with all the other weapons. Why?
Well if you are a beginner with the Sr-8 you will find yourself hitting rarely and being killed a lot. Fail will help you. One of the fastest way to take down a sniper is to rush on him as Tarquin pointed out in his post. If you see somebody rushing on you you will likely pull out your secondary weapon or your sidearm. As we pointed out secondaries are not that accurate and sidearms are quite hard to use. Using the Sr-8 will force you to use both secondaries and sidearms a lot and since they are not so accurate you will adjust your aim more often to take down some bad guys. Probably this will get you a bad score but don’t worry. When you will get back to autos you will naturally have a better aim and also you will learn to use perhaps one of the most powerful weapons in Urban Terror wich is the Sr-8.

6. Aim at corners and hiding spots

When you walk don’t point your weapon at the floor. Not even right in front of you. You should always point your gun at where you think that enemies will come out: corners, hiding spots and so on. This is very important since you will spend less time adjusting your aim to shoot at enemies. This ability will come along as you get familiar with the maps and as you play.

7. Think about what you are doing

Be councious of what you are doing. When you face an enemy not just shoot but mentally stop for a second and think.
Counciously think: «Ok I’m facing an enemy, I must look for an headshot/I must shoot at his torso». Aim for the torso or head (better). Also consider your opponent’s equipment. If you see that he has helmet and no kevlar just aim for the torso instead of trying the headshot. If you are getting too much legs shots that means that you are aiming too low. Being aware of what you are doing will make you focused. And with better focus comes better aim.

8. Try the Counter-Strike Method

As explained in this post, the Counter-Strike method will help increase your accuracy and creativity.

9. Watch your movements

To avoid bullets often players tend to jump sideways. This might be helpful but especially when you are out of stamina or you have your legs bleeding this might be very hard. Try instead to move sideways randomly. Also depending on your weapon consider moving towards your opponent to have better shots (for example you have to be at point-blank distance to deal high damage with the SPAS).

10. Training

Aim is one of those things that will come along with time. If you are very talented (or you have a lot of time to waste play) you might get this skill very quickly. In other cases it might take time, but the more you play the more you will increase your accuracy and skills.

Have some more tips? Tell us in your comments! These comments might go in a future post about some more tips about aim and accuracy!

You’ll want to be able to play on your newly created Urban Terror server once it’s done, so you’ll need to create another install of it. Download the .zip file again, unzip it and rename the Urban Terror folder to something like “UrbanTerrorServer”. Put it where you want, preferrably in your “Applications” folder.

Step 2: Get familiar with the terminal

In fact the built-in Terminal of Mac OS X isn’t that different from UrT’s console. You enter stuff, it responds. It’s that simple.

Step 3: Edit the server’s settings

While you might be used to finding most of your Urban Terror stuff in your ∼/Library/Application Support/Quake 3 directory, all the server’s files are stored in your actual UrT installation directory. Access both

and

and edit those two files in the way you like, for this please refer to the Urban Terror Manual.

Step 4: Add custom .pk3s (optional)

In case you want to use custom maps, funstuff, skins, or in fact anything packed into a pk3 on your server, place it in the q3ut4 directory mentioned in the post above. Keep in mind that the autodl url has to be set correctly for people to be able to download all that.

Step 5: Set up your router

I’m assuming you’ll use the standard port, which is 27960 for Urban Terror. Open up that port in your firewall and forward it to your computer using the UDP protocoll. As the interface is different for each router, I can’t tell you how to do this step by step. This site may be helpful though.

Step 6: Locate the iourbanterror.ub

What actually runs the server is not your ioUrbanTerror.app, but a little unix file called ioUrbanTerror.ub. You find it by navigating to your server install, right-clicking ioUrbanTerror.app and then using the “Show package contents” item in the contextual menu. A new finder window should pop up. Navigate to

and leave the window open.

Step 7: Set up the terminal

Open it up and enter the following:

[path to your install]/ioUrbanTerror.app/Contents/MacOS/ioUrbanTerror.ub +set dedicated 2 +exec server.cfg

You can also just drag the .ub file into the terminal window and then add +set dedicated 2 +exec server.cfg.

Step 8: Hit enter!

The Urban Terror Server icon will bounce in the dock and then seem to freeze while the Mac OS terminal is spitting out all sorts of jibberish. This is normal, that means the server is running. DO NOT FORCE QUIT THE URBAN TERROR SERVER, EVERYTHING IS OK!

Step 9: Locate your server in the server list

No need to explain this step any further.

Step 10: PWN people!

Enjoy your zero ping and admin power and start owning! Wear a helmet. HF GL!