Hello,

i believe there are some issues with 4.0:
First: the scripts, for instance psclient:

#!/bin/bash
 
R=$PWD/$0
# this concats the current directory with the path of the script, resulting in something like
# /home/Pirx//opt/Planeshift/psclient
# this should probably read R=$0

R=${R%/*}
# this strips the last component of the path, now we are getting
# /home/Pirx//opt/Planeshift
# it think that should read "/opt/Planshift", one could also use $(dirname $0)

cd $R
# this obviously fails. it works if you do R=$0 above, or cd $(dirname $0)

chmod 770 psclient.bin
# this should not work for ordinary users, because the user playing the game
# should not have write access to the install directory
# the file should be made executable by the installer

export LD_LIBRARY_PATH=libs/:\$LD_LIBRARY_PATH
# ok, i would prefer that the game would use the system libraries,
# but that it should work this way too

exec ./psclient.bin $@
# ok

after fixing the scripts as described above i get:
$ /opt/PlaneShift/psclient
Your configuration files are in... /home/Pirx/.PlaneShift
DEBUG: Sound System Software Renderer Initializing...

planeshift.application.client:
  PlaneShift Steel Blue (0.4.00)
  This game uses Crystal Space Engine created by Jorrit and others
  1.2.0 [Unix-x86-GCC]
     315) LOG_ANY flag deactivated with no filter.
 ...
     319) All LOGS are off.
Mounting skin: /this/art/skins/default.zip
     432) <src/common/paws/pawsimagedrawable.cpp:56 PreparePixmap>
Speicherzugriffsfehler

If you melt 1 iron stock (weight 4.0) you get 10 molten iron (weight 40.0) which you can cast again in 1 iron stock (weight 4.0).

I second this.

Machine specific config belongs to /etc/planeshift/ and user config to ~/.planeshift/

Even on Windows you can do that now.

It would also have the advantage not to loose your config on reinstall.