From e151c6eb15e6e01b0a4ef79ca1417af35a4297cc Mon Sep 17 00:00:00 2001 From: smallmodel <15067410+smallmodel@users.noreply.github.com> Date: Mon, 9 Sep 2024 23:32:08 +0200 Subject: [PATCH] Update documentation --- docs/getting_started_running.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/getting_started_running.md b/docs/getting_started_running.md index 98170136..f1e32f7c 100644 --- a/docs/getting_started_running.md +++ b/docs/getting_started_running.md @@ -18,15 +18,17 @@ You can now start a local OpenMOHAA server or play on a server. ## User data location -The location of user data, like console logs, saves and config files can be found in different locations depending on the platform: +The location of user-writable data, like the console logfile, saves and configuration files can be found in different locations depending on the platform: - `%APPDATA%\openmohaa\` on Windows - `~/.openmohaa/` on Linux -This has two advantages: +This is by design since ioquake3 and has two advantages: - On a multi-user system, each user will have their own configuration file - It doesn't overwrite the existing MOHAA configuration in the MOHAA installation directory. +The location of user-writable data can be changed manually by setting the `fs_homepath` variable in the command-line argument. The value can be a relative path (relative to the current working directory) or an absolute path. + Note that the configuration file isn't created nor written automatically on a dedicated server (**omohaaded**). ## Playing with bots