On 2012-11-24 12:10, Hide wrote:
Give us a Planet Defence Structure that only targets dropped Enemy infantry. It will be up to each faction what planets they want to put them on and how many... Or, how about a planet base that commands ai fighters or even just a fighter (per base) that orbits the planet and will seek out dropped inf, but stays with in orbit of planet. Kinda like a drone that auto patrols the skys...???

On 2012-11-24 11:54, Bladerunner2014 wrote:
I see my tranny rushing while playing kluth is causing conversation...allow me to clear up your concerns.....

I used 4 trannys and would fill them in home server and would literally drop inf over and over for hours, somedays 10 hours straight, and I can tell you it is not as easy as you folks believe.

I will say that doing it with a kluth tranny is easier because of the cloak, but I still wasted alot of trips getting killed.

A fact you maynot know: I used to have over 258,000k prestige, and overtime I am down to 203,000k prestige, alot of the loss is from tranny rushing because I sd everytime I drop to get next tranny faster.

The planet def is more than adequete because doing it as ugto without the cloak means alot of death while attempting.

I do NOT use gates....I use plat trails to travel around, which means I do alot of 90 sec jumps to get to the planet I am dropping on, sometimes 2 or 3 jumps to get there....that is alot of time just travelling and alot of patience. A lot of times I would drop 30 or 40 and then the enemy would just bomb and 10-15 mins of work down the drain and I would have to start all over again and try another planet.

Tranny rushes are not as easy as you think, and do cost you prestige....it is human tenacity and patience that make it an effective option, it is NOT a game weakness....

I challenge any of you to use up 4 spots in your sy and build a plat trail and try tranny rushing with 4 trannys for 10 hours straight....you will see how much work it is, and how much failure there is....I know some will reply and say they tranny rush already....but trust me, you don't....not the way I do.

Success in this game usually comes from how many players are on in your faction...the less players on in your faction at any given time means more failure.

If you want to talk about the lack of balance of the factions then have your clan switch factions for a week or two and learn about how the other 2 factions work now(which you can't learn in beta). This game constantly changes, you CANNOT speak about another factions powers and weaknesses if you don't try to play that faction for atleast a week.

When you win say little, and when you lose say less.





[ This Message was edited by: Bladerunner2014 on 2012-11-24 12:03 ]

On 2012-11-26 08:05, Bardiche wrote:
I think one of the more interesting ideas to "fix" the issue of K'Luth Transports being virtually impossible to stop from dropping on ships and planets was the idea of a "minimum vision zone". To avoid completely trivialising K'Luth Cloak, I would propose the following.

- Include a gadget named "Active Sensors", or replace the "Scanner" functionality with the proposed functionality below.

- "Active Sensors" have high energy consumption and vastly increase mass of the ship, being meant to be used while immobile rather than while moving. Jump Drive functionality remains. While "Active Sensors" are active, they will grant "true vision" in a 250gu area around the vessel. "True vision" referring to detecting absolutely everything regardless of its signature.

This would disallow K'Luth transports from reaching a target undetected and makes them as vulnerable as their human counter-parts, except it can be invisible at 251gu+ distance.

- A disadvantage of this approach is that it removes K'Luth first strike functionality, and fitted on small ships can make them illuminate K'Luth targets forever, making cloak unpossible to be deployed. The key factor is to balance the device such that small ships using it will be incredibly lacking in manoeuvrability and further have such high energy drain at 50% engine output that they cannot sustain it for very long.

This means energy output needs to be carefully measured for each level such that each ship that fits it bleeds energy if they use the sensors overlong. Additionally, restrict the device to dedicated scout vessels and command vessels, so players are still trading in a useful ship for functionality.

---

For the moment, though, I don't foresee immediate changes to the way cloaking works. A definite solution that makes everyone happy is probably impossible, though. As a playerbase, it's a good idea to consider what different aspects a solution has; what disadvantages does it bring and what does it break, and what can be done against it?

On 2012-11-26 08:05, Bardiche wrote:
I think one of the more interesting ideas to "fix" the issue of K'Luth Transports being virtually impossible to stop from dropping on ships and planets was the idea of a "minimum vision zone". To avoid completely trivialising K'Luth Cloak, I would propose the following.

- Include a gadget named "Active Sensors", or replace the "Scanner" functionality with the proposed functionality below.

- "Active Sensors" have high energy consumption and vastly increase mass of the ship, being meant to be used while immobile rather than while moving. Jump Drive functionality remains. While "Active Sensors" are active, they will grant "true vision" in a 250gu area around the vessel. "True vision" referring to detecting absolutely everything regardless of its signature.

This would disallow K'Luth transports from reaching a target undetected and makes them as vulnerable as their human counter-parts, except it can be invisible at 251gu+ distance.

- A disadvantage of this approach is that it removes K'Luth first strike functionality, and fitted on small ships can make them illuminate K'Luth targets forever, making cloak unpossible to be deployed. The key factor is to balance the device such that small ships using it will be incredibly lacking in manoeuvrability and further have such high energy drain at 50% engine output that they cannot sustain it for very long.

This means energy output needs to be carefully measured for each level such that each ship that fits it bleeds energy if they use the sensors overlong. Additionally, restrict the device to dedicated scout vessels and command vessels, so players are still trading in a useful ship for functionality.

---

For the moment, though, I don't foresee immediate changes to the way cloaking works. A definite solution that makes everyone happy is probably impossible, though. As a playerbase, it's a good idea to consider what different aspects a solution has; what disadvantages does it bring and what does it break, and what can be done against it?