Clothing collections

[blackfirefly000]

Saves MP Ped clothes by collection instead of global ID to allow saved beds to be the same across various game builds. Primarily useful for servers using addon drawables. Includes support for legacy saves to preserve continuity.

Also updates CitizenFX.Core.Client API to 1.0.10230 to enable the use of the new natives.

Tested using b3095, 3258, and 3407 without issues.

[PassiveRolePlayer]

Hey im not sure how github works, but does the green tick mean that it has been added to vMenu ?

[SkylarPlayz348]

The green tick means it passed all the CI/CD tests

[SkylarPlayz348]

I'm just putting this out there but there is one problem and that is EUP by EUP Team on Patreon all of those are saver in addon for collections that already exist so if a server has EUP 9.7 and another has a future update of 9.15 which in this example hits the drawable limit for one collection let's say a new gta update 4000 which added 30 clothes to a collection well since in this scenario 9.15 works with 4000 but if I rolled back to 3570 or even 3095 those 30 slots aren't there so drawable lets say 100 on 3095 isn't the same as on this 4000 update. So the same problem exists regardless of collection size.

[TayMcKenzieNZ]

Regarding limits:

https://docs.gta.clothing/game-mechanics/game-limits-and-crashes

[blackfirefly000]

It has always been up to server owners to ensure they don’t exceed the ymt limit. This has not changed.

This does not intend to mitigate the effects of changes in drawable order in addon resources. If the creator of EUP, for example, changes the drawable order inside their resource between 9.7 and 9.15, there’s no feature that exists that can handle that and you need to have a conversation with the EUP team.

This is not intended to provide compatibility across different servers. Clothing compatibility across servers has always been poor and it is recommended to save peds specifically to each server. If two servers are using the same resource with the same drawable order, this will allow for saved peds to be the same, but this is a side effect, and not what this PR is intending to solve.

What this IS intended for is for servers using the same clothing resources (or updated ones with the same order) to be able to update from b3095 to b4000 for example. Provided the drawable limit is not reached, all saved peds will be the same across the update.

[blackfirefly000]

I'm just putting this out there but there is one problem and that is EUP by EUP Team on Patreon all of those are saver in addon for collections that already exist so if a server has EUP 9.7 and another has a future update of 9.15 which in this example hits the drawable limit for one collection let's say a new gta update 4000 which added 30 clothes to a collection well since in this scenario 9.15 works with 4000 but if I rolled back to 3570 or even 3095 those 30 slots aren't there so drawable lets say 100 on 3095 isn't the same as on this 4000 update. So the same problem exists regardless of collection size.

You can check out the following https://docs.fivem.net/docs/scripting-manual/using-new-game-features/collection-based-natives/ for more clarity on what clothing collections can and cannot do and the benefits of using them.

[SkylarPlayz348]

in my example this has nothing to do with ymts as EUP 9.7 adds to the existing collections

[blackfirefly000]

in my example this has nothing to do with ymts as EUP 9.7 adds to the existing collections

Provided the drawable order is the same it will still work as intended. If you update EUP and they use an addon ymt (which I would recommend they do) or they change the drawable order, it’s gonna be messed up either way. But like I said, this really isn’t intended to address changes caused by resource updates, but changes caused by title updates.

For example, drawable number 1 in addon resource 1 has a global number of 550 in b3095 and 600 in b3502. If you update from b3095 to b3052, as long as drawable number 1 in addon resource 1 is still the same, your saved ped will look the same.