View Issue Details

IDProjectCategoryLast Update
0000723AI War 1 / ClassicBug - OtherDec 20, 2010 9:08 pm
Reporterthemachineissentient Assigned Tokeith.lamothe  
Status minor fix for laterResolutionopen 
Product Version3.719 
Summary0000723: Youngling nanoswarm enters regeneration chamber in regular mode, leaves in frd mode
DescriptionI have an offensive regeneration chamber, the ship becomes pink after it exits, and immediately suicides
TagsNo tags attached.
Internal Weight

Activities

Draco18s

Oct 19, 2010 11:32 pm

developer   ~0001473

All younglings exhibit this behavior (exiting in FRD).

keith.lamothe

Oct 20, 2010 3:28 pm

administrator   ~0001565

Chris, at one point I was asked to make this auto-frd-out-of-regen thing the case. Is it supposed to just go away entirely, or only not apply to nanoswarms?

zebramatt

Oct 20, 2010 3:32 pm

reporter   ~0001566

Last edited: Oct 20, 2010 3:32 pm

Now that there is an option to have a rally point out of regeneration chambers, FRD makes even less sense.

Although there's probably still an argument for having them not FRD when a rally point is posted; but continue to FRD without a rally.

Or maybe a new CTRL menu item would be good.

Or both? :p

Chris_McElligottPark

Oct 20, 2010 3:32 pm

administrator   ~0001568

They should be whatever they were when they went in.

keith.lamothe

Oct 20, 2010 3:56 pm

administrator   ~0001578

Well, yes, but any youngling that automatically self-orders itself to go to the regen chamber necessarily clears its frd flag in the process, so that basically means removing the auto-frd behavior, which I've done.

Draco18s

Oct 20, 2010 3:57 pm

developer   ~0001579

Couldn't you do the same thing as the space dock? Setting a rally point with V held down should set them to be in FRD just like the space dock.
(Mmmm...mushroom grenades...)

Chris_McElligottPark

Oct 20, 2010 3:58 pm

administrator   ~0001580

Either way.

Chris_McElligottPark

Oct 20, 2010 3:58 pm

administrator   ~0001581

But, the auto-FRD is preferable to no-FRD.

keith.lamothe

Oct 20, 2010 4:01 pm

administrator   ~0001582

Ok, so I should turn that behavior back on, and this issue is a no-change-needed? :)

Chris_McElligottPark

Oct 20, 2010 4:03 pm

administrator   ~0001583

Apparently so, for now. Gather points are out of scope for 4.0. You could move it to Strongly Considered for post-4.0.

keith.lamothe

Oct 20, 2010 4:04 pm

administrator   ~0001584

Ok, pulling the change out, we'll revisit this.

themachineissentient

Oct 20, 2010 6:42 pm

reporter   ~0001629

I missed out on these discussions because I was at work. Anyway, by having children auto-frd from regeneration chambers, they basically stream out and suicide when you are doing offenses maneuvers. They need to be the same mode as when they entered. I bring a bunch of these onto a planet and slowly send a few at a time at the targets I want when I am fighting, but what is happening is they get low on HP, go into the regeneration chamber, and suddenly I have all of my ships running around kamikaze into the enemy without any of my control. I'm sitting there clicking as fast as I can to catch them all, but no, off they go speeding into self-destruction.

A smart player will not just throw 200 of these nano guys at the same targets because you are just coating the same units multiple times. And suicide one at a time just doesn't make sense.

These ships offer the opportunity for some grand scenarios and skill wins with micro, as well as large exciting battles. If they are on frd mode but do not have a target, and they are low on health, go into the regeneration chamber and emerge on the same mode. If they are not on frd mode, and they do not have a target, go into the regeneration chamber and emerge on the same mode.

Chris_McElligottPark

Oct 20, 2010 6:55 pm

administrator   ~0001632

It's simply out of scope for 4.0, we just don't have any time. As Keith noted, they are not in FRD mode ever when they get to the chamber, because they had to leave FRD to go to it. These are more balanced for defense right now, and unfortunately that's how it's going to have to be until after 4.0.

Issue History

Date Modified Username Field Change
Oct 19, 2010 8:22 pm themachineissentient New Issue
Oct 19, 2010 11:32 pm Draco18s Note Added: 0001473
Oct 20, 2010 3:28 pm keith.lamothe Note Added: 0001565
Oct 20, 2010 3:28 pm keith.lamothe Assigned To => keith.lamothe
Oct 20, 2010 3:28 pm keith.lamothe Status new => assigned
Oct 20, 2010 3:32 pm zebramatt Note Added: 0001566
Oct 20, 2010 3:32 pm Chris_McElligottPark Note Added: 0001568
Oct 20, 2010 3:32 pm zebramatt Note Edited: 0001566
Oct 20, 2010 3:56 pm keith.lamothe Note Added: 0001578
Oct 20, 2010 3:57 pm Draco18s Note Added: 0001579
Oct 20, 2010 3:58 pm Chris_McElligottPark Note Added: 0001580
Oct 20, 2010 3:58 pm Chris_McElligottPark Note Added: 0001581
Oct 20, 2010 4:01 pm keith.lamothe Note Added: 0001582
Oct 20, 2010 4:03 pm Chris_McElligottPark Note Added: 0001583
Oct 20, 2010 4:04 pm keith.lamothe Note Added: 0001584
Oct 20, 2010 4:04 pm keith.lamothe Status assigned => feature for later
Oct 20, 2010 6:42 pm themachineissentient Note Added: 0001629
Oct 20, 2010 6:55 pm Chris_McElligottPark Note Added: 0001632
Dec 20, 2010 9:08 pm Chris_McElligottPark Status feature for later => minor fix for later