Updating Versions #7

New issue

Closed

opened 2023-04-09 10:18:21 -04:00 by Xenon257R · 0 comments

Xenon257R commented

2023-04-09 10:18:21 -04:00

(Migrated from github.com)

This will be a pinned issue thread for current and upcoming version updates for the suite to work within Rainmeter's limitations. This is an issue in part due to the complexity of this suite, but can also be my lack of understanding the packaging system they offer.

THE ABSOLUTE BEST SOLUTION IS TO DO A FRESH RE-INSTALL

With every updated .rmskin package, I have ensured that files that 100% can be preserved are made to do so within Rainmeter's limitations (which is mainly .inc and select .ini files), and you can re-apply your old preferences from that point onward. I apologize for the inconvenience, but this frustration should only come with each update, which are few and far between. To reduce the pains of updating databases one by one manually, You can refer to the restoration checklist below.

Restoring as many old preferences as possible

The gist of it is, every time you update this suite, your .json configurations and a few other things are wiped - this is despite me writing specifically in the packaging to ignore said files when updating, but Rainmeter does it anyways. But fear not - before applying the update, you can manually backup the folder by simply Copy-Pasting the BlueArchive directory into a separate directory (keep the copy out of the Skins folder to avoid complications) to re-pull wanted changes back. Alternatively, Rainmeter's update system does provide a "Save Backup" option:

However, this Backup has fully failed on one of my computers, so I advise a manual Copy+Paste backup if you don't want to risk it (thought it appears a failed backup simply restores the old version and aborts the installation of the new one).

So below is an exhaustive list of files that are safe to simply pluck from Skins\@Backup and drop it right back into Skins\BlueArchive:

Upgrading to the latest version, you are safe to restore:

(Merge) your old @Resources\assets directory with the new one
- Make sure it's a merge and not replace! That way, both the old and new are combined
The @Resources\notes directory and its contents
The @Resources\json directory
- DO NOT RESTORE layout.json if you're coming from 1.0.0. This version of layout.json is deprecated.
All new TrayApps you have created, adaptive or simple
- Don't forget to reposition them and re-add them to the new layout.json Database from the ToggleSwitch context menu!
DO NOT RESTORE config.inc if you're coming from pre-1.2.0. This version of config.inc is deprecated.
Any additional .ini, .inc or Skin files you have created/changed yourself
- This step is best skipped for changed files, as the file you have changed may have received an update your suite might need. Instead, it is best to re-change the potentially new files.

After restoring the above files, as much of the old version should be restored. It is encouraged to double-check all your configurations and correct any missing transfers. If anything still remains broken/missing and you are unable to recover your preferences, leave a comment below and I'll see what I can do. Just make sure you didn't delete that @Backup file and did not attempt any further re-installations (they will override your @Backup every time, meaning you will TRULY lose your old preferences this way).

This will be a pinned issue thread for current and upcoming version updates for the suite to work within *Rainmeter*'s limitations. This is an issue in part due to the complexity of this suite, but can also be my lack of understanding the packaging system they offer. ## THE ABSOLUTE BEST SOLUTION IS TO DO A FRESH RE-INSTALL With every updated `.rmskin` package, I have ensured that files that 100% can be preserved are made to do so within *Rainmeter*'s limitations (which is mainly `.inc` and select `.ini` files), and you can re-apply your old preferences from that point onward. I apologize for the inconvenience, but this frustration should only come with each update, which are few and far between. To reduce the pains of updating databases one by one manually, You can refer to the restoration checklist below. ## Restoring as many old preferences as possible The gist of it is, every time you update this suite, your `.json` configurations and a few other things are wiped - this is despite me writing specifically in the packaging to ignore said files when updating, but *Rainmeter* does it anyways. But fear not - before applying the update, you can manually backup the folder by simply Copy-Pasting the `BlueArchive` directory into a separate directory (keep the copy out of the `Skins` folder to avoid complications) to re-pull wanted changes back. Alternatively, *Rainmeter*'s update system does provide a "Save Backup" option: ![image](https://user-images.githubusercontent.com/65873135/230777169-725b68df-ac83-4644-bfec-ad03e5e977da.png) However, this Backup has fully failed on one of my computers, so I advise a manual `Copy`+`Paste` backup if you don't want to risk it (thought it appears a failed backup simply restores the old version and aborts the installation of the new one). So below is an exhaustive list of files that are safe to simply pluck from `Skins\@Backup` and drop it right back into `Skins\BlueArchive`: ## Upgrading to the latest version, you are safe to restore: - (Merge) your old `@Resources\assets` directory with the new one - Make sure it's a merge and not replace! That way, both the old and new are combined - The `@Resources\notes` directory and its contents - The `@Resources\json` directory - **DO NOT RESTORE** `layout.json` if you're coming from **1.0.0**. This version of `layout.json` is deprecated. - All new `TrayApp`s you have created, adaptive or simple - Don't forget to reposition them and re-add them to the new `layout.json` Database from the `ToggleSwitch` context menu! - **DO NOT RESTORE** `config.inc` if you're coming from pre-**1.2.0**. This version of `config.inc` is deprecated. - Any additional `.ini`, `.inc` or Skin files you have created/changed yourself - This step is best skipped for changed files, as the file you have changed may have received an update your suite might need. Instead, it is best to re-change the potentially new files. After restoring the above files, as much of the old version should be restored. It is encouraged to double-check all your configurations and correct any missing transfers. If anything still remains broken/missing and you are unable to recover your preferences, leave a comment below and I'll see what I can do. Just make sure you didn't delete that `@Backup` file and did not attempt any further re-installations (they will override your `@Backup` every time, meaning you will TRULY lose your old preferences this way).

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Xenon257R/blue-archive-rainmeter#7

No description provided.

Rows
Columns