- Fix the password problem so passwords are actually checked.
- Change some default options like SAVE_HOMEDIR, XPM_PIX (you hade
the port requiring xpm but CF wasn't configured to link it in),
ForceCCOPTIONS, EXPLORE_MODE, etc.
- Remove the empty ${CFDIR}/lib/shutdown from the Makefile and the
PLIST. This file just causes the program to exit without saying
why until the user manually removes the file.
- Fix "crossfire -o" to call uname correctly.
- Set logfile to be line buffered (instead of block buffered) since they
hardly ever call fflush(3).
Submitted by: Dave Chapeskie <dchapes@golden.net>
Ok, I found the problem.. the artifact code assigns a level value
to artifacts with kind "Berserkergang". The specialweapon/apply
code, when it finds a weapon with a "level" immediately compares
the title field to the weilder's name. If they dont match, it can't
be used.
I created a patch to remove the level designation from the artifact
code since other named weaopns (cf "glamdri") dont have a level
assigned.
B) From: Klaus Elsbernd <elsbernd@dfki.uni-kl.de>
In version 0.92.8 is a bug in the inventory-unlock-code, which
prevents unlocking.
C) From: myself
make post-install target modified in Makefile, *$*HOME was eaten
up by 'make' and displayed nonsense. Tell player to create the players
dir in his login directory.
1) get experience points if you use skills
2) don't crash if player logs in with 2 skills enabled
3) cleaned up PLIST (removed 2 player characters of mine
which aren't part of the distribution)
crossfire is a multiplayer graphical arcade and adventure game made for
X-Windows. It contains elements of various famous games like nethack and
moria. There are different quests to solve, many maps make the game really
interesting. Nice sound capabilities via rplay. Different players can form
a team over network. Treasure and experience points will be shared equally
among the players of a team.
Could please someone try to fix the password authentication ?!
In server/main.c the function check_passwd doesn't work properly.
I made a workaround returning always ok (1) here and marked it as
UGLY_PASSWORD_HACK...
