lively-wallpaper-playlist

Lively Wallpaper Playlist

A lightweight utility that automatically cycles through your saved Lively wallpapers and assigns random wallpapers to each monitor at a configurable interval. It is currently in alpha release.

📥 Download

Download the latest installer from the Releases page and run the .exe installer.

⚙ Requirements

🚀 Installation

  1. Download the installer.
  2. Run the installer and follow the instructions. (Note: Windows SmartScreen may warn that the app is from an unknown publisher. Click More info → Run anyway to continue. Don’t worry it’s not a virus (Check the source code if your scared (I would))
  3. If Lively cannot be found, manually locate Lively.exe Microsoft Store installs are usually located in: %LocalAppData%\\Packages\\12030rocksdanister.LivelyWallpaper_97hta09mmv6hy\\LocalCache\\Local or %LocalAppData%\\Packages\\12030rocksdanister.LivelyWallpaper_97hta09mmv6hy\\Build
  4. When it asks for monitor numbers, check your Lively Wallpaper monitor settings and use that (Note: It must have comma’s between monitor numbers, e.g1,2).
  5. When it asks for the folder containing your Lively wallpapers, open Lively → Settings → General → Wallpaper Directory and use that path.

🧠 Configuration

To configure settings, right click on the system tray icon and press Edit Config. config.json Will now open up.

Settings:

📃 Logging

Lively Playlist now includes a built-in logging system to help track activity, diagnose issues, and understand how the application is behaving behind the scenes. The log files are automatically generated and stored in the same directory as your configuration file, inside a dedicated logs subfolder.

To Open the log, right click on the system tray icon and press Open Log. It will now open the current instances log in the default text editor. NOTE: Currently there is only one Mega Log, but in the future it is planned for each instance to have a seperate log.

If anything goes wrong or behaves unexpectedly, checking the logs is the first step for debugging or reporting issues.

📝 Logging Explanation

To understand lets analyze the parts of the log message:

[HASH] YYYY-MM-DD HH:MM:SS [LEVEL] Message

Now let’s break down each section:

⚙️ Features

🧩 Planned Features

🎯 Usability & Interface

⚡ Functionality

🧩 Advanced Features

💬 Feedback & Contributions

If you try this project, I’d love to hear what you think.