forked from dkfans/keeperfx-stable
-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Computer Player casting Call to Arms broken #53
Labels
Comments
Loobinex
added a commit
that referenced
this issue
Nov 8, 2019
Partial fix to #53 The timeout to CTA now works. A problem remains that many creatures are picked up while affected by CTA/
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue already exist on the official branch: dkfans/keeperfx#483
A computer player has several ways to attack the player, one of them is the 'Quick Attack', where the Call to Arms spell is used to attack the player. At some point the CP using CtA broke - it is working in old versions of KeeperFX and the original game - and now cannot be used to launch an effective attack or defense, and sometimes it even harms the computer.
What should happen on a quick attack is this:
However, only the first two steps work, the other 3 are problematic. It does not seem to gather enough units, units don't make it to the room to attack, and the CTA flag keeps on for far too long. This is seriously hampering the CP's effectiveness. My guess is the problem on (4) is that whenever a unit is hungry the CP picks it up, releasing it from CTA, and it's a long walk so most units go hungry. No idea why (3) and (5) go wrong.
The CP also cast CTA defensively when it is attacked, that flag also stays on for far too long after the battle is finished.
On this map the issue became really apparent, and I reworked it into a good test map: LevelCTAtest.zip
To reproduce the issue:
The map contains this script command:
SET_COMPUTER_CHECKS(PLAYER3,"CHECK FOR QUICK ATTACK",1500,45,3000,8,20)
Which is explained by the Duke as:
I changed the 30000 to 20, so that the first attack comes sooner for testing reasons.
The text was updated successfully, but these errors were encountered: