---

2019 NOV 30

• Less folders to configure initially
  • This means we'll have to make some adjustments to some of the repository structures!
  • Add some root configuration for automation?
  • Some mechanism to identify folders...
• Separate leveldesign and graphics build!
  • Can we have the configuration entirely in-tree, rather than as a loose workspace?
    • At least, a way to generate a workspace from an in-tree configuration...
• Separate lightmapping from shape export.
• There's too much duplication between configurations, especially the configuration for ecosystems and continents... Use georges sheets for configuration, or another mechanism that can inherit parameters? Shouldn't most of these parameters be part of the .continent sheet?
• Some continents have different names in different contexts...
• Continent boundary can be different between RBank build boundary, boundary specified in continent sheet, and boundary specified in land file... How to consolidate?

A build project essentially has inputs... and outputs which can be either installed or used by another build project. Currently build projects depend directly on using fixed paths of their dependencies. It could be nice if instead build projects generate a list of lookup directories based on their output. (Both lookup directory lists of input data for artist tools, as well as lookup directory lists for build tools and runtime!) Example: Project may list the directories of all .shape it outputs, a depending project just needs to reference the project, and the list type, rather than any actual path!

Could we build continents directly based on continent sheets???