If metalmap is not found, mexes can still be built
Moderator: Content Developer
- Forboding Angel
- Evolution RTS Developer
- Posts: 14673
- Joined: 17 Nov 2005, 02:43
If metalmap is not found, mexes can still be built
Is this intended behavior?
Re: If metalmap is not found, mexes can still be built
I would assume this is to make it work with speedmetal-like metalmaps.
Re: If metalmap is not found, mexes can still be built
assumptions are bad, would be best to ask this sort of thing in zkdev forb.
-
- Moderator
- Posts: 2464
- Joined: 12 Oct 2007, 09:24
Re: If metalmap is not found, mexes can still be built
If the metal spot finder identifies less than 6 distinct metal spots (connected areas of non-black metal map) then mexes are able to be built anywhere and their income is base on the metal within the mex radius. This behaviour is in place to make the metal spot system not affect full metal maps where the mex radius is less than the size of the extractor structure.
If the metalmap is entirely black then there are no distinct mexes. I assume you are talking about EvoRTS. You should edit the mex_spot_finder gadget in Initialize to never trigger "Indiscrete metal map detected".
If the metalmap is entirely black then there are no distinct mexes. I assume you are talking about EvoRTS. You should edit the mex_spot_finder gadget in Initialize to never trigger "Indiscrete metal map detected".
- Forboding Angel
- Evolution RTS Developer
- Posts: 14673
- Joined: 17 Nov 2005, 02:43
Re: If metalmap is not found, mexes can still be built
Well for zk too. Couldn't see why you guys would want that behavior, but in the context of metal maps I guess that makes sense. Thanks for the heads up on how it works.
Re: If metalmap is not found, mexes can still be built
Part of ZK's ideology is compatibility with BA maps. If a BA map is cloud-metal-based, ZK will support it.