We were hacked. Several times over the past two weeks, in fact.
While all passwords are encrypted and salted, it's recommended that you change your password here when you can.
Ohhhhh, you are SO gunna be flamed now......
:ar15:
Yeah, I know but I think it'd be unfair if I didn't use them.
I was in the tank when I got killed by a Vod and plus, it killed some noob too and I got a TK Punish. This happened twice. This "vehicle drop" idea is dumb, but now that it exists, don't change it anymore.
This thread is retarded. Do you really think a programming team that can't fix the red tag bug is going to be able to impliment no drop zones without creating ~20 more bugs for the game?
I'm a lawyer, not a programmer, but if DICE/EA could devolop a game of these proportions, I would imagine that they have enough talented people capable of fixing one of the biggest issues with 1.3. So far, limiting the number of drops and drop areas seams like a good start, and must be addressed regardless of the fact how hard it is to write the code for it.
It's not a matter of it being possible for them to do it, it's a matter of it being practical.
I personally doing think "no drop zones" is the idea solution for a number of reasons:
Variation in Drop fixes more "abuse" than No Drop Zones.
Not only does it adress dropping on runways/rooftops (fixed and specific areas), but it limits the abusive behaviour overall. It simply wouldn't be reliable and thus wouldn't be popular. At the same time, it still allows for desperation/fluke success. Those big flukes can be highly entertaining.
Variation in Drop is simple, No Drop Zones is not.
Adding variation to a variable is reasonably simple. It should take no more than a couple lines of code. Creating a whole new No Drop Zone system would be a major development. You have to make a system for designating no drop areas, re-do every map to include them, and come up with the system for checking zones in real time. Likely a could hundred lines of code. This is a bad thing.
Not only do all those extra lines of code take longer to write (and thus become expensive), but it give a higher chance for bugs to creep in. With that many new lines, the chances for conflict also increases and new bugs can form.
So... logicly if you were in charge, which way would you go?
I'm a lawyer, not a programmer, but if DICE/EA could devolop a game of these proportions, I would imagine that they have enough talented people capable of fixing one of the biggest issues with 1.3. So far, limiting the number of drops and drop areas seams like a good start, and must be addressed regardless of the fact how hard it is to write the code for it.
The problem is no-drop zones the problem is that they are deadly accurate.
Just add a +/- 5 meter random variance to the drop in a random direction. If the commander's cartillery dropped 5 meters away in a random direction each time he can't use it like he does today.
You could, in addition, make it so you can't drop it on targets with Elevations > 0 (not on the ground layer). The top of a hill is ground and thus Elevation 0. The top of a building or the top of artillery is > 0 thus not allowed. The Essex is floating in water way above the ground thus > 0 and not allowed.
Harmor, I think the variation is enough to stand on it's own. Adding a restriction based on elevation is again adding something new to the system and for the same reasons I outlined above, we really don't want to be suggesting that.
I'm a lawyer, not a programmer, but if DICE/EA could devolop a game of these proportions, I would imagine that they have enough talented people capable of fixing one of the biggest issues with 1.3.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment