Skip to content

Auto-tiler auto-bake #6

@Kenoshen

Description

@Kenoshen

You should be able to tell the auto-tiler to auto-bake on save. This saves us from having to come up with a separate parser to parse in the special AutoTile layer type and it reduces friction to using the AutoTiler.

Tasks

  • trigger the Bake command on save
  • make the Baked layer invisible and un-editable and locked to the auto-tile level
  • automatically delete the old baked layer and replace with new baked layer?
  • BONUS: only re-bake the levels that have auto-tile changes to them to avoid unnecessary merge conflicts
  • BONUS: only re-bake the entire world if the auto-tile rules change

Questions/Concerns

  • One issue that I can see being a problem is that every time you click the Bake button on the AutoTile layer, the entire Baked layer is generated. This is obviously a feature and not a bug, but the problem is that if you are editing Level_1 and then you click Bake, you've now just re-Baked every other Layer_N. And the way it handles the auto-tiling is that a new seed value is generated and used to re-calculate all of the other levels. It would be really nice if Baking had the option of only re-Baking the levels that have changes or if the auto-tiling rules have changed. That way most of the work of re-Baking is focused just on the level you are working on and doesn't cause unnecessary merge conflicts.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions