qdaro
patreon
Qvaro (TRIAL)
🕑 Added 2025-10-16 06:59:00 +0000 UTCFast and comfy resource manager for VaM.
This is a TRIAL version with 100 packages limit and a lot of features disabled.
Version: 1.3.1 (Changelog)
Installation
1. Qvaro is a single 15MB exe file that needs to be placed in your VaM directory.
2. Launch it. That's it.
~. If you've updated your OS anytime in the last 5+ years, it should just work. Otherwise you might need to install Windows WebView2.
Support
There's a Chat channel called "Support". Use it to report or discuss issues.
False positive virus detection
The app is made using Go programming language which produces fast, lean, single file binaries (perfect for this use case). But some antiviruses don't see this packaging type often, and trigger false positives. This is a known quirk with go binaries, but also happens to pretty much all unsigned apps. You can run the app through VirusTotal to see the couple of weird antiviruses that don't like it and decide for yourself if you trust it or not. I could prevent this by signing the binary, but the signing certificates can cost up to thousands of dollars per year 😭, sooo I'm not doing that... It's a weird racket - pays us or we tell your users your app is a virus...
Data
All the data Qvaro produces is stored in Qvaro_Data directory. It's just a couple configs and a catalog file. There is no garbage like extracted thumbnails or anything else (thumbs are served directly from vars as needed).
Comments
qdaro
I do have an idea on how to make Qvaro aware of additional vars. I'm experimenting with virtual categories. You'll be able to create a virtual Qvaro category that'll point to any location on your drive(s). Qvaro will then catalog this location as if it's an additional category inside AddonPackages. It'll be a bunch of work since it requires a lot of refactoring though, so no ETA :(
Rosemarie
The UI work on this app is *chefs kiss* really nice. It's the best looking addon for VaM I've ever seen. Also, I love being able to look at, sort and manage my assets this way without having to open VaM - and without having to install that "Server Manager" VAR thumbnail extension for Windows explorer. The ONLY thing keeping me from joining a paid tier is that you hard-coded the VaM root folder's AddonPackages, Custom and Saves folder trees into the app - which immediately makes this a chore to use for anyone using JayJayWon's BrowserAssist to dynamically load and offload our VAR packages. To be able to see all my assets using your app, I'd have to open VaM, then have BA move all my offloaded packages back - and that defeats the value I would have found in your app - being able to manage my assets without opening VaM. I would never give up BrowserAssist's VAR manager - I have nearly 7000 packages in my repo - and without BrowserAssist the game would take a year to start up or load a scene, if it didn't crash while trying. Prior to BA, like many "power users", I was clumsily keeping smaller repositories to try and only load what I thought I needed for a session, which is awful. I highly suggest - and request - adding the ability to specify additional and/or alternate locations. If you have a good reason not to open it up to letting the user specify any location they want - I would request you at least add a "BrowserAssist compatibility mode/setting" that aggregates the contents of the Saves\PluginData\JayJayWon\BrowserAssist\OffloadedVARs folder with what it finds in the default folder trees. I realize this may get complicated when someone decides to run a VAR de-duplication or something that alters the VAR packages inside OffloadedVARs. That would cause an issue with incorrect dependencies in BrowserAssist until the user manually resets the VAR cache. For maximum data safety and compatibility, I would suggest disabling any feature in your app that moves or modifies VAR files while this "compatibility mode" is active. You could display a message for the user that they should temporarily disable BA's VAR management before doing anything that changes VARs. Then they could go ahead and do that - come back and disable compatibility mode - which re-enables VAR de-dupe and locks the app to whatever is in the AddonPackages folder again. Since de-duplicating is not something someone would be doing extremely often, I think this workflow would be ideal. It maintains compatibility with BrowserAssist, allows us to view all our assets even if BA has offloaded them, prevents corrupting BA's dependency cache, and still allows us to use the de-duplication features, once the app notifies us and we turn off BA. I've never bothered to write something this long - but I really like your app - and I'd really like to be able to use it. I hope this was helpful!
