Richard42: /* Where the heck are the files? */

2018-01-25T06:19:29Z

Where the heck are the files?

Richard42: Places where Mupen64Plus installs and/or searches for various files

2015-07-26T06:14:22Z

Places where Mupen64Plus installs and/or searches for various files

New page

== Where the heck are the files? ==

Due to the flexibility of Mupen64Plus and its cross-platform design, they could be just about anywhere! The quick-reference tables below gives the most likely locations for some common files. The remainder this wiki page gives the full details of where they could be.

==== Linux/OSX ====
{| class="wikitable"
|-
|'''File Type''' || '''Path'''
|-
|Config file || <code>~/.config/mupen64plus/</code>
|-
|Screenshots || <code>~/.local/share/mupen64plus/screenshot/</code>
|-
|Save states || <code>~/.local/share/mupen64plus/save/</code>
|}

==== Windows XP and Earlier ====
{| class="wikitable"
|-
|'''File Type''' || '''Path'''
|-
|Config file || <code>C:\Documents and Settings\your_user_name\Application Data\Mupen64Plus\</code>
|-
|Screenshots || <code>C:\Documents and Settings\your_user_name\Application Data\Mupen64Plus\screenshot\</code>
|-
|Save states || <code>C:\Documents and Settings\your_user_name\Application Data\Mupen64Plus\save\</code>
|}

==== Windows Vista and Newer ====

{| class="wikitable"
|-
|'''File Type''' || '''Path'''
|-
|Config file || <code>C:\Users\your_user_name\AppData\Roaming\Mupen64Plus\</code>
|-
|Screenshots || <code>C:\Users\your_user_name\AppData\Roaming\Mupen64Plus\screenshot\</code>
|-
|Save states || <code>C:\Users\your_user_name\AppData\Roaming\Mupen64Plus\save\</code>
|}

=== Front-End Specific Files ===

The front-end User Interface is responsible for finding the core libraries and plugins for startup. Each front-end may have its own method for finding these libraries. The Mupen64Plus-UI-Console front-end looks for these libraries in the following places, in order:

==== Core Library ====
# Path given by <code>--corelib</code> option
# Path given at compile time with <code>COREDIR</code> macro
# No path at all (allows the Operating System to search for the shared library)
# Current directory

==== Plugin Libraries====
The Mupen64Plus-UI-Console front-end looks through several directories in search of valid Mupen64Plus plugins. When it finds a directory containing plugins, it populates a list with all of the plugins found. Then, when loading plugins it only uses plugins from this list (found in one directory), unless the user specifies full plugin paths on the command line with the <code>--gfx</code>, <code>--audio</code>, <code>--rsp</code>, or <code>--input</code> options. The order in which directories are searched is:

# Path given by <code>--plugindir</code> option
# Path given by '''PluginDir''' parameter in Mupen64Plus config file
# (Unix-only) Path given at compile-time with <code>PLUGINDIR</code> macro
# (Unix-only) <code>/usr/local/lib/mupen64plus</code>
# (Unix-only) <code>/usr/lib/mupen64plus</code>
# Current Directory

=== Core-specific Files ===

These are files which are read and written by the core emulator.

==== Screenshots ====
# Path given by <code>--sshotdir</code> option (if using Mupen64Plus-UI-Console)
# Path given by '''ScreenshotPath''' parameter in Mupen64Plus config file
# ''User_Data''/screenshot/ (see OS-specific sections below)

==== Save states ====
# ''User_Data''/save/ (see OS-specific sections below)

=== Unix-specific Search Paths ===

The ''Shared_Data'' search paths work in the following way: each time a shared data file needs is requested (such as an .ini file, or font file), the emulator core looks through all of the ''Shared_Data'' paths in order to find the file.

''Shared_Data'':
# Path given by <code>--datadir</code> option (if using Mupen64Plus-UI-Console)
# Path given by '''SharedDataPath''' parameter in Mupen64Plus config file
# Path given at compile-time with <code>SHAREDIR</code> macro
# <code>/usr/local/share/mupen64plus</code>
# <code>/usr/share/mupen64plus</code>
# <code>./</code>

The ''User_Data'' and ''User_Config'' search paths work in the following way: at startup time, the emulator core looks through the list of directories to find one that exists. The first one found is used to read/write all ''User_Data'' or ''User_Config'' files, or if none exists, then the last one in the list is created.

''User_Data'':
# <code>$XDG_DATA_HOME/mupen64plus/</code>
# <code>$HOME/.local/share/mupen64plus/</code>

''User_Config'':
# Path given by <code>--configdir</code> option (if using Mupen64Plus-UI-Console)
# <code>$XDG_CONFIG_HOME/mupen64plus/</code>
# <code>$HOME/.config/mupen64plus/</code>

=== Windows-specific Search Paths ===

The ''Shared_Data'' search paths work in the following way: each time a shared data file needs is requested (such as an .ini file, or font file), the emulator core looks through all of the ''Shared_Data'' paths in order to find the file.

On Windows versions prior to Vista, the <code>$CSIDL_APPDATA</code> path is usually: <code>C:\Documents and Settings\your_user_name\Application Data</code>. On later versions of Windows, this path is usually: <code>C:\Users\your_user_name\AppData\Roaming</code>.

''Shared_Data'':
# Path given by <code>--datadir</code> option (if using Mupen64Plus-UI-Console)
# Path given by '''SharedDataPath''' parameter in Mupen64Plus config file
# <code>$CSIDL_APPDATA\Mupen64Plus\</code>

On Windows, the ''User_Data'' and ''User_Config'' directories are the same. These search paths work in the following way: at startup time, the emulator core looks through the list of directories to find one that exists. The first one found is used to read/write all ''User_Data'' or ''User_Config'' files, or if none exists, then the last one in the list is created.

''User_Data'':<br />
''User_Config'':
# Path given by <code>--configdir</code> option (if using Mupen64Plus-UI-Console)
# <code>$CSIDL_APPDATA\Mupen64Plus\</code>

@@ Line 3: / Line 3: @@
 Due to the flexibility of Mupen64Plus and its cross-platform design, they could be just about anywhere!  The quick-reference tables below gives the most likely locations for some common files. The remainder this wiki page gives the full details of where they could be.
-==== Linux/OSX ====
+==== OSX/MacOS (Mupen64Plus 2.5.1 and earlier) ====
 {| class="wikitable"
 |-
@@ Line 13: / Line 14: @@
 |-
 |Save states || <code>~/.local/share/mupen64plus/save/</code>
 |}
@@ Line 47: / Line 60: @@
 # Path given by <code>--corelib</code> option
 # Path given at compile time with <code>COREDIR</code> macro
 # No path at all (allows the Operating System to search for the shared library)
 # Current directory
@@ Line 55: / Line 69: @@
 # Path given by <code>--plugindir</code> option
 # Path given by '''PluginDir''' parameter in Mupen64Plus config file
 # (Unix-only) Path given at compile-time with <code>PLUGINDIR</code> macro
 # (Unix-only) <code>/usr/local/lib/mupen64plus</code>
@@ Line 79: / Line 94: @@
 # Path given by <code>--datadir</code> option (if using Mupen64Plus-UI-Console)
 # Path given by '''SharedDataPath''' parameter in Mupen64Plus config file
 # Path given at compile-time with <code>SHAREDIR</code> macro
-# <code>/usr/local/share/mupen64plus</code>
+# (Linux-only) <code>/usr/local/share/mupen64plus</code>
-# <code>/usr/share/mupen64plus</code>
+# (Linux-only) <code>/usr/share/mupen64plus</code>
 # <code>./</code>
-The ''User_Data'' and ''User_Config'' search paths work in the following way: at startup time, the emulator core looks through the list of directories to find one that exists.  The first one found is used to read/write all ''User_Data'' or ''User_Config'' files, or if none exists, then the last one in the list is created.
+On MacOS (with Mupen64Plus 2.6 and newer), the User Data and User Config directories are set to <code>~/Library/Application Support/Mupen64Plus/</code>.
 ''User_Data'':

FileLocations - Revision history

Richard42: /* Where the heck are the files? */

Richard42: Places where Mupen64Plus installs and/or searches for various files