Supamiu / sorian-ai-mod

Automatically exported from code.google.com/p/sorian-ai-mod
0 stars 0 forks source link

Decision to launch nukes, and radar blindness #28

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Simply playing a game against Sorian AI Adaptives
2.
3.

What is the expected output? What do you see instead?
Replaying one of my playthroughs I noticed that after wrecking expansion bases, 
the S-AI was left in negative 3000 or so power income, so it's radar went 
completely down. However, it was still able to perfectly hit a cloacked (!) 
Monkeylord, 100% accurate, with a strategic bomber. Playthrough was viewed from 
AI's perspective and there was most definitely NOT any sort of marker where ML 
was supposed to be. Unless the Sorian somehow figured out it's location simply 
by having the red laser beam in it's optical range. Also goes for pinpoint 
accuracy in using TML's on cloacked units such as Monkeylord and radar-spoofed 
units such as Goliath in BlackOps Unleashed Unit pack mod. 

Another issue is that AI decides not to launch nukes in expansion bases if they 
have a defense built - even if that defense was built 3 seconds ago and it's 
impossible to already have as missile in it. As soon as the defense was built, 
the base is considered nuke-proof. Late game nuke volleys are always targeted 
at main base at which point I have enough anti-nukes to handle Yolona. 

What version of the product are you using? On what operating system?
These are the issues I noticed in an earlier version of Sorian AI (1.6-somethin 
I think) however I noticed no mention of that in change logs I've read 
completely. If the issues have been resolved in meantime, I apologise. If not, 
it's not urgent anyway. 

Please provide any additional information below (bug log, other installed mods, 
etc).
Issues appear in both un-modded game at version 5899, and with Blackops Unit 
Pack. AI handles new experimental units mighty fine though. Fine work :)

Original issue reported on code.google.com by eudaimon...@gmail.com on 22 Jan 2013 at 10:37