|
|
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Skihids
Bullet Cluster
Legacy Rising
2634
   |
Posted - 2014.01.05 06:16:00 -
[1] - Quote
Use your brain, please.
One uplink next to the objective in an enclosed area and you can't drop a triage or ammo hive anywhere useful.
Use a flux grenade if you don't like the enemy equipment.
Fix lagging in the code, don't create artificial restrictions trying to avoid the buggy code. |
Skihids
Bullet Cluster
Legacy Rising
2637
|
Posted - 2014.01.05 08:13:00 -
[2] - Quote
Ryder Azorria wrote:Skihids wrote:Use your brain, please.
One uplink next to the objective in an enclosed area and you can't drop a triage or ammo hive anywhere useful.
Use a flux grenade if you don't like the enemy equipment.
Fix lagging in the code, don't create artificial restrictions trying to avoid the buggy code. The lag is only partly due to less than optimized code, the server having to track so many different entities is always going to cause lag - the only way to properly fix it is to reduce the amount of equipment on the field.
And you know this because of your intimate knowledge of the code? |
Skihids
Bullet Cluster
Legacy Rising
2637
|
Posted - 2014.01.05 08:37:00 -
[3] - Quote
Aero Yassavi wrote:Asha Starwind wrote:why doesn't anyone ever suggest something sensible like an expiration timer after ### the deploy-able expires. That combined with the idea that equipment uses some sort of signal transmission to draw CPU and PG from your suit, thus if you change suits the equipment you placed with the previous suit would be destroyed. If you die and respawn in the same suit, then your equipment stays. But if you die and switch suits, or go to a supply depot and switch suits, your equipment is destroyed. I know some people won't like this because they use speed fits to quickly get uplinks down and then switch to something more practical for combat, but in my opinion it would only add another layer of strategy to Dust with setting up who is going to use what equipment and what fit is best of carrying such equipment.
Then you too will find you don't like it when you have to hike in from your rear spawn because the two uplinks that people decided to fit due to the restrictions get destroyed or camped. I just read a post where the author was disgusted with the blueberries who in part "couldn't be bothered to toss out an uplink".
Watch what you wish for, because you just might get it. |
Skihids
Bullet Cluster
Legacy Rising
2637
|
Posted - 2014.01.05 08:43:00 -
[4] - Quote
Fizzer94 wrote:Skihids wrote:Ryder Azorria wrote:Skihids wrote:Use your brain, please.
One uplink next to the objective in an enclosed area and you can't drop a triage or ammo hive anywhere useful.
Use a flux grenade if you don't like the enemy equipment.
Fix lagging in the code, don't create artificial restrictions trying to avoid the buggy code. The lag is only partly due to less than optimized code, the server having to track so many different entities is always going to cause lag - the only way to properly fix it is to reduce the amount of equipment on the field. And you know this because of your intimate knowledge of the code? He knows it because its quite basic. A lot of entities can make a server laggy, regardless of the 'code'. CCP can't magically make the internet faster because they want to.
This sounds like "common knowledge" that may have no basis in fact. What does network latency have to do with a handful of fixed points? Equipment doesn't move once deployed. It can be fixed locally on your system if need be. It isn't a merc running around constantly altering his position and orientation. |
Skihids
Bullet Cluster
Legacy Rising
2637
|
Posted - 2014.01.05 08:46:00 -
[5] - Quote
Aero Yassavi wrote:Skihids wrote:Aero Yassavi wrote:Asha Starwind wrote:why doesn't anyone ever suggest something sensible like an expiration timer after ### the deploy-able expires. That combined with the idea that equipment uses some sort of signal transmission to draw CPU and PG from your suit, thus if you change suits the equipment you placed with the previous suit would be destroyed. If you die and respawn in the same suit, then your equipment stays. But if you die and switch suits, or go to a supply depot and switch suits, your equipment is destroyed. I know some people won't like this because they use speed fits to quickly get uplinks down and then switch to something more practical for combat, but in my opinion it would only add another layer of strategy to Dust with setting up who is going to use what equipment and what fit is best of carrying such equipment. Then you too will find you don't like it when you have to hike in from your rear spawn because the two uplinks that people decided to fit due to the restrictions get destroyed or camped. I just read a post where the author was disgusted with the blueberries who in part "couldn't be bothered to toss out an uplink". Watch what you wish for, because you just might get it. Not sure what you mean? Place uplinks better if they are getting destroyed or camped.
My point is that your suggestion would likely reduce deployed uplinks to one or two per side because nobody would dedicate many slots to it all game long. That much smaller number would be more easily destroyed or camped. |
|
|
| |
|