You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, Ogmo doesnt handle the need for multiple level types very well (ie, some levels need these layers, some levels need those layers, etc). Currently you either need to have extra layers that go unused between levels (which can lead to bloat), or you need to use multiple Ogmo projects, which is not a great solution either.
Adding a Layer Template system will hopefully fix this issue. This would entail these changes:
In Project Settings
Add an Add Template button to the Layers tab, which creates a Popup to name the new Layer Template
Add a dropdown to the Layers tab to swap between Layer Templates
Add a Delete Template button to bring up a Popup with a dropdown to select the template to delete
In Level Editor
Add a dropdown to the Level Values popup that swaps Layer Template on the Level
This may or may not work, but we should try to maintain as much of the Level data when swapping between templates - matching Layers with the same name and the same type is a good start
If the Level's Template is changed, add a warning that the Level's data will be changed/erased
In the Project file (ie project.ogmo)
Replace the layers field with a templates field containing an array of layers arrays
This is a breaking change, but we can add logic to auto-update project files (ie if a project file is found with a layers field, convert it to a templates field containing the layers field
In the Level file (ie level.json)
add a template field that holds the name of the template used in the Level
The text was updated successfully, but these errors were encountered:
Right now, Ogmo doesnt handle the need for multiple level types very well (ie, some levels need these layers, some levels need those layers, etc). Currently you either need to have extra layers that go unused between levels (which can lead to bloat), or you need to use multiple Ogmo projects, which is not a great solution either.
Adding a Layer Template system will hopefully fix this issue. This would entail these changes:
Add Template
button to the Layers tab, which creates a Popup to name the new Layer TemplateDelete Template
button to bring up a Popup with a dropdown to select the template to deletelayers
field with atemplates
field containing an array of layers arrayslayers
field, convert it to atemplates
field containing thelayers
fieldtemplate
field that holds the name of the template used in the LevelThe text was updated successfully, but these errors were encountered: