cyberpresidentvanellope/Bubberstation
1
0
Fork 0
mirror of https://github.com/Bubberstation/Bubberstation.git synced 2026-07-20 20:45:28 +01:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #29601

Browse Source
This commit is contained in:
Jordan Brown
2017-08-01 09:37:28 -04:00
parent f878d98664 bc687f2677
commit 3ec4aec215
77 changed files with 159 additions and 159 deletions
Download Patch File Download Diff File Expand all files Collapse all files
code/modules/procedural_mapping/mapGeneratorReadme.dm
+2 -2
View File
@@ -80,7 +80,7 @@ mapGeneratorModule
Simple Workflow:
1. Define a/some mapGeneratorModule(s) to your liking, choosing atoms and turfs to spawn
#Note: I chose to split Turfs and Atoms off into seperate modules, but this is NOT required.
#Note: I chose to split Turfs and Atoms off into separate modules, but this is NOT required.
#Note: A mapGeneratorModule may have turfs AND atoms, so long as each is in it's appropriate list
2. Define a mapGenerator type who's modules list contains the typepath(s) of all the module(s) you wish to use
@@ -98,7 +98,7 @@ Simple Workflow:
Option Suggestions:
* Have seperate modules for Turfs and Atoms, this is not enforced, but it is how I have structured my nature example.
* Have separate modules for Turfs and Atoms, this is not enforced, but it is how I have structured my nature example.
* If your map doesn't look quite to your liking, simply jiggle with the variables on your modules and the type probabilities
* You can mix and map premade areas with the procedural generation, for example mapping an entire flat land but having code generate just the grass tufts