User profiles disabled: Difference between revisions
Jump to navigation
Jump to search
Doom64hunter (talk | contribs) Create documentation for user_profiles_disabled file (I don't believe this exists yet?) |
Doom64hunter (talk | contribs) usecwd != user_profiles_disabled |
||
| Line 3: | Line 3: | ||
This includes config files, screenshots, saves, the autoload directory and texture cache files. It also affects the commands [[readarrayfromfile]] and [[writearraytofile]], which would normally also read/write data from/to the profile directory. | This includes config files, screenshots, saves, the autoload directory and texture cache files. It also affects the commands [[readarrayfromfile]] and [[writearraytofile]], which would normally also read/write data from/to the profile directory. | ||
The presence of <code>user_profiles_disabled</code> is | The presence of <code>user_profiles_disabled</code> is similar to setting the launch parameter <code>-usecwd</code>, however, the latter parameter comes with additional effects. | ||
Latest revision as of 11:12, 29 May 2023
If an empty file with the name user_profiles_disabled is placed in the eduke32 base directory, the game will use this directory instead of Appdata or /home/user/.config/eduke32 to store user data.
This includes config files, screenshots, saves, the autoload directory and texture cache files. It also affects the commands readarrayfromfile and writearraytofile, which would normally also read/write data from/to the profile directory.
The presence of user_profiles_disabled is similar to setting the launch parameter -usecwd, however, the latter parameter comes with additional effects.