AI Imps still retarded

aljfalderz

il y a 7 ans
Views 6 968
mis à jour il y a 7 ans
Not Fixable

Win 10 64bit

Ram - 16GB

CPU - Intel i7-4790K

GPU Nvidia GTX 1080-TI (MSI Gaming-X 11GB)

Patch 1.6.5

So heres a problem that still hasnt been fixed since the Beta release.

AI imps will still run all the way through your dungeon to mine a random wall block. I've reported this before and didn't really care that they did it but it's just getting silly now.

I've noticed that it's always happens when you use an aureate monolithe but usually its just that the AI wants to ruin the efficiency of your rooms (can't see any other reason why they mine out the corners of the rooms when there wasn't even gold there to begin with).

The AI are too easy to defeat when all their imps are just dying in your territory and it's really off-putting to play when your minions spend all their time killing them rather than working.

Here's the Output log and some images of the AI imps being stupid:

output_log.txt

Game Version:

Steam Public

Platform:

Windows

Comment évalueriez-vous le service client qui vous a répondu ?

Note de satisfaction par aljfalderz il y a 7 ans

Ajoutez un commentaire sur la qualité de l'assistance que vous avez reçue (optionnel):

Réponses 2

Plus ancien en premier
Plus récent en premier Plus ancien en premier

Biervampir [AUT]

il y a 7 ans

Thanks for the report.
AI Overhaul will happening in 2.0 (the next upcomming major Update)

Répondre Lien

Tim White

il y a 7 ans
Not Fixable

Hi aljfalderz,

Thanks for submitting a ticket, and apologies for the issue you've encountered. As Biervampir mentioned, all being well there will be some improvements to the game's AI in Patch 2.0, which we have tentatively announced for early-mid next year, though the date is subject to change.

I have made the developers aware of this issue, and they will consider it when working on the AI improvements.

For now I will close this issue as "not fixable", since we are unable to release improvements to the AI until Patch 2.0. If you do still encounter the issue with Patch 2.0, I would recommend submitting a new ticket.

Thank you once again,

Tim