Migrating from v1.x.x to v2.x.x
Brand new, big update is out! If you're here, I assume you're already a bit familiar with VALocker. Let me tell you about what's new, what's changed, and what you need to do to transition as smoothly as possible.
I've rewritten VALocker from scratch. What does that mean? First of all, it is much easier to update and maintain, since it was redesigned with the hardships of v1.x.x in mind. The UI was redesigned so it's more consistent. Plus, you can now add your own custom theme! More importantly, VALocker will now automatically check for updates and update files. You won't need to redownload VALocker unless a new version is out. It's also been designed to store all your files in the same place, %APPDATA%/VALocker/. That means the download simplifies to a single executable that you can put anywhere. Same goes for the Python files (although the Python files need to be together).
VALocker also uses a new library to capture screenshots, betterDXcam, a fork of DXcam, maintained by me. Why? DXcam doesn't support changing resolutions on the fly, and it was last updated by its maintainer 2 years ago. I should be able (through my very limited knowledge) be able to provide more support for DXcam, tailored especially to VALocker.
My proudest feature yet, however, is support for other resolutions!! VALocker now allows you to pick between preset configurations that I manually calculated, but you can make a custom one yourself following this guide.
- Support for other resolutions
- Automatic updates
- Faster detection
- New UI
- Theming
- Easier to maintain structure
Because of all the changes, some options aren't currently available or were deprecated, such as:
- Map Specific Agents, I want to find a better way to do this, no promises on when implementation will be added.
- Auto-Drop-Spike, Adding more tools like this may make it more complex to change resolutions, still not sure how to fix this.
- Minimize to a tray icon, VALocker is a fully-fledged GUI, I see no point in keeping it as an option.
- Most settings, I will add them back, but I am exhausted with all the new updates, most settings will be added later on. They can be changed in the config file as of right now.
Migrating is very easy, I've written v2.x.x with migration in mind, here's what you need to do. If you don't care about your old data, you can simply delete your old VALocker folder, download v2.x.x, and run it. Thats it.
If you do care about migrating your data, all you need to do is replace the OLD VALocker executable (the v1.x.x exe) with the v2.x.x executable. Your settings, stats, and saves should be automatically converted to the new YAML file format and moved to the new directory. It may not seem like anything is happening, VALocker only shows the UI after it has moved all the files, so don't fret. After that, you can move the exe wherever your heart desires. It may seem like nothing is happening for a couple seconds (~7ish)
However, just in case, I would STRONGLY recommend backing up the data file.
Once you first open VALocker, it won't try to migrate your files anymore. If you want to re-migrate them, go to %APPDATA%/VALocker/settings/settings.yaml and set the alreadyMigrated value to false.
- (Optional) Back up old files, VALocker will delete old files when it has migrated them.
- Download the new v2.x.x EXE
- Replace the old v1.x.x EXE with the new v2.x.x EXE, as seen below
- Run VALocker
- When the GUI appears, you're done!
If you've created your own custom locking config, it WON'T be migrated, since it requires changing the v1.x.x Python files. However, I've written a guide (also linked above) on how to create your own config.