View Issue Details

IDProjectCategoryLast Update
0003103AI War 1 / ClassicSuggestion - Balance TweaksOct 31, 2011 9:55 am
ReporterPrezombie Assigned To 
Status consideringResolutionopen 
Product Version5.007 
Summary0003103: A way to fix FF healstacking.
DescriptionYou can't heal an FF under fire, but you are able to heal an FF that has be set into low power, meaning if you have a pair, and alternately turn one off, you can have engineers repair the other. A simple fix to remove this exploit would be to make low powered FFs (maybe other units with similar function?) immune to repair and healing.
TagsNo tags attached.
Internal WeightFeature Suggestion

Activities

zoutzakje

Mar 25, 2011 7:31 am

reporter   ~0011446

This won't work. When you place multiple FF's over something, there is usually just one taking fire. The other one can be repaired, wheter you put it in low power mode or not. If enemy ships are firing too fast and all FF's get hit at about the same time, then I think people should still be able to put the FF they want repaired in low power mode to be able to repair it. Shutting one or more FF's down means the active one(s) will die a lot faster, so there already is a risk in doing that.

Red Spot

Mar 25, 2011 1:37 pm

reporter   ~0011454

I can repair them under heavy fire as well, low power mode just means I dont have to micro it in detail.
In some cases, imo, the lack of micro is more important than a really minor exploit, like here :)

Prezombie

Mar 26, 2011 6:48 am

reporter   ~0011481

Last edited: Mar 26, 2011 6:48 am

Hm, maybe they should be immune to repair, but quickly regenerate after a few minutes of not being hurt?

I understand the point of removing micro, but the synergy of two FF gens is far more powerful than just one, which really feels exploity. Having a M3 FF and a M1 FF together shouldn't result in a near-unbreachable barrier, especially in defender mode.

Red Spot

Mar 26, 2011 9:07 am

reporter   ~0011483

If 500 bombers attack you and you have 2-3 mk1 FFs, they all die and so does your CC.
The 'exploit' only gives a minor boost over not doing anything, when several shield cover each other.

An other, exactly the same thing, you can do is simply make sure they die 1 after each other and have a team of engies build new ones as older ones die. Should it than also disallow FFs being assisted by engies?

In other words, if you want this nerfed, you'll need to nerf quite a few other things as well. (engies supporting, different shieldsizes, mobility, relativly low cost, double+ cover, etc)

Sigma7

Oct 12, 2011 4:41 pm

reporter   ~0016482

5.015: "When a forcefield is damaged by enemy fire, all allied forcefields whose fields are in contact (or very close to it) with the damaged ff will take 1 point of damage from the energy conducted along the surface of the field."

Since there's already a fix for forcefield heal stacking, I think we can close the bug.

Draco18s

Oct 12, 2011 11:26 pm

developer   ~0016513

Bug can indeed be closed, however, you can still micro your FFs around by moving a damaged one away from the stack, healing it over there, and cycling it back in.

With three or more FFs, you can micro the same effect that we used to have without the excessive micro.

I feel dirty having said that. :X
(That is: I feel ashamed for having found a workaround to a [i]fixed exploit[/i].)

TechSY730

Oct 31, 2011 9:44 am

reporter   ~0017336

@Draco18s

I'm not really that concerned about that exploit. Forcefields have such a glacially slow speed that by the time you move the damaged one out of the way, repair it, and the back in, you will probably still be behind. Yea, if your good, you could buy yourself some extra time, but nothing like the possibly infinite time as before.

Draco18s

Oct 31, 2011 9:55 am

developer   ~0017339

Oh, it took about four FFs to really do it (two covering, two repairing), and no, while I couldn't have been able to buy an infinite amount of time, it was non-negligible. I actually had to cycle twice before the AI ships were all dead (that is, each force field spent some time away being repaired at least twice).

Issue History

Date Modified Username Field Change
Mar 25, 2011 5:46 am Prezombie New Issue
Mar 25, 2011 7:31 am zoutzakje Note Added: 0011446
Mar 25, 2011 1:37 pm Red Spot Note Added: 0011454
Mar 26, 2011 6:48 am Prezombie Note Added: 0011481
Mar 26, 2011 6:48 am Prezombie Note Edited: 0011481
Mar 26, 2011 9:07 am Red Spot Note Added: 0011483
Oct 12, 2011 4:41 pm Sigma7 Note Added: 0016482
Oct 12, 2011 11:26 pm Draco18s Note Added: 0016513
Oct 31, 2011 7:41 am tigersfan Internal Weight => Feature Suggestion
Oct 31, 2011 7:41 am tigersfan Status new => considering
Oct 31, 2011 9:44 am TechSY730 Note Added: 0017336
Oct 31, 2011 9:55 am Draco18s Note Added: 0017339