I want to clarify my position regarding the ongoing accusations from the VaMHub moderation team that I “copied copyrighted code” from the CUA Editor Tutorial.
These claims are factually incorrect, technically misleading, and based on a misinterpretation of VaM’s own scripting framework.
What was actually used
The portions of code referenced by the moderators are standard structural elements required for any VaM plugin to function —
such as plugin headers, JSONStorable definitions, and “About” sections that display plugin information in the UI.
These are not creative or original works, but part of VaM’s MVRScript framework —
a public scripting structure that every creator must use to make their plugins load properly in the engine.
Even the so-called “evidence” shown by moderation consists of these same framework elements, used identically in countless other VaM plugins.
Code comments, structure, and templates are not copyrightable
The examples cited by moderation include lines such as:
#region PluginInfo
public string pluginAuthor = "Frief";
public string pluginName = "BDSM-Saddle";
...
#endregion
Such template code — including identical variable names, comment headers, and plugin metadata — is functionally required.
It does not qualify as protected intellectual property under either U.S. or EU copyright law.
It represents boilerplate, not creative authorship.
Code comments, variable naming conventions, and section formatting serve technical documentation purposes — not artistic expression — and therefore cannot be copyrighted.
Independent implementation
All of my functional logic and interaction systems were written independently from scratch.
While I learned general scripting principles from public tutorials (as most creators do),
I did not copy or import code directly from those sources.
Even the moderators’ own screenshots show that the only overlap lies in generic, framework-level syntax used by everyone.
The folder name “VamDeluxe,” cited in their post, was simply a leftover naming error — not reused code, not a license claim, and not evidence of infringement.
Misrepresentation and moderation conduct
The moderation team presented these technical similarities as “proof of copyright violation,”
while simultaneously closing public threads and preventing any opportunity for clarification.
This created a one-sided narrative that falsely implied guilt and undermined the ability to respond with technical evidence.
Publicly framing boilerplate structure and folder naming as “copied code” is both misleading and unprofessional.
My position and formal request
Because of the repeated misrepresentation and inconsistent enforcement,
I have issued a formal GDPR and copyright takedown request
requiring VaMHub (MeshVR, LLC, and affiliated staff)
to remove all of my content and associated data within 14 days.
I do not consent to further hosting, mirroring, or redistribution of my works by VaMHub or its operators.
To clarify:
✅ I acknowledge learning from public tutorials.
❌ I did not copy, reuse, or redistribute any copyrighted or proprietary code.
✅ My implementations follow VaM’s public scripting standards — not private or protected work.
❌ The “VamDeluxe” folder was an unintentional leftover, not reused code.
Final note
Accusing creators of copyright infringement over framework structure, variable names, or code comments is an overreach that harms, not protects, the community.
It discourages contribution, breeds mistrust, and undermines the collaborative spirit that made VaM successful in the first place.
— Frief
