ommmmmmm / keeperfx

Automatically exported from code.google.com/p/keeperfx
0 stars 1 forks source link

Enemy keeper casts call to arms beyond LOS #235

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
(please describe a single problem, providing as much detail as possible)
1. In any map where there is a direct connection between your dungeon and an 
enemy keeper
2. They cast Call to Arms in the main body of your dungeon, even if they 
haven't explored that far yet

What version of the product are you using? On what operating system?
(you can see your KeeperFX version by viewing keeperfx.log in notepad)

Keeperfx 4.3.910 Windows 7

Please provide any additional information below.
(describe one bug per report, but with all you can gather about it)

Original issue reported on code.google.com by Olympus...@gmail.com on 29 Jan 2014 at 10:41

GoogleCodeExporter commented 9 years ago
This has happened from the beginning of Dungeon Keeper. I can only assume as 
the AI knows the map perfectly it doesn't need to explore. On the other end of 
the scale if you've ever sat and let the aggressive assistant play he'll dig to 
the enemy dungeon but be able to dig a perfect outline of the enemy dungeon.
As a computer player they automatically know everything on the map.

Original comment by shortaie...@gmail.com on 29 Jan 2014 at 11:53

GoogleCodeExporter commented 9 years ago
It's not that computer player 'knows' everything, he doesn't even have a 
concept of 'knowing'.

Computers execute algorithms. Real-time games need to have the algorithms 
straight and simple, so that the continuous gameplay is sustained.

Anyway, I agree that computer player should compute the place to cast CTA with 
checking whether the place is revealed. If there's no such check now, we'll try 
to add it.

Original comment by mefistotelis on 29 Jan 2014 at 1:04

GoogleCodeExporter commented 9 years ago

Original comment by eatpajdi...@gmail.com on 30 Apr 2015 at 5:36