# SickLockers {% @github-files/github-code-block %} ## Dependencies \~ Ox\_libs \~ Ox\_target \~ ESX ## Menu Options \~ Chief can access any inventory that has been created so long as they know the name or case number for the locker/evidence storage! \~ Lower rank officers can use this to store personal goods on them or if they go off duty they can leave their weapons in a safe place! \~ Deletion is in there but will not work at this time until i figure a smooth way to delete they inventories! If you have ideas PLEASE let me know! \~ You can use multiple locations with job based menus and rank based chief menus! \~ Each case has a unique id that can be pulled up from anywhere really! ## Utilization \~ Uses OX\_libs for context and Dialog \~ Uses OX\_Inventory for storage/lockers \~ Webhooks for Creating and Deleting Inventories! {% hint style="info" %} \~ it’s known that it seems like the stashs don’t stay. It’s more of an illusion as you will think you are creating a new one but it will open the one already made. Figuring a way to skip that. \~ removed stateBags as it seemed some issues but found a way to remove requirement for 1.9.2 \~ will be compatible with older esx versions out of box as it no longer uses state bags and I learned how to check for esx export and if nil use event. \~ job lockers for other jobs set in config \~ cleaner config with more options {% endhint %} {% hint style="warning" %} If you need help with anything or have ideas for this or other scripts please join the Discord with the link below! Discord also has other scripts I have made and will be adding more as we go on! Thank you all again! [Discord](https://discord.gg/YCsBGB58eg) {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.sickscripts.com/shared-framework/sicklockers.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.