# Can you have scripts that are 'per project'?

**URL:** https://qa.fmod.com/t/can-you-have-scripts-that-are-per-project/23692
**Category:** FMOD Studio
**Tags:** studio-scripting-api
**Created:** [November 20, 2025, 11:41pm UTC](https://qa.fmod.com/t/can-you-have-scripts-that-are-per-project/23692 "2025-11-20T23:41:38Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![tom-bossa](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/tom-bossa/32/9307_2.png) [@tom-bossa](https://qa.fmod.com/u/tom-bossa)
#### Post date: [November 20, 2025, 11:41pm UTC](https://qa.fmod.com/t/can-you-have-scripts-that-are-per-project/23692/1 "2025-11-20T23:41:38Z")

</div>

I’m currently using fmod scripting api but for user scripts to show up it seems they must go in %localappdata% on a per machine level. When using source control and multiple develolpers it would be much nicer to have a script that’s only really valid for 1 project to be included in the project folder somehow. Is this at all possible?

Many thanks

---

<div class="post-metadata">

### Author: ![joseph](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/joseph/32/264_2.png) [@joseph](https://qa.fmod.com/u/joseph)
#### Post date: [November 26, 2025, 11:45pm UTC](https://qa.fmod.com/t/can-you-have-scripts-that-are-per-project/23692/2 "2025-11-26T23:45:03Z")

</div>

Yes, this is possible!

As detailed in the [FMOD Studio User Manual](https://www.fmod.com/docs/2.03/studio/scripting-terminal-reference.html#script-files), FMOD Studio actually looks for script files in three different locations.

- The **system scripts directory** is the one you’ve already discovered. It’s used for user-specific scripts, i.e.: for when there are multiple people who have accounts on the same computer, and they each have their own personal scripts:
  - Windows: `%localappdata%/FMOD Studio/Scripts`
  - Mac: `~/Library/Preferences/FMOD Studio/Scripts`
  - Linux: `~/.config/fmod-studio/Scripts`

- The **built-in scripts directory** is for scripts that are shared by all accounts using the same computer:
  - Windows: `%fmod_install_directory%/Scripts`
  - Mac: `%fmod_bundle%/Scripts`
  - Linux: `%fmod_install_directory%/Scripts`

- The **project scripts directory** is for scripts that are associated with a specific FMOD Studio project, and are shared by everyone working on that project:
  - `%project_root_directory%/Scripts`

Whenever you load a project in FMOD Studio, FMOD Studio automatically loads scripts from all three of these locations, so you can freely use all three of them in combination if you want.

In any case, it sounds like you want the **project scripts directory**. Just open your FMOD Studio project folder (i.e.: the folder that contains the .fspro file) and create a subfolder named “Scripts”. Then, put any script files you want to share inside that “Scripts” folder. If you do this while your FMOD Studio project is open, you will need to select “Scripts \> Reload” before you can use them in FMOD Studio, and you will need to save the project before you can submit them to your source control repository.

---

<div class="post-metadata">

### Author: ![tom-bossa](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/tom-bossa/32/9307_2.png) [@tom-bossa](https://qa.fmod.com/u/tom-bossa)
#### Post date: [November 28, 2025, 1:17pm UTC](https://qa.fmod.com/t/can-you-have-scripts-that-are-per-project/23692/3 "2025-11-28T13:17:33Z")

</div>

oh perfect! Just tried and worked great, I must of completely missed that when looking it up, sorry 😃

---

<div class="post-metadata">

### Author: ![dada\_da](https://avatars.discourse-cdn.com/v4/letter/d/ce73a5/32.png) [@dada\_da](https://qa.fmod.com/u/dada_da)
#### Post date: [December 6, 2025, 6:22pm UTC](https://qa.fmod.com/t/can-you-have-scripts-that-are-per-project/23692/4 "2025-12-06T18:22:53Z")

</div>

I am struggling to get the built-in scripts approach to work on OSX Sequoia.

I believe the suggested path no longer exists unless I am missing something:

- Mac: `~/Library/Preferences/FMOD Studio/Scripts`

If that’s true, where else should the scripts go to be available for all users and independent of the application itself?

Thanks!

---

<div class="post-metadata">

### Author: ![joseph](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/joseph/32/264_2.png) [@joseph](https://qa.fmod.com/u/joseph)
#### Post date: [December 8, 2025, 1:51am UTC](https://qa.fmod.com/t/can-you-have-scripts-that-are-per-project/23692/5 "2025-12-08T01:51:52Z")

</div>

> [@dada\_da](#):
>
> where else should the scripts go to be available for all users and independent of the application itself?

The **built-in scripts directory** is for scripts that are shared by all users on the same computer. On MacOS, the built-in scripts directory is `%fmod_bundle%/Scripts`

I’m not sure what you mean by “independent of the application itself.” An FMOD Studio script is a script that runs inside FMOD Studio, so it is impossible by definition for an FMOD Studio script to function independently of FMOD Studio.

---

<div class="post-metadata">

### Author: ![dada\_da](https://avatars.discourse-cdn.com/v4/letter/d/ce73a5/32.png) [@dada\_da](https://qa.fmod.com/u/dada_da)
#### Post date: [December 8, 2025, 6:53am UTC](https://qa.fmod.com/t/can-you-have-scripts-that-are-per-project/23692/6 "2025-12-08T06:53:59Z")

</div>

Sorry for my lack of clarity:  
I mean the path of the „system scripts“ you mentioned as the first in your list in this post does not seem to work.

---

<div class="post-metadata">

### Author: ![joseph](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/joseph/32/264_2.png) [@joseph](https://qa.fmod.com/u/joseph)
#### Post date: [December 15, 2025, 11:42pm UTC](https://qa.fmod.com/t/can-you-have-scripts-that-are-per-project/23692/7 "2025-12-15T23:42:23Z")

</div>

Hmm… You’re right, it doesn’t seem to be working. Thanks for the report; I’ve added this issue to our bug tracker.

Unfortunately, I am not aware of any simple workaround for this issue, so you will have to use the other two scripts directories until it is fixed.
