Author: ONX, CanisterDog, Momo
Introducing our new doctors and vetirinary scrubs! This clothing set includes:
- Including identical garment options for male/female peds
- 7 base garment colors for doctors: SAMA - San Andreas Medical Authority
- 7 base garment colors for vets: SAACC - San Andreas Animal Care & Control
- 3-4 accent colors for both doctors/vets providing 26 options for both scrub types!
- Each set of scrubs has both short sleeve and long sleeve options
This new clothing release is a part of the ONX Emergency Clothing Pack
Previews
Note: Face accessories and hair displayed in promotional material not included, the custom faces are a part of our MP Freemode Ped Blendable Faces pack
FAQ:
The clothing isn’t visible or working on my server?
To use this as an add-on pack and stream custom clothing you’ll need to atleast have the Cfx.re Element Club Argentum membership via patreon.
|
|
| Assets are accessible |
Textures Only |
| Subscription-based |
Yes |
| Polygons (model and LOD) Top |
4,176 high, 1,288 med, 902 low |
| Polygons (model and LOD) Pants |
2,876 high, 1,164 med, 270 low |
| Texture size and amount |
1024x1024 max, 312 textures, 115MB total, 350KB each |
| Requirements & dependencies |
Cfx.re Argentum |
| Support |
Yes |
3 Likes
Please make sure to include the correct template in your topic
Thank you!
I’d pay the right amount to get it lifetime. I was so happy to see scrubs and then I saw it was a sub. Dang it.
1 Like
I noticed the new requirements after submitting my apologies! All updated, hopefully that should suffice.
Thanks!
I just purchased the pack only to realize that it’s a subscription. I would have liked to buy it permanently. It’s a shame because I won’t pay $25 per month for a clothing pack.
1 Like
yea idk why he never learns no one wants subscriptions
3 Likes
You need to fill in these values, it sounds like someone just made an accidental purchase because your template was incomplete.
Def wish it was a stand alone. I’m not a big fan of the PD clothing.
My apologies again, I had those portions filled out previously and pasted over with only the asset requirements, should all be in order now.
Apologies for the confusion. Feel free to message me with your tebex transaction id and any additional details for a full refund or follow the support guidelines in the package description or the readme in your downloaded resource.
We maintain this asset pack as a subscription because we frequently update it. Additionally, FiveM’s YMT limitations currently prevent us from encrypting assets via escrow for individual standalone clothing releases. This is due to the requirement that each file name must remain consistent. YMTs for clothing packs rely on the naming conventions of those encrypted assets, which would subsequently conflict across multiple packs. Furthermore, I believe the latest GTA build only supports up to 8 YMTs.
We would like to release standalone. However, peds/clothing do not work the same way maps and vehicles do. We’re currently limited due to how YMTs are handled for clothing so multiple standalones for our releases will very quickly cause issues for anyone that were to purchase multiple standalones.
Male and female take up 2 YMT slots, leaving 6 on the latest GTA build not including any custom clothing servers are likely already running. We would have to release non-escrow for people to add our clothing to their own YMTs by changing file names which at this time we are not willing to do.
Either that or we have all standalones share a single YMT with buffer slots and each standalone just fills into these slots however, this would leave huge gaps of empty clothing slots considering how most servers handle their clothing menus. Our clothing menu also prevents index shifting of outfits on updates and eliminates gaps so we may consider releasing this though most servers are pretty well established with their own clothing menus by now, it just depends on interest really.
I am also willing to hear out any suggestions and what people are willing to work with should we do some not so typical standalone releases.
Here’s an idea for that issue if I’m understanding it correctly.
Like how some map creators do it, allow for free-to-download YMTs that are combined?
For example how G&N has a GitHub repo for all their map data, merged into 1 resource to prevent conflicts.
I guess you could do something similar, setting up common combinations for YMT e.g:
- PD standalone
- EMS standalone
- PD & EMS combined
Unfortunately you would have to maintain at least 2 ymts when updating clothes, and that may be a pain in the ass, but I think it could work and allow for escrowing.
Resource structure would be something like this then:
- cfx_onx_pd_clothing (containing respective clothing pieces, no YMT)
- cfx_onx_ems_clothing (containing respective clothing pieces, no YMT)
- cfx_onx_clothing_data (containing by default pd & ems YMT, but optionals can be manually downloaded/selected in fxmanifest)
Hope that helps, or at least gives some inspiration for another solution.
Either way, love the pack and the work, and I’ll definitely be using this for my project!
This is something we’ve considered, but it again limits our standalone options. For each individual release—such as our upcoming Judge clothing and robes—they would have to be grouped into one of those existing packs, rather than being truly standalone.
This is similar to how we’re handling our upcoming vehicles pack, with a single metadata pack for all vehicles. This approach makes it as simple as drag and drop for each vehicle resource containing just the models, whether purchased as standalone or as part of a subscription. However, this method doesn’t translate as easily to clothing, as clothing items need to fit into preordained slots with no flexibility on categories without being wasteful.
1 Like
People don’t care, they just manage their way to pick up and renew their clothing packs. If yours is better than the PD they used to have, then the choice is easy. You’re missing out a LOT by not releasing standalone.
Or provide a replace option, if addons are too much.
There is always a way.
okay well that’s fair enough thank you for explaining it and ofc its completely valid just now we know the actual reason behind it.
thanks,
an escrowed replace option would be a whole different plane of issues some servers already replace clothing that might conflict with his clothing yes u can just rename shit manually ( unsure if that even works with escrowed im presuming it does) that takes ages and so it wouldn’t be a drag n drop resource which is a terrible selling point
Renaming is primarily why it’s an issue because you can’t do that. The file names for the models have to remain the same for escrow to work. If you could rename then it would also be less of an issue as you could create your own YMTs or add our clothing to existing YMTs and if we did replace then they would be locked to what we choose they would replace too which again is not ideal.
But that’s an issue only if we wanted to push for a replace option, which is not necessarily provided. As a server owner, I have bought quite a fair amount of lore friendly clothes package, that were add-on, and I just manage and mix with what I need at that moment or which creator fits the best in myh vision of clothes.
Add-on is OKAY. People manage. I’m not the only one begging for this to come out as an actual lifelong pack.
And I’m unsure why this has an impact on the YMTs actually? If it’s a sub or a lifetime, it’s still the same, we still have to manage about the number of YMT used on the server?
