Hi everyone,
I’d like to raise a concern that currently affects not only my own work but potentially many other creators as well.
Over the last few days, I’ve been informed by the moderation team that all of my resources containing .cs files — basically, every interactive or script-based asset — are being unpublished due to alleged “license violations.”
The claim is based on the idea that some of my scripts follow the same general structure as the CUA Editor Tutorial by Hazmhox, which was released years ago as a public learning example.
To clarify:
For me a tutorial is a learning guide, not a proprietary codebase.
It demonstrates the basic structure of an MVRScript plugin — exactly the same pattern used by practically every plugin on the Hub.
Nevertheless, this standard structure is now being interpreted as “copyright-protected code,” and I’m being asked to relicense or remove everything that follows it.
The result is that all of my interactive assets — including long-standing ones used as dependencies in countless scenes — are now being taken offline.
That means many community-made scenes will no longer function.
All of my work has been created voluntarily, without payment, and shared freely to help others.
Being asked to retroactively rewrite or relicense code that follows a common VaM standard feels unreasonable and ultimately harmful to everyone who contributes free content to this platform.
If the CUA Editor Tutorial’s basic structure is now considered protected intellectual property, then every plugin author on this platform could be affected.
This kind of interpretation risks discouraging future creators from making or sharing anything interactive at all — which would be a huge loss for the VaM community as a whole.
meaning every creator who has used or learned from that tutorial would have to list it as a credit and adopt its CC BY-SA license.
That would include the majority of interactive resources currently on the Hub.
– Frief
I’d like to raise a concern that currently affects not only my own work but potentially many other creators as well.
Over the last few days, I’ve been informed by the moderation team that all of my resources containing .cs files — basically, every interactive or script-based asset — are being unpublished due to alleged “license violations.”
The claim is based on the idea that some of my scripts follow the same general structure as the CUA Editor Tutorial by Hazmhox, which was released years ago as a public learning example.
To clarify:
For me a tutorial is a learning guide, not a proprietary codebase.
It demonstrates the basic structure of an MVRScript plugin — exactly the same pattern used by practically every plugin on the Hub.
Nevertheless, this standard structure is now being interpreted as “copyright-protected code,” and I’m being asked to relicense or remove everything that follows it.
The result is that all of my interactive assets — including long-standing ones used as dependencies in countless scenes — are now being taken offline.
That means many community-made scenes will no longer function.
All of my work has been created voluntarily, without payment, and shared freely to help others.
Being asked to retroactively rewrite or relicense code that follows a common VaM standard feels unreasonable and ultimately harmful to everyone who contributes free content to this platform.
If the CUA Editor Tutorial’s basic structure is now considered protected intellectual property, then every plugin author on this platform could be affected.
This kind of interpretation risks discouraging future creators from making or sharing anything interactive at all — which would be a huge loss for the VaM community as a whole.
meaning every creator who has used or learned from that tutorial would have to list it as a credit and adopt its CC BY-SA license.
That would include the majority of interactive resources currently on the Hub.
– Frief
