Usually minas morgul works perfectly fine both assault and defense. This time around i fought gondor brutal ai defender. they had erebor as allied reinforcements though. In this case gondor controls the fortress but also got assigned to share a base with erebor. So now he rushes out one builder after another to build a base outside where his defeated erebor ally once stood instead of comfortably sitting behind their walls.
Bug minas morgul assault wotr 4.1
Started by Mestane, Mar 14 2020 05:27 PM
2 replies to this topic
#2
MattTheLegoman
-
- T3A Staff
-
- 3,669 posts
LEGO Knight of Minas Ithil
- Location:Tomorrow, when the War began
- Projects:Mapping this Middle-earth
- Mapper
- Division:BFME
- Job:T3A Staff
Posted 06 April 2020 - 04:50 PM
I do not understand what you are saying. Minas Morgul has not been touched yet by AotR.
Edited by MattTheLegoman, 06 April 2020 - 04:50 PM.
Remember that all worlds draw to an end and that noble death is a treasure which no one is too poor to buy. - C.S. Lewis
There will come a time when you believe everything is finished. That will be the beginning. - Louis L'Amour
What will matter then will be people. If relationships will matter most then, shouldn't they matter most now? - Max Lucado
#3
Mestane
-
- Members
-
- 53 posts
Posted 08 April 2020 - 11:50 AM
Ok, i’ll try to explain myself better.
I belive this to be two seperate bugs colliding. I don’t think either has to do with the map specifically, just that they manifest in this map in an interesting, albeit strange way.
First the bug of assigning starting positions for enemy AI, where multiple AI’s get assigned the same starting position in RTS. You know, when they build on the same layout of their base and compete for space to put down barracks, fortress etc.
Second bug in this case is born out of the first in my opinion, because the defenders starting position is inside the fortress, but a reinforcing ai ally’s starting position is outside the castle walls, opposite of the assaulting army (minas morgul as a 3 player map). So now the first bug kicks in and wants to put the defender ai and his allied ai in the same starting position. The ai can’t put them both inside the fortress so the game assigns both defender and ally AIs to the starting position outside the fortress. So this is the second bug here because the defender AI doesn’t behave like the fortress defender but identical to the allied AI outside the walls. In effect the defender AI pushes all his builders out of the fortress and starts competing with his ally for the same base layout, even going so far as to build a fortress (which usually is not available to be built by a fortress defender). This also messes up the win conditions for the assulting army (the player in this case) whereas destroying the fortress citadel and killing the last builder doesn’t defeat the AI. You end up having to economically “scare” the AI into forfeiting to win the battle.
I belive this to be two seperate bugs colliding. I don’t think either has to do with the map specifically, just that they manifest in this map in an interesting, albeit strange way.
First the bug of assigning starting positions for enemy AI, where multiple AI’s get assigned the same starting position in RTS. You know, when they build on the same layout of their base and compete for space to put down barracks, fortress etc.
Second bug in this case is born out of the first in my opinion, because the defenders starting position is inside the fortress, but a reinforcing ai ally’s starting position is outside the castle walls, opposite of the assaulting army (minas morgul as a 3 player map). So now the first bug kicks in and wants to put the defender ai and his allied ai in the same starting position. The ai can’t put them both inside the fortress so the game assigns both defender and ally AIs to the starting position outside the fortress. So this is the second bug here because the defender AI doesn’t behave like the fortress defender but identical to the allied AI outside the walls. In effect the defender AI pushes all his builders out of the fortress and starts competing with his ally for the same base layout, even going so far as to build a fortress (which usually is not available to be built by a fortress defender). This also messes up the win conditions for the assulting army (the player in this case) whereas destroying the fortress citadel and killing the last builder doesn’t defeat the AI. You end up having to economically “scare” the AI into forfeiting to win the battle.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
