A collection of various VRChat mods to make desktop life less miserable. https://vrc.ljoonal.xyz
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
ljoonal e04700cd96
Add some notes on stability
3 weeks ago
Libs Initial commit 3 months ago
NoDetailsForClienters Initial commit 3 months ago
TrustColorChanger Rework TrustColorCustomizer 3 weeks ago
.gitignore Add directory file 3 weeks ago
Directory.Build.props Initial commit 3 months ago
LICENSE Initial commit 3 months ago
README.md Add some notes on stability 3 weeks ago
VRC-Mods.csproj Initial commit 3 months ago


VRC Mods

Tested on 1149 GPL-3 Lines of code

This repository contains my mods for VRChat, using MelonLoader.

I try to minimize the things that a single mod of mine does. That way my mods hopefully don't need that many updates, and maintenance of them will be easy. Because I value stability over adding many fancy new features. So a mod not receiving updates can just mean that it's still working just fine as intended.

To install, just follow the MelonLoader wiki's instructions. After that just drag'n'drop the DLL's into the Mods folder. If you need help join the VRChat modding group to see the guide if you've not done that already.


Modding is against VRC TOS, and the devs are known to ban users who get caught using mods. No warranty is provided for these mods, and they're provided as-is.

Please have a look at the source code & build from source for maximal safety. I also recommend mirroring this git repository if you want to make sure you always have access to the source code even if I need to take down the public git repositories.

If you care for your safety but aren't willing to read the source code and compile the mods yourself, I'd recommend that you only grab mods that the VRChat modding group endorses. This repository might contain some mods that they do not endorse, as they might fall into a grey area of what the moderators there want to allow.

Using mods anyway

I've yet to be banned for using mods, but I've tried to be smart about it, and suggest that you do so too:

  • Don't be malicious.
  • Avoid sharing evidence that you're using mods (screenshots/recordings/streaming).
  • Hide that you're using mods when not in an instance exclusively made out of your friends.

It might only take a single report to get you banned if you're being naughty, but behave and you'll probably be fine.

Mod list

If you want the feature enough to get the mod for it, you should probably also go upvote the canny ticket if there is one.

Trust Color Changer


A mod to allow customizing the trust colors.

Currently implemented:

  • Trust Color Value
  • Trust Color in Toggles
  • Turst Color in Safety Settings page

Credit to emm for being the first one to do this afaik.

No Details for Clienters


Spoof values like FPS and Ping, since VRChat shows them to remote users.

They're usually hidden behind complex debugging menus in the vanilla game. So well hidden so well in fact that I haven't confirmed wherever they are findable without mods, but I trust the people who've told me they are.

Many clients conveniently show them though. And often users users of such clients comment on other peoples' FPS/ping, usually with bad intent. This mod is meant to take combat such users by rendering their bragging/spying meaningless with spoofed values that might seem realistic at first glance.

This mod is not meant to help you be "cool" or try to deceive the VRC system. Because if the VRC devs wanted to, they could most likely easily detect the spoofing. So I'd kindly ask that if you're going to be using this, use at least somewhat realistic values to not give VRC devs a reason to start cracking down on it and ruin it for those of us who just want some more privacy.

You might also want to check out knah's HWID patch & NoSteamAtAll if you're trying to remain a bit more private.

Credit to null from the VRC modding group discord for mentioning the values to use for spoofing.

For developers


Ensure that the required DLL's (listed in the Directory.build.props file and in the individual .csproj files) can be found from standard installation paths (check Directory.build.props). Then use the dotnet build command to build.

Alternatively you can try to open the folder in Visual Studio, but I cannot provide help for using that. If you do want to improve the situation, do feel free to contribute!

Contacting & contributing

Contact me on the modding group Discord, elsewhere, and/or possibly send me git patches if you've already written any code that you'd like to get merged.