Page 1 of 1

Faya

Posted: 18 Mar 2018, 09:35
by Silentwings
2-16 players, 28x28 FFA map.

Features dynamic mex/geo placing in FFA mode (viewtopic.php?f=44&t=31849).

Image
Image


There are two map options:
  • 1. Acid water. Default on.
    2. Geothermal vent mode: (1) None (2) Random (3) Always. Default is random mode, in which the chance of geovents appearing is min(1,nbTeams/6).
Made with World Machine.

DL link: https://springfiles.com/spring/spring-maps/faya

Re: Faya

Posted: 18 Mar 2018, 10:20
by PtaQ
Looks great, gj! We'll try it out today in BA :)

Re: Faya

Posted: 18 Mar 2018, 19:20
by hokomoko
Damn, you're on fire!

Re: Faya

Posted: 19 Mar 2018, 17:01
by triton
Map is great overall but would it be possible ot make it 10-15% smaller? It's a bit empty like this.

Re: Faya

Posted: 19 Mar 2018, 21:54
by Silentwings
Wouldn't that result in very little space to build a base within a single spot of the inner ring? Fwiw I am pretty certain that the total amount of buildable ground is about the same as throne/dworld.

Re: Faya

Posted: 30 Mar 2018, 11:29
by tulipe
Mexs are not displayed (only start positions) in "Faya v1" metal view in springlobby 0.264 . Image (PtaQ wrote in discord it's cause faya has dynamic mexes.)
Even if mexs are generated ingame, should a approximativ position or something be displayed in springlobby map view to give an overview? (How understand amount of mexs for players who don't know this new map?)
Same questioning for others maps with dynamical mexs placement.

Re: Faya

Posted: 30 Mar 2018, 19:50
by Silentwings
SL will view the map as having no mexes, because the metal map (in the sense of what is compiled into the map) is blank. This is intentional. Mexes and geos are positioned dynamically, after the battle has been launched. Their positions/amounts depend on the game mode, the number of players, the start positions used, and whether the game implements viewtopic.php?f=44&t=31849.

Maybe it would be better if SL displayed the full 16 player metal/geo config. This could be done, with some (hacky-ish) extra work, but it isn't the current behaviour.