Quality-of-life Editor tools for VRCFury. The goal: features appear where you’re already working — right-click a page, click a button on a flipbook row, see a banner on a Toggle, drop in two objects to swap references — instead of hiding behind a separate window.
The framework is designed so adding a new tool is usually a single small file with one [InitializeOnLoad] registration. See the Adding a Tool wiki page.
Object references whose target has been deleted, and pops a non-modal window listing each one with a Ping button. Dismiss it once and it stays dismissed until the next reload — so real problems can’t linger silently, but you don’t get nagged after you’ve acknowledged the situation. Can be re-run anytime via Tools -> WhyKnot -> wk-vrcfury-qol -> Check for missing references….useGlobalParam = true and globalParam = MenuPath are kept in sync. Per-toggle opt-out via the banner button or right-click menu. Stops VRCFury from silently renaming parameters during avatar regen.Preview button that creates a temporary, non-saveable avatar copy in place, applies the selected toggle or page to that copy, and hides the source avatar in Scene view. It does not move or reframe the Scene camera. While the copy is active, the same button turns into a red Stop Previewing button that destroys the copy and restores visibility.Duplicate button next to every Page #N label, or duplicate to the end from the right-click menu.Duplicate item, or use Copy to page on a flipbook page action to append just that one BlendShape / Material Swap / action to another page.AssetDatabase.Refresh() even when Unity is unfocused. It does not watch the whole project. Per-package session logs live under %LocalAppData%/WhyKnot/Logs/dev.whyknot.wk-vrcfury-qol/; hot-reload sessions use %LocalAppData%/WhyKnot/Logs/dev.whyknot.wk-vrcfury-qol.Editor.hotreload/. Open them from Window -> WhyKnot -> VRCFury QoL -> Logs and check watcher state from Window -> WhyKnot -> VRCFury QoL -> Hot Reload Status.Detailed walkthroughs of every tool live in the Tools Overview wiki page.
Add the WhyKnot VPM listing to the VRChat Creator Companion, then this package shows up under Manage Project -> Add Package.
vcc:// handler URL and VCC opens with the listing pre-filled. Click I Understand, Add Repository.https://vpm.whyknot.dev/index.json, click I Understand, Add Repository.Unity compiles the package into a dedicated dev.whyknot.wk-vrcfury-qol.Editor assembly (Editor/ only — nothing leaks into runtime builds). Hard-depends on com.vrcfury.vrcfury (>= 1.1300.0); VCC will refuse to install without VRCFury present.
For Unity projects not managed by VCC: download dev.whyknot.wk-vrcfury-qol-X.Y.Z.zip from the latest release, unzip into Packages/dev.whyknot.wk-vrcfury-qol/ (so Packages/dev.whyknot.wk-vrcfury-qol/package.json exists), and Unity’s Package Manager picks it up on next refresh. VRCFury must already be installed in the project.
Tested against VRCFury 1.1303.x on Unity 2022.3.
For per-clone setup steps (hot-reload bootstrap, etc.) see the Installation wiki page.
A tool is a small [InitializeOnLoad] static class that registers itself with VrcfQol. The framework provides typed helpers so your tool never has to walk the reflection cache by hand. The full developer guide with examples for every Register* method lives at Adding a Tool.
These tools make real, destructive changes to your scene (deleting source VRCFury components during a migration, replacing object references in bulk, forcing useGlobalParam on by default, etc). Always:
Bug reports, feature requests, and pull requests are all welcome. See CONTRIBUTING.md for the dev loop and PR conventions.
Licensed under the GNU General Public License v3.0 or later. See LICENSE for the full text.
dev.whyknot.wk-vrcfury-qol
https://github.com/RealWhyKnot/wk-vrcfury-qol
1.2.2 (Changelog)
2022.3 or later
No dependencies
No legacy packages