-
Notifications
You must be signed in to change notification settings - Fork 0
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
AI is broken/passive #10
Comments
Hi, this is very strange and I do not think I have encountered this issue. Chapter 2 enemies do attack you regardless of your position, if I'm not mistaken. Can you give more details? Your exact command and the chapters where you saw this behaviour? |
The issue occurred both when running the randomiser python file without settings and with. The time I tried with the settings I used -ab -ads -dbsr -epa -erps -g "Conquest" I'm running the randomiser on a rom of the special edition. The bug occurs in all chapters. Enemies will not be aggressive but will attack anyone in range. For example, the enemies in Chapter 5 attacked the Ryoma replacement, killing themselves on his rigged RNG, while the mages that spawned in the corners of the map did not move after appearing |
Can you provide a link to your |
https://drive.google.com/file/d/1vJsI0ApwW2riJ3ZOzDtnLmOvnXyPrbub/view?usp=sharing This is the most recent attempt I had at making it work. The AI was still broken. It's a slightly edited version of your upgraded patch, where I removed the added turn limits and reverted the stats of most of the weapons. However, the bug still occurred with a vanilla special edition rom. |
I got the randomiser working the other day, but noticed that the enemy AI was broken. Normally aggressive enemies will not move unless I enter their range, which really harms the experience on many maps. I tried the older randomiser, which did not have this issue, but I prefer the balancing of this one, and was wondering if you'd have any ideas about what causes this.
I had a look with Paragon at the AI for Chapter 2 at least, but they appear to use the same AI settings, despite the different behaviour.
The text was updated successfully, but these errors were encountered: