Simpiflified the configuration of SaveLevelDataComponent (only need to set the SaveGameSettingsResource now) by:
Move from save names to save name prepends (e.g. save_game_data.tres -> save_) within SaveGameSettingsResource
Move the default_icon_resource export out of SaveLevelDataComponent and to SaveGameSettingsResource
Move the ui_node export out of SaveLevelDataComponent and to SaveLoadUI
## Features
* Add Autosave support
* Simpiflified the configuration of `SaveLevelDataComponent` (only need to set the `SaveGameSettingsResource` now) by:
* Move from save names to save name prepends (e.g. `save_game_data.tres` -> `save_`) within `SaveGameSettingsResource`
* Move the `default_icon_resource` export out of `SaveLevelDataComponent` and to `SaveGameSettingsResource`
* Move the `ui_node` export out of `SaveLevelDataComponent` and to `SaveLoadUI`
Current Known Issue: AutoSave date is suing modified date but they're all being modified about the same time, meaning the save time looks identical.
Maybe created save time should be stored within the resource rather than checking the file modified?
Current Known Issue: AutoSave date is suing modified date but they're all being modified about the same time, meaning the save time looks identical.
Maybe created save time should be stored within the resource rather than checking the file modified?
This is mostly ready to go, although there is 1 issue I can't figure out.
The AutosaveNotification UI is pretty random about being visible on screen even when the visibility is true. Even weirder is initially, I could get it to show up by just adding print(visible) as if that was affecting the visibility. I don't really understand it and will need to investigate it further.
This is mostly ready to go, although there is 1 issue I can't figure out.
The `AutosaveNotification` UI is pretty random about being visible on screen even when the visibility is `true`. Even weirder is initially, I could get it to show up by just adding `print(visible)` as if that was affecting the visibility. I don't really understand it and will need to investigate it further.
Features
SaveLevelDataComponent
(only need to set theSaveGameSettingsResource
now) by:save_game_data.tres
->save_
) withinSaveGameSettingsResource
default_icon_resource
export out ofSaveLevelDataComponent
and toSaveGameSettingsResource
ui_node
export out ofSaveLevelDataComponent
and toSaveLoadUI
Current Known Issue: AutoSave date is suing modified date but they're all being modified about the same time, meaning the save time looks identical.
Maybe created save time should be stored within the resource rather than checking the file modified?
This is mostly ready to go, although there is 1 issue I can't figure out.
The
AutosaveNotification
UI is pretty random about being visible on screen even when the visibility istrue
. Even weirder is initially, I could get it to show up by just addingprint(visible)
as if that was affecting the visibility. I don't really understand it and will need to investigate it further.WIP: Autosaves and Simplifying SaveLevelDataComponentto Autosaves and Simplifying SaveLevelDataComponent 1 month agoc1ca3a98cb
.