I have a 20:1 kill:tk ratio, because I go out of my way to kill tkers, and I (used to) bomb a bit too recklessly. 100:1 was just an example. Most servers seem to be run by clans, so the admin will probably set the limit to just below their lowest clan member, which should be reasonable for most people.SiMSaM16 wrote:
I have a 40:1 kill:tk ratio
Search
Search results: 14 found, showing up to 50
True. There shouldn't be a TK for people who get rammed by jets. Shot or bombed is another story, but if you're a dipshit walking out in front of a jet on a runway, you deserve to die. As to the bumper buggy, vehicles should be unable to TK through raming unless they are moving. If they are moving forward, only the front of the vehicle should be able to TK, if backward, only the back should be able to TK.arson wrote:
A good number of my tk's come from being forced by smaktards who want to hump the wheeel of the jets, or who likes to play bumper buggy with the armor if im lucky enough to get there first. The bookkeeping of tks is flawed and that prob needs to be fixed.
I think BF2 should include a server option to block players from joining if they have such and such number of TKs, team damage, or team vehicle damage per kills or score. For example, the admin could set the server to block people who have more than 1 TK for every 100 kills. Anyone who has more than one TK per 100 kills wouldn't be allowed to enter the server. Making this option available should both significantly reduce team killing (at least intentional team-killing), and should make it possible for non-TKers to play on servers with other non-TKers. What do you think?
Oh, I get it. Thanks. Would +karma but I don't have enough posts yet.
Christmas and easter were both pagan holidays until Christianity hijacked them. I believe pagans still celebrate solctices and equinoxes, though. Either way, it doesn't make you a Christian, pagan, whatever sort of atheist. Unless you believe there is some special significance to easter and Christmas, you're just taking a vacation and giving/receiving gifts.Jinto-sk wrote:
Aparently I'm a christian Atheist.
this is the official name for my beliefs
Before you all start flaming me or -1 me let me explain.
I do not believe in god and religion etc. but I follow the beliefs of christianity - well no not the beliefs, but I celebrate christmas, I sure as hell have a long easter weekend off work. Because I live in a society ruled by christianity and it's holidays and I join in the celebrations of these national holidays etc I am a
Christian Atheist
Atheist here, and no, I don't want to be a Christian. If I wanted to be a Christian, I would probably be one.
Under miscellaneous stats, there's a thing that says "Cost ($50 base)" and the number it gives me is 19.8283 cph (which it says is cents per hour). What is that number? Is that the cost of the bandwidth on servers I've played on?
I don't see why there couldn't be jets on Iron Gator or Night Flight. What's the point of capturing an airport if you aren't going to use it?gimp-pf wrote:
and where the fuck would the planes even take off from. i can guarentee there are no air fields in the city.jeez people
M16 if I'm doing long range stuff, AK if I'm doing close quarters stuff. The M16 is practically a sniper rifle, the AK is just devastating in close combat.
Using How To Make War 4th edition, I've determined the following:
*The US navy will flat-out own the current combined European navy.
*The combined land forces of all European nations would be just a little bit weaker than our army. Factor in the defender advantage and we've got 3:1 odds against them.
Given the naval superiority, Europe would need to devote a good portion of its GDP to building up navies before they could invade the US. This would take a few years, probably. During that time, the US could be building up its own navy and assembling land forces and militia fallbacks.
So pretty much, no. Even if all of Europe got involved, they wouldn't be able to take on the US at this time, and the time it would take for them to get here would practically preclude any chance of success. The only hope of European victory would be if the US got involved in a civil war beforehand and all of the ships were denied safe harbor.
*The US navy will flat-out own the current combined European navy.
*The combined land forces of all European nations would be just a little bit weaker than our army. Factor in the defender advantage and we've got 3:1 odds against them.
Given the naval superiority, Europe would need to devote a good portion of its GDP to building up navies before they could invade the US. This would take a few years, probably. During that time, the US could be building up its own navy and assembling land forces and militia fallbacks.
So pretty much, no. Even if all of Europe got involved, they wouldn't be able to take on the US at this time, and the time it would take for them to get here would practically preclude any chance of success. The only hope of European victory would be if the US got involved in a civil war beforehand and all of the ships were denied safe harbor.
I was recently playing a 64 person Dragon Valley and was teamkilled and I "teamkilled" in some very interesting ways. The first, biggest one was when I had gotten into a jet, and guy drove a jeep into me while I was in the hangar. The jeep blew up, he died, I died, and I got the teamkill. The same guy jumped in front of my plane while on the runway in another incident. Obviously, I got the teamkill. Once he realized the server didn't kick for teamkills, he got even more creative. Without an end in sight, he pulled that wonderful classic of M95ing me out of the cockpit, and stealing the jet. Even better, he outright shot me in the hangar while we were waiting for the plane. So, I think there should be a change of rules as an improvement in the next patch, because as you can understand, I'm FUCKING PISSED!
Firstly, there should be no road kill teamkills for jets who crash into non-vehicles. Anyone stupid enough to walk in front of a jet on the runway deserves to die. There should be no opportunity to punish, and no loss of points. Second, teamkilling a jet or its pilot in a repair zone or which was in a repair zone within the last two seconds, which isn't traveling at or above 300 (unamed increments, which will be referred to as UIs from now on) or teamkilling a helicopter in a repair zone with anything other than a collision from a jet moving faster than 400 UIs or AA missiles (as both of these happen accidentally) should cause -12 teamwork points, and the option for two punishes. Third, any collision between a ground vehicle and a jet in a repair zone or which was in a repair zone in the last two seconds should automatically give the teamkill to the ground vehicle (it's possible a ground vehicle was legitimately fighting to defend the airfield, and a jet was pressed for time to get airborne, and they collided accidently, but it will shore up that exploit and the ground vehicle should be careful when wandering onto a runway). They don't belong on the airfield. Teamkilling anyone in a repair zone should count for -8 teamwork poitns IF the teamkilled party decides to punish.
So to sum it up:
1. Run in front of a jet and you die. There is no teamkill.
2. Teamkill a jet or helicopter pilot at base or that just left base and you'll get -12 teamwork and possibly get punished twice.
3. Drive a vehicle into a jet in a hangar and you'll get the teamkill.
Firstly, there should be no road kill teamkills for jets who crash into non-vehicles. Anyone stupid enough to walk in front of a jet on the runway deserves to die. There should be no opportunity to punish, and no loss of points. Second, teamkilling a jet or its pilot in a repair zone or which was in a repair zone within the last two seconds, which isn't traveling at or above 300 (unamed increments, which will be referred to as UIs from now on) or teamkilling a helicopter in a repair zone with anything other than a collision from a jet moving faster than 400 UIs or AA missiles (as both of these happen accidentally) should cause -12 teamwork points, and the option for two punishes. Third, any collision between a ground vehicle and a jet in a repair zone or which was in a repair zone in the last two seconds should automatically give the teamkill to the ground vehicle (it's possible a ground vehicle was legitimately fighting to defend the airfield, and a jet was pressed for time to get airborne, and they collided accidently, but it will shore up that exploit and the ground vehicle should be careful when wandering onto a runway). They don't belong on the airfield. Teamkilling anyone in a repair zone should count for -8 teamwork poitns IF the teamkilled party decides to punish.
So to sum it up:
1. Run in front of a jet and you die. There is no teamkill.
2. Teamkill a jet or helicopter pilot at base or that just left base and you'll get -12 teamwork and possibly get punished twice.
3. Drive a vehicle into a jet in a hangar and you'll get the teamkill.
The Kubra tunnel is pretty easy. I can do it without damage with the fighter pretty much every time. With the bomber I'm more like 50-50 to even get through it. It's not a regular practice of mine, but on occasion, I've used that tunnel to evade the other jets on the map. I've had a lot of n00bs try to follow me, and I only wish I could have gotten the kills for those.
As for getting shot down in like 5 minutes, there are two important things you need to do if you don't want that to happen. The first is that enemy jets should always be your #1 priority. If you don't shoot them down first, then they'll take your kindness and kill you anyway. As shooting jets has become easier, it's now much more important to take them out than it is to try and not aggravate them so that you can both just bomb the shit out of your teams (which was my previous strategy, to only attack when attacked, because I could survive an attack pretty much every time). Second, is to take out AA, as your second priority. Those AA turrets are targets begging to be hit. If you know where they are on the map, then you should know when someone is in one and be able to take it out (you should always be on bombing mode so you don't alert other jets when you spot them, you want to sneak up on them. This also lets you see the AA even if it's outside of visual range.) AA vehicles are a bit more tricky. Against them, I've found it best to jink as you're coming in and bomb them. If you do both of those, then you can own everything else on the map.
As for getting shot down in like 5 minutes, there are two important things you need to do if you don't want that to happen. The first is that enemy jets should always be your #1 priority. If you don't shoot them down first, then they'll take your kindness and kill you anyway. As shooting jets has become easier, it's now much more important to take them out than it is to try and not aggravate them so that you can both just bomb the shit out of your teams (which was my previous strategy, to only attack when attacked, because I could survive an attack pretty much every time). Second, is to take out AA, as your second priority. Those AA turrets are targets begging to be hit. If you know where they are on the map, then you should know when someone is in one and be able to take it out (you should always be on bombing mode so you don't alert other jets when you spot them, you want to sneak up on them. This also lets you see the AA even if it's outside of visual range.) AA vehicles are a bit more tricky. Against them, I've found it best to jink as you're coming in and bomb them. If you do both of those, then you can own everything else on the map.
I agree with this wholeheartedly. I would also prefer that the AT mines show up at a greater distance when in a vehicle, because only getting 10 meters notice of a mine when traveling in something as fast as an FAV doesn't leave much time to respond. As someone else mentioned, claymores really need to say what direction they're pointed, as well as saying they're a claymore.
Gah! This download is taking like 2 hours! I have a 100+k connection, but BF2 is giving me a 31KB/s connection on this download. It's worse than... oh god, I'm going to be sick... it's worse than a 56K!