The new Outfit Bag 2.0 script comes with a brand new custom preview system so you can see exactly how your saved outfits look before putting them on. You also have the ability to mix and match different parts of your outfits. Want to just change your headwear, or maybe your jacket? Outfit Bag 2.0 lets you do that with ease. 

Main features

Sharing your style has never been easier. Outfit Bag 2.0 retains the feature you loved from the original – the ability to make your outfit bag publicly accessible. Let your friends and other players try on your saved outfits. 

An additional new feature for this 2.0 release is the introduction of static outfit bags. Through the config file, you can set persistent outfit bags for your players to use. You can also restrict the use of the outfit bags to specific job types making it a great choice for uniformed roles such as police or EMS. 

The UI colour scheme is also easily customisable through the config so you can fit it to match your servers theme.

Outfit bag 2.0 is fully standalone, meaning that it requires absolutely no other resources to function.

Highlights

• Unique real-time preview system
• Application of full and partial outfits
• Target support as well as 3d text option
• Fully standalone
• Support for usable items for ESX and QBCore
• Automatic despawning of forgotten bags
• Customizable UI colors through config

Integrations

This resource works with any clothing system, but to ensure the outfits are saved upon relog, it has built-in integrations for the following systems:

• Illenium Appearance
• FiveM Appearance
• QB Clothing
• CodeM Appearance

FAQ

Do I need any additional resources to use the Outfit bag 2.0?

Absolutely not! This resource is fully standalone. The only exception is a framework to have usable items. When using the standalone mode, you can use our custom command to summon the bag

Do the outfits stay in the bag after a server restart?

Yes, all the outfits are saved in the database.

You mentioned Illenium and Fivem-appearance. Do I need these for the script to function?

No, these are outfit saving systems, when not using one of these, the only difference is that outfits applied through the outfit bag will be temporary (unless saved by an external system). Meaning that they will not be re-applied upon relog.

Can I edit the UI of the bag?

Yes, the html, css and javascript code are totally open for you to edit

Is the resource obfuscated?

Yes, most of it is obfuscated using Cfx Escrow. Although, just as always in our scripts. All code related to framework and potential (optional)dependencies is always public

What is the resource usage (resmon) with the Outfit Bag 2.0?

The resource usage is practically 0. The only time it can get higher is when the bag is open or the 3d text is being rendered

I have bought the old "Classic Outfit bag" script (aka 1.0). Do I have to pay the full price?

No, everyone who bought the old version gets an automatic 50% off on the new 2.0 release. Just login with the same Cfx account on our website to use it.

I have the "Classic Outfit bag" on my server already. Will upgrading wipe the outfits?

No, all the outfits you currently have will work flawlessly on the Outfit bag 2.0, with no additional installation/upgrading steps necessary

What's the difference between your old Outfit Bag and this one?

The original Outfit bag 1.0 is still available. This script has been re-written from the ground up. Due to the previous outfit bag script being nearly 3 years old at this point, it's quite dated.
Now whats new? Brand new UI, The preview system, Partial application of the outfits, Static outfit bags, available exports and debug features. Those are just the visible changes. Under the hood, this script has a completely rewritten logic, granting much better performance and stability.

Compatibility

STANDALONE

QBOX

QBCORE

ESX

VRP