yea yea, no need for hivebootlick opinions just go back to your 3mb castlefight, real games need real space
A problem is that a bigger max map size allows for more abuse, distributing assets that were not meant to be via a Warcraft III map. I do not see the argument for creativity. The original map size limit was 4 MB, if not less, and that’s when creativity (creating something novel that is also usable) sparked, trying to build something with less resources. The terrain, configuration, map script are quite fixed costs, the preplaced doodads grow only slowly, as do objects, respectively you would hit other limits increasing them too much, so it’s really rather about textures, complex models, sounds pushing the map size limit. Back in the day, you did not make exact depictions of everything, but rather used some standard resources and put them in other settings, cueing the player for the imagination while it still retained the Warcraft III style.
ok buddy, your point was lost around 2008~
I do agree but like i said if Blizzard did decide to do this they should create simple pop-up setting so people can just refuse to download maps once they see the filesize. Sounds like a win win to me.
But i generally do agree that 512mb is enough, any mapmaker worth their salt who isn’t dumping unoptimized ripped garbage in their map would find a way to make it fit.
myea its not enough when the map is as big as a standalone game 
anyway this issue has been fixed with a script that turns on war3 local files and transfers needed files in the correct game folder location for the player hence unlimited size