I think more that the engine will always create some errors for any newer implementations that weren't considered back then because of limitated technology. Also there will be error becausr the code wasn't written by this team and they don't have a deeper knowledge of it. And also, mostly, because due to the technology of the time, Devs back then might have resorted using some tricks to make their code functional and optimized. So they might have written something that works but only in that circumstances or that is implemented in a clever way and links multiple things
So the release went probably like this. The New devs improved the pathing code and tested it. It worked and you can actually see that Melee units are better now. There is no actual reason to play an entire game to test it because the new team thinks that it is only linked to the pathing. But the previous pathing code had some trickery into it and was connected to buildings and natural resources and the 'bump/collision' effect.
They tried to fix the gate that didn't take damage from the sides from petards by removing that additional parts that made the building Gate resistant to it but they didn't know that the old code had the same code connected to the TC as well, that protected the TC from explosive seige units.
Looks like the DLC_BLACK terrain, could be a constant number typo in one of the script files coming along with the new season change.
I had the same issue and it was because of the no snow grid mod.
Honestly I thought this post was a joke, but by the end I'm not sure ...Ok, I guess some people might think I am memeing again, but honestly:
Calm down guys its still a beta. I think they will fix all issues before release.
Now some might argue: "TurboNoob, as your name suggests, you seem to be a real noob, don't you know the game was already released like more than 2 months ago, it is no beta!"
In response to this: Little do you know, its actually a payed beta - in the sense, that you have to pay in order to be allowed to playtest it. It is ok, that the game now was officially released, as I hope it brings fun to casual and new players, like we were as kids, when we started playing AoE2, which also was not perfect to current standards, but we loved it.
Of course, when we played it more and more, we got better and therefore spotted things we wanted to change or be invented, so we can make the game more competative.
From my point of view, voobly AoE2 was solid for competative and casual game play purposes compared to AoE2 1.0.
Now I see that the devs are active, and trying to respond to issues and also wishes from the community. While new players might not be able to spot issues, most of you seem to be able, so please bug-test the game further and make constructive feedback.
But please only judge the game on 14.11.2020. Game will be out then for a year, and by then we can see how it performs. <3
POEAnd D3 is not a new game but it is more or less the leading ARPG right now.
Well, this would be the dream scenario I guessMaybe you guys are on to something. What if AoE4 is just aoe2 with a new engine that enables the devs to implement all the DE features without any of the bugs. It will solve pathing issues from the core, instead of tweaking unit box sizes which allow units to pass walls, or change the gate structure without it resulting in dying tcs.
It will not be the same game.Well, this would be the dream scenario I guess
That intentional to prevent laming Kappa.
That intentional to prevent laming Kappa.
Ok, they released a Hotfix before ( https://www.ageofempires.com/news/aoe2de-hotfix-34793/ ) but deleted it shortly after. Hmm, maybe found some more problems?
They actually tested it before releasing? This is progress guys!!