> ## Documentation Index
> Fetch the complete documentation index at: https://lationscripts.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Money Laundering - FAQs

> Solutions to frequently asked questions

<AccordionGroup>
  <Accordion title="When I enter the money washing warehouse, it's empty inside with no washing machines">
    This simply means you are currently using an outdated version of `bob74_ipl` and must update to the [latest](https://github.com/Bob74/bob74_ipl/releases/latest). It is recommended to completely delete your old `bob74_ipl` resource and download fresh and perform a full server restart after install.
  </Accordion>

  <Accordion title="When I try to do a money washing contract it says 'You don't have enough money on you' but I have the money in my inventory">
    This is a common misconfiguration issue. The solution depends on which framework you are using.

    If you are on ESX, the most common issue is failing to update your dirty money item name in the config. By default, the script is configured to use "markedbills", which is qb-core specific and won't work with ESX. To fix this, open `lation_laundering/config.lua` and find the `Config.Levels` section, which is typically around line 315. Inside this section you'll find multiple sections each within a bracket such as `[1]`, `[2]`, etc, each with their own `dirtyMoney` variable. If it says `markedbills`, update every section to the spawn name of your dirty money. On ESX, this is typically `black_money`.

    If you are on qb-core, the issue is usually a misconfiguration inside the `Config.QBCore` section in `lation_laundering/config.lua`. This section is preconfigured to work with the standard `markedbills` item provided by qb-core which includes a "worth" metadata value being attached. If you use `markedbills` and are receiving the alert mentioned above, then it is possible you are using `markedbills` as a single item where x1 `markedbills` is considered worth \$1 dirty. If that is the case, you must set the `metadata` section to `false` inside `Config.QBCore`. If you use any other item besides markedbills, then you must find the `Config.Levels` section which is typically around line 315. Inside this section you'll find multiple sections each within a bracket such as `[1]`, `[2]`, etc, each with their own `dirtyMoney` variable. Update every section to the spawn name of your specific dirty money item.

    Finally, if you are on qbox then the issue could be two different things. The first thing to figure out is, what dirty money item are you using in your server? If you are using `black_money` (or any item that is **NOT** `markedbills`) as your dirty money item then you must go to the `Config.Levels` section inside `lation_laundering/config.lua` (*approximately around line 315*). In this section you'll find multiple sections each within a bracket such as `[1]`, `[2]`, etc, each with their own `dirtyMoney` variable. Update each section to the correct spawn name of your dirty money. If you DO use `markedbills` as your dirty money, then you simply need to go to the `Config.QBCore` section of the config and set the `metadata` option to `false`.

    <Note>
      If you are still having trouble or do not understand the instructions explained above, please reach out to us and we will do our best to help you!
    </Note>
  </Accordion>

  <Accordion title="My question or issue isn't listed here">
    Sorry about that! Please reach out to us on [**Discord**](https://discord.gg/9EbY4nM5uu) or via email at [**support@lationscripts.com**](mailto:support@lationscripts.com) regarding your issue.
  </Accordion>
</AccordionGroup>

<Note>
  When working with, testing, or tweaking this resource; do not restart the script! To properly restart this resource you first must `stop lation_laundering` then `ensure lation_laundering`. Failure to do so can cause issues, errors, and unexpected behavior.
</Note>