View Issue Details

IDProjectCategoryLast Update
0009466AI War 1 / ClassicSuggestion - AI Behavior And TacticsOct 5, 2012 2:51 pm
ReporterFaulty Logic Assigned Tokeith.lamothe  
Status resolvedResolutionfixed 
Fixed in Version5.090 
Summary0009466: Let threat attack at random sometimes
DescriptionSo every undecided_time_increment or so, threat has a small chance of throwing fp calculations out the window and attacking anyway. This can cause major damage in some cases, adds to the unpredictability of the AI, and makes permanently paralyzing threat with 100% confidence impossible.

Threat should also immediately do something if an AIHW is attacked.
TagsNo tags attached.
Internal WeightNew

Relationships

related to 0007016 considering Reduce the firepower cutoff ratio that "stalking a wormhole" AI ships will wait for before entering 
related to 0009465 resolvedkeith.lamothe Give Freed AI Ships more possible actions 

Activities

TechSY730

Sep 3, 2012 9:36 pm

reporter   ~0028177

Last edited: Sep 3, 2012 9:37 pm

Of course the tricky thing will be to figure out what the interval should be and what the chance should be each interval, and whether to make one, both, or neither a constant, and if not a constant, what thing(s) would it vary with?

Faulty Logic

Sep 3, 2012 9:45 pm

reporter   ~0028178

I was thinking something like doing a check every 20 minutes and having the chance be around 10 percent. So the chance is there, while relying on this mechanic to get threat to attack would not work.

TechSY730

Sep 5, 2012 9:57 am

reporter   ~0028223

Last edited: Sep 5, 2012 9:58 am

@Faulty Logic
Those values seem a bit high, when you consider how long game are. It's hard to say by just "eyeballing" it though.

I'll have to break out some math to figure out what expected average durations between these "forced threat enters" and expected deviations from that average given a set of durations and chances.

Now where did I put that probability and statistics textbook?...

Faulty Logic

Sep 5, 2012 11:36 pm

reporter   ~0028245

My goal was a .5 chance of random threat attack every three hours or so. Those values produced a .61 chance/three hours. For about 50, then 1 10% check every 25 minutes is about right. This is pretty high, but threat does say "ships that will soon be attacking your planets."

Battlecrydnx

Sep 6, 2012 12:38 am

reporter   ~0028246

Last edited: Sep 6, 2012 12:39 am

Make it so it's a 3% chance every 10 minutes. Additive chance so 3% first 10 6% over 20m, ect ect. And -possibly- add it as a modifyable varible so we can make it so that the random wave chance is 1% every 2 minutes ect. Or add it as a minor faction(Or AI Plot) and make it so the higher value it has(IE. dyson sphere can be 1-10) the higher chance it has of randomly spawning a wave to wave you.

keith.lamothe

Oct 5, 2012 2:51 pm

administrator   ~0028599

For 5.090:

* Since "make the threatballs fish or cut bait" was 0000001 on the second round of the 6.0 poll:
** Threat ships behave as they used to for about 30 minutes after being freed, but after that they are switched to an alternate "Threat Fleet" behavior that is somewhat similar to the new Special Forces mechanic.
*** Note: this only happens on Difficulty 7+, as it's not the AI getting anything extra, it's just behaving more intelligently (in theory) with what it has.
** If an AI homeworld or core world is under attack, the threat fleet will rally to defend it.
** Otherwise, if it sees an accessible non-AI planet with a significant human presence that it thinks it can take out, it goes to attack that (it will still pool up at the entry wormhole in some cases, until enough of them are there to pass the threshold, so they don't march in to the grinder one-by-one).
** Otherwise, it picks a planet in AI territory to hang out at until either of the two above conditions are met.
** If a carrier is spontaneously formed from ships that have a significant threat-fleet population, the carrier (and anything it spawns) is also considered threat-fleet.

Not exactly what any one request was going for, iirc, but I think this will make that threat at least more interesting. Thanks for the feedback :)

Issue History

Date Modified Username Field Change
Sep 3, 2012 9:30 pm Faulty Logic New Issue
Sep 3, 2012 9:31 pm Faulty Logic Relationship added related to 0007016
Sep 3, 2012 9:36 pm TechSY730 Relationship added related to 0009465
Sep 3, 2012 9:36 pm TechSY730 Note Added: 0028177
Sep 3, 2012 9:37 pm TechSY730 Note Edited: 0028177
Sep 3, 2012 9:45 pm Faulty Logic Note Added: 0028178
Sep 5, 2012 9:57 am TechSY730 Note Added: 0028223
Sep 5, 2012 9:58 am TechSY730 Note Edited: 0028223
Sep 5, 2012 9:58 am TechSY730 Note Edited: 0028223
Sep 5, 2012 11:36 pm Faulty Logic Note Added: 0028245
Sep 6, 2012 12:38 am Battlecrydnx Note Added: 0028246
Sep 6, 2012 12:39 am Battlecrydnx Note Edited: 0028246
Oct 5, 2012 2:51 pm keith.lamothe Internal Weight => New
Oct 5, 2012 2:51 pm keith.lamothe Note Added: 0028599
Oct 5, 2012 2:51 pm keith.lamothe Status new => resolved
Oct 5, 2012 2:51 pm keith.lamothe Fixed in Version => 5.090
Oct 5, 2012 2:51 pm keith.lamothe Resolution open => fixed
Oct 5, 2012 2:51 pm keith.lamothe Assigned To => keith.lamothe