Yea, I’m having the same issue, even excluded all the metas
Great work. I hope JavaScript support is around the corner!
Alright so… ive tried about five times now to get it to work.
ive excluded files not supported using escrow_ignore… and it still is sitting at status: submitted
this is what is in my fxmanifest
fx_version 'adamant'
game 'gta5'
this_is_a_map 'yes'
data_file 'GTXD_PARENTING_DATA' 'gtxd.meta'
data_file 'DLC_ITYP_REQUEST' 'sadamine/stream/sadamine.ytyp'
escrow_ignore {
'gtxd.meta',
'stream/sadamine_collisions.ybn',
'stream/sadamine.ytyp',
'stream/sadamine.ymap',
'stream/sadamine_textures3.ytd',
'stream/sadamine_textures2.ytd',
'stream/sadamine_textures1.ytd'
}
files {
'gtxd.meta',
}
i think you missed adding lua54 'yes' to your manifest
is that only required if i am using lua scripts?
Ok so , as a small developer that already released some stuff either free or paid, i saw my scripts getting leaked or even getting sold (even at higher prices that my own) !
this is a very good way now to handle these type of problems
BUT
if i want to purchase some script, as a customer, i dont want it to be encrypted , i will always edit them so much no matter how perfect they are, i just love to play around with them and adopt them to my framework and add new things or even remove unused stuff…
i suggest any other developers to not encrypt main files
so anybody that is paying for it , can edit it as they like to (they paid for it at the end so, its kinda unfair for it to be encrypted)
BUT …
maybe have some of the functions encrypted in another file like a utility file…
i think this will be the best of both side
TLDR:
from a developer to other developers
Dont encrypt main files , so the buyer can modify it as they like without any problem (it would be also a lot easier for you, because you don’t have to edit them for each customer)
on the other hand , encrypt some functions (maybe some that don’t need any editing anyway)
(this is just my idea, not that i am saying everybody should do this, but i think this is better than just encrypting everything)
4 Likes
I tried few times and now I can see that my resource gets encrypted if there aren’t any “data_file” in fxmanifest. We have to wait when it’s gonna be compatible
Yeah but they need to be there for the resource to work properly.
Maybe I overlooked it, since I never released anything paid. But can you force people, besides some sort of a basic description, to state if their resources are encrypted?
I hate when they don’t do it, I ask them and suddenly they’re like “Oh, well, it is encrypted”. Just be upfront about it. Me and my community rarely buy anything encrypted, so naturally, we want to know what’s up.
I don’t think I’m asking for too much. Simply require statement about any encryption (yes or no, what type). If they don’t comply, unlist their resource.
Shout out to those that won’t be using this encryption though. I’ll keep my profit shares for you.
And to CFX, good job on this one. I understand why you didn’t really want it in the first place, but it feels like the best way due to your pro arguments.
8 Likes
Yes, exactly this!
I hope all the devs creating (paid) scripts will only use it like that.
It would be like 100x the support necessary if you would encrypt just all apart from e.g. a config file. Or people won’t get any support.
Me and the “myScripts” dev provide support for all our customers usually within a max. of two days and until everything works. If we were to encrypt everything, we simply wouldn’t have time to do anything else apart from support lol.
As for my paid scripts, I will only encrypt the functions that are essential for the script to work and will never need any editing.
e.g. database queries should never be encrypted, since people might want to change them for their framework.
1 Like
I have about 30 resources to encrypt and put them on Tebex, here’s an example of my file that won’t encrypt properly. Stuck at submitted for 2 days, resubmitted various times and won’t encrypt.
fx_version 'cerulean'
games {'gta5'}
files {
'*.meta',
}
escrow_ignore {
'stream/cbq/*.ytd',
'fxmanifest.lua',
'weaponcomponents.meta',
'weaponarchetypes.meta',
'weaponanimations.meta',
'weaponCBQ.meta',
'pedpersonality.meta'
}
data_file 'WEAPONCOMPONENTSINFO_FILE' 'weaponcomponents.meta'
data_file 'WEAPON_METADATA_FILE' 'weaponarchetypes.meta'
data_file 'WEAPON_ANIMATIONS_FILE' 'weaponanimations.meta'
data_file 'WEAPONINFO_FILE' 'weaponCBQ.meta'
data_file 'PED_PERSONALITY_FILE' 'pedpersonality.meta'
Are data_files currently not supported?
1 Like
Same issue here. Stuck at submitted even after excluding them from being encrypted.
Yeah, so as a small developer myself I have been trying to weigh up whether it is worth encrypting. But this, this is how I intend on doing most of my scripts from now on. Some stuff if I really don’t want it leaking then I will full encrypt, but most of my stuff will be done like this now.
Big up you for this idea!! Love it
3 Likes
We just released a fix for assets stuck at the processing stage.
Please use the re-upload button to try again.
1 Like
It seems to work now! One more question, should we exclude .meta files from escrow?
2 Likes
can we get an option to allow licensekey instead of the whole account?
1 Like
Exciting news.
1 Like
As answered in an earlier message, no, sorry.
It works now, awesome.
2 Likes
Great work!
1 Like