@meager fractal
Integrating obfuscation directly into the workshop upload process is exactly the kind of support server owners need from BI.
This isn't just about preventing complete reuploads of mods but protecting the content from being easily accessible and modified. When content is obfuscated upon upload, it shields the work from being directly downloaded and inspected, addressing a significant concern for creators who invest time and resources into their projects.
Here also an message that i already sent in this discussion:
"It's true that anything obfuscated can eventually be cracked by someone with enough time and malicious intent.
However, taking a page from FiveM's playbook shows that a middle ground is possible. In FiveM, when players join a server, the content downloaded to their hard drive is obfuscated. This doesn't make it impossible to access or steal the content, but it significantly increases the effort and skill required to do so, compared to simply joining a server and downloading all resources directly.
Years ago, FiveM faced similar issues with content theft among server owners, leading them to implement obfuscation. This move has, to a certain extent, mitigated the problem by adding a layer of difficulty for those intent on stealing content.
I believe a similar approach could be beneficial for the Arma community. If BI provided an option for modders to choose whether their mods should be obfuscated upon upload to the workshop, it could alleviate many concerns without requiring BI to manually check each mod. This would be a tool in the hands of the creators, giving them the choice to protect their work if they wish.
Of course, for those who prefer to share their work openly or under specific licenses, the current system of licenses and reporting would still apply. This isn't about restricting the sharing of content or learning from each other but about giving creators more control over the distribution and protection of their work.
"