-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Looks as Combat is working but not full #13
Comments
Hello, This should be filled in the Combat repository, however, check syslog system file for combat-daemon output. Maybe you can also recompile it in simulation mode and check it from command line. For my experience I had some issues with mysql.lock file. Some put it in /tmp folder some in /var and maybe a symlink is needed. |
Hi Oh i read in your text my fault. Configure |
Hi So i have to |
Hi, no problem. :) You have to take a look at the Makefile, check if it suits your server and invoke it simply with a make command. |
Thx |
Hi i tried now to make the combat. wehre i can find the moves_combat app? |
i don't no wat i have to do. APP=./bin/moves_combat is it the outup of the make process or a file i don't have? or is it the path to moves_combat php in scheduler? |
ok not my day. sorry i searched to far away... |
so now after compiling i found a mistake i have. sh: 1: /var/stfc/combat/bin/moves_combat/var/stfc/combat/bin/moves_combat: not found is not full clear for me the path to set in config.srcipt.php. (daemon) sorry for this question. |
Hi
we have tried a combat situation.
The log from combat is arived and say my fleet is destroyed.
But my ship is still there.
Output from moves-log:
Starting Moves Scheduler...
entering file
"SELECT f.fleet_id, f.fleet_name, f.n_ships,
u.user_name AS owner_name
FROM (ship_fleets f)
INNER JOIN user u ON u.user_id = f.user_id
WHERE f.planet_id = 5855 AND
f.user_id = 11 AND
f.alert_phase = 2"
Executed Moves Scheduler (queries: 17) in 0.0158 secs
Finished Scheduler in 0.0243 secs
Executed Queries: 18
The text was updated successfully, but these errors were encountered: