Relative paths clarification

Some paths are treated differently when aren't set to absolute:

Path	Relative to
mods_dir, -f and temp_dir	Current working directory.
.vmbrc folder (--rc)	--rc param is checked first and if set, the config file is found or created there. Otherwise, multiple paths are checked in the following order: -f param -> current working directory -> %userprofile% directory -> executable directory. If not found anywhere, a default config will be created in the executable directory.
template_dir and --template	Multiple paths are checked in the following order: -f param -> current working directory -> mods_dir config param -> %userprofile% directory -> executable directory.
Path to .cfg file (--cfg)	Each mod's directory.
Paths in .cfg files	Each mod's directory for vmb, but for uploader it is relative to the directory with the .cfg file.

You can use --cwd flag to force all paths which are relative to the executable's directory to be relative to the current working directory instead. You only need to use this flag if you're running vmb from the source code (via node.exe).