Ok - Ok. I was upset enough that I decided to stay up late at night to check if what I suspected is true.
I recently saved a number of maps in a another person's campaign on 1.30. It completely bugged the AI for every single computer AI using AI made with the AI editor. When those missions were played, the AI just sent both the workers meant for getting gold and the ones meant to getting lumber to the gold mine, and made nothing else. So all that happened was there was an overstocked goldmine with 8-9 peons trying to mine it, the AI did nothing else. The other maps in the campaign work fine, since they were saved on 1.29. I just had my friend test the maps on the PTR, and the exact same problem persists. I will post screenshots later.
Let me explain why this is so upsetting. I thought that bugs related to 1.30 were ones that affected how the game was played, but once the next patch came the gameplay would be fixed, since the errors related to 1.30 did not actually effect the map itself, but just how it was played. What this AI bug shows is that anything made with 1.30 actually completely ruins the map, and there is no reason why it does so. The only changes I made to those maps were language /grammar mistakes.
In addition to those to maps in that campaign, I have recently edited 2 entire campaigns on behalf of 2 other people, all done in 1.30. Of course I didn't bother testing, since there was no reason for me to suspect anything would go wrong.
Can I just ask, has this 1.30 version actually destroyed those maps, and was I just a fool to spend time on those 2 maps in that campaign + the other 2 entire campaigns on 1.30? Like I said, I had no issue with 1.30 affecting gameplay, but it seems it has actually destroyed AIs permanently in maps. This is really upsetting for me. 2 entire campaigns + 2 maps in 1 campaign are all heavily based on melee gameplay, which includes AI. These maps will be ruined if the AI is permanently broken.
I will add pictures tomorrow, but there is nothing to see--- just 9 peons on 1 goldmine, not making anything.
Edit1: Also, the fact that the map reviewer who discovered the bugs was on 1.29 is important, since it means it actually messed up the map itself, not just affecting the gameplay (of course it bugged on 1.30 and the PTR as I said above, but just want to emphasise this). If it was just limited to 1.30 and the PTR, maybe you could argue its just a gameplay issue,and has not effected the core map itself. But if someone on 1.29 had the same error, it means 1.30 permanently destroyed the AI.
I can understand a permanent bug affecting maps made on a PTR, since they are still tests. But I made these on 1.30, an official release, and I waited a week or so to use it incase of any huge bugs. I really hope someone can explain how a permanent error could have occurred such as this.
Edit 2: Pictures