How to use playfield_static.yaml

Discussion in 'Planets & Playfields' started by pdog, Jul 22, 2018.

  1. pdog

    pdog Ensign

    Joined:
    Jan 1, 2016
    Messages:
    25
    Likes Received:
    4
    Hi all,

    Can someone tell me how you tell the game to use the playfield_static.yaml instead of the playfield_dynamic.yaml within a scenario folder when generating a new game/save?

    This is for a server setup.
     
    #1
  2. Needleship

    Needleship Master of Custom Terrain

    Joined:
    Apr 13, 2017
    Messages:
    479
    Likes Received:
    800
    Hmm... don't really have knowledge about scenarios, but -

    Playfield_dynamic.yaml contains data of planetary basic settings, biomes, texture distribution. All this is seed dependant.
    Playfield_static has weather, resources, POI, creatures... - Things that don't change with a game's seed.

    Both are combined by EGS to a playfield.yaml. That one is tied to a specific seed.

    So I guess there is no need to 'use it instead'...
    Either you use playfield_static and playfield_dynamic, or you use the resulting playfield.yaml.
     
    #2
  3. pdog

    pdog Ensign

    Joined:
    Jan 1, 2016
    Messages:
    25
    Likes Received:
    4
    Thanks for the reply. I will just use the playfield.yaml that are created in the saves directory.
     
    #3
    Needleship likes this.
  4. stimdealer0001

    stimdealer0001 Captain

    Joined:
    Sep 14, 2015
    Messages:
    159
    Likes Received:
    149
    That's the easiest way to go about modifying your planets honestly. The only downside to just editting the playfield.yaml is you won't be able to modify terrain settings using the SSG. It requires the dynamic and static files, and puts them together into a new playfield.yaml when you export.
     
    #4
  5. pdog

    pdog Ensign

    Joined:
    Jan 1, 2016
    Messages:
    25
    Likes Received:
    4
    Thanks, got it now.
     
    #5
    Needleship likes this.

Share This Page