their map has over a terra-byte of memory.

I just want to say that you are grossly overestimating the number of bytes that each map takes. IIRC, Warlight uses 1024^X for map size, so...

Terabyte = 1024^4, Where your suggestion is
Gigabyte = 1024^3
Megabyte = 1024^2, 2 Megabytes is the maximum allowed for a map.
Kilobyte = 1024^1

This might not seem like a lot, but you're off by about a factor of 1,000,000. Also, a 1 Terabyte map wouldn't really be a good use of a hard drive... (The high-end ones today get to about 8 TB.) (And don't even THINK about it fitting on an Android or iPhone.)

EDIT: Also, downloading a 1 TB map would take forever. Don't do it. Realistically, maps would probably have to limit at two-digit MB to keep download speeds decent.

Edited 2/3/2015 19:42:58

I was thinking more in another range
Lets think about this
3.0 Mb map (US) has 3000 territories (roughly taken)
10.0 Mb maps have then 10 000 territories.
100.0 Mb (which is 0.1 Gb) has already 100 000 territories.
I don't think anyone would like to make or play a map more than 100 000 territories...
I was thinking in a territory range of >3300 to at most 20 000 which means at most 20Mb.
(Starting with more territories in a game could solve the issue of long time expanding.)

Even if there're 100 of those supermaps and 1000 normal maps on warlight. The capacity would still only 5 Gb which is 0.005 Tb Space wouldn't be any problem
a 1Tb map would have 1 000 000 000 territories! which is absurd and not realistic to make or play.

Edited 2/3/2015 21:24:37

@Riyamitie okay, then we should make the mapmaker follow that formula whenever the map is over a megabyte, which renders it a "Supermap." The new maximum should then be 10 megabytes.
PS sorry for my extreme derpyness :P

I think a 3,000 - 5,000 territory amount would do my long-ignored/unused Milky Way Galaxy map idea.