Expanding on some issues posted in my other thread.
There is a low barrier for entry, no quality control, nor any assurance that paid assets are meeting the release guidelines or terms set by the Creator Platform License Agreement. I’ll also mention some general issues with releases that are still relevant to paid releases.
Quality
The release guidelines has a section on this, but many developers simply ignore it. There is a note about simple resources with “less than 50 lines”, which doesn’t really consider
- code formatting
- code complexity
- 1000 lines “config” files
- functional lines of code (ignoring whitespace, comments, etc.)
- framework boilerplate code (e.g. login event, logout event, job update event, etc.)
Encryption (asset protection)
The quality of code cannot be verified by users until an actual issue occurs, and then there is no guarantee of improvements, bug fixes, etc. Questionable and sometimes exploitable code is able to hide behind encryption and customers have no way to know until an exploit becomes common knowledge.
Free resources cannot be encrypted or obfuscated, and MUST be under an open-source or minimally restrictive source-available license; this frequently pushes developers to sell something simple because of concerns about the content being stolen and resold.
“Open source” releases
People frequently advertise their assets as “open-source” despite not meeting the open source definition, a key part of which being the permission to redistribute, modify, adapt, etc.
ULTRA DELUXE EDITION
The state of gaming is nicely replicated on the FiveM platform by its many “talented” (see greedy) developers. Rather than including an unencrypted file to setup events or exports so you can freely use any framework, you are often forced into buying different versions for ESX, QBCore, or whatever.
Even worse is the sale of an “open-source” version of a resource for twice the price as the encrypted version. Asset protection was added to protect developers from having their assets stolen and redistributed, but is instead used to justify a higher price point for accessing the source code.
ChatGPT
Introducing PixelVision™. Some 50 billboard resources, with their release threads including seven short paragraphs of AI-generated text - and somehow this isn’t mass-reported as spam and delisted!
Asset theft, copyright infringement, and licensing violations
Feel free to look through Mr PixelVision™’s topics for such examples.
There are many blatantly obvious examples, and reporting them often results in no action being taken, or a single thread out of dozens being delisted. Many releases import assets from other games (like The Sims) or the Unreal Engine Marketplace; delisting doesn’t even do much because those assets will stay on Tebex indefinitely, unless they receive a DMCA from the copyright (or trademark or whatever) holder.
Even when somebody has multiple releases removed they aren’t blacklisted from the platform and will continue to resell stolen assets, despite the PLA stating:
6.3. Repeat Infringer Policy. Repeated violation of the Creator PLA by infringing our intellectual property rights or the rights of third-parties is subject to the repeat infringer policy set out in the Rockstar TOS.
In accordance with the DMCA and other applicable law, the Company has adopted a policy of terminating, in appropriate circumstances and at Company’s sole discretion, registered accounts deemed to be repeat infringers. The Company may also at its sole discretion limit access to the Online Services and/or terminate the account of anyone who infringes any intellectual property rights of others, whether or not there is any repeat infringement.
I don’t need to talk about the abuse of open-source releases again.
Other blatant violations of the PLA
Can I mention MenanAk47 again? He still has his Patreon up with 557 members, has been DMCA’d multiple times for redistributing stolen content or violating licenses. Before double dipping by releasing on Tebex he was earning something like $10,000 monthly for content he did not create, employing tactics such as code obfuscation, remote loading, and ip locking.