AI can't plays manland abilities correctly
- Dominant language
- Java
- Stars
- 2.4k
- Forks
- 940
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 160
Description
[From reddit by ChaoMing](https://www.reddit.com/r/XMage/comments/axcj8z/bugminor_annoyance_ai_and_manlands/):
> Nothing too major, but the AI loves to hang when it has a Manland on the field such as [[Creeping Tar Pit]] or [[Shambling Vent]] because it takes its ability into account at every step when calculating the best approach it should take. This leads to unnecessarily long wait times for those that use the AI as a goldfish and they happen to have manlands.
>
> Other issues include:
>
> Repeated usage of the manland ability even if the land is already a creature
>
> Tapping itself to use its own ability
>
> Viable solutions include hard-limiting the AI to only consider using the ability once per turn (reset at every end step or uptap step) and preventing the AI from tapping the manland to pay for its ability cost.
>
Contributor guide
No contributing guide indexed for this repository
Research direction
The report concerns AI evaluation of manland activations, including repeated activation, self-tapping for the cost, and long decision waits. No files or tests are named, so start by locating the AI decision path for manlands and its turn or step reset handling. Done means avoiding repeated activations, preventing self-payment, and eliminating the unnecessary delays.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ai, game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100