sandbox: MaxLatitude requirement for Space Elevator
alienvalkyrie A problem that was also touched on a bit in the mentioned GNA ticket: If we restrict the Space Elevator to only be buildable near the equator, it will (under current rules) be completely unbuildable on alltemperate maps. For effects, there are workarounds for this (since different effects can activate and stack based on server settings / global latitude requirements); this is not possible for a building, since that can only have one requirement vector.
This is fine if the alltemperate map is meant to emulate a small section of a larger planet in the middle latitudes, but it still raises the question if we want this to be the case, and if not, what to do about it.
The second question is what latitude bound to use exactly – the only numbers in the GNA discussion seem to implicitly assume degrees, so the 5 in the commented-out requirement would work out to 5 * 1000/90 = 500/9 or about 55.56 latitude points in our 1000-based implementation; I'd at least round that up to 60 to be on the slightly safer side for smaller maps; though I do feel it could still be much higher.
(The question of balance, with this change favoring players who happen to start near the equator and grab territory there early, is probably largely irrelevant for a ruleset like sandbox.)
Can we simply lock alltemperate disabled on sandbox?
alienvalkyrie alienvalkyrie alienvalkyrie I also bumped the latitude range up to +-150, since 60 was unreasonably tight in maps generated with standard settings; this should work reasonably well, including with changed wrap and singlepole settings.
alienvalkyrie 
sandbox Space Elevator has a commented-out "MaxLatitude" requirement with a comment that it should be enabled once we have support for it. Now we have. Check that also the value makes sense with the requirement implementation we have.