Discontinuation of HRtoVRChat


HRtoVRChat will continue to work.

Direction of HRtoVRChat

The decision to discontinue HRtoVRChat was not light, but I feel as if it is time to sunset the program. As of right now, it has not reached End-of-Life (EOL). Any outstanding bugs will be fixed and any security breaches will be patched. All working services should be maintained so long as they continue to support us.

Support for HRtoVRChat

As of right now, if anyone has any questions about HRtoVRChat, I will answer them out of kindness, but I am not going to prioritize them anymore. Any issues that are not critical will be left unassigned and most likely ignored; however, any PRs that can pass checks, I am happy to merge and build.

When will HRtoVRChat Retire?

I plan to retire HRtoVRChat on January 1st, 2024. Once retired, no bug fixes will be fixed, no security breaches will be patched, and the GitHub page will be archived. Anyone is free to fork the repository afterwards and continue the project if they wish to. I would be more than happy to answer any technical questions about any piece of the software that any developers may have.

Will HRtoVRChat Continue to Work After Retirement?

I think that's a very ironic question ("work after retirement"), but yes, so long as VRChat does not change their internals regarding OSC (yes, I know about OSC Query, regular OSC should still work). HRtoVRChat is completely client-based, relying off of no servers (excluding providers that are cloud-based).

What's Next?

Join my discord or keep up with my newsletter to know what I'm doing next. I will have officially closed the VRChat chapter of my life after retiring HRtoVRChat, and I feel as if it was about time. I mean, I haven't played the game in a year. Eh, maybe I'll join it again some day to see what it's like now. ¯\_(ツ)_/¯ 

thanks for sticking around for so long everyone, and thank you for allowing me to make cool things for you all. peace ✌️🧡