In fact you are allowed to edit all files, but you are not allowed to publicly show any changes to them.
Beiträge von Dennis
-
-
Belstgut is a staff member, and his post is offical.
-
-
By not using a cracked server.
-
Those are errors that occur when the logfile can not be read, and this is the case if the path is wrong, g_logsync is not set to 2 or permissions are not set. As your path seems right, this error only occurs with gameranger, usually.
-
Zitat
sv_hostname\GameRanger\
?If its not GameRanger, i'm at the end with my knowledge. Everything should work.
Maybe one of the devs can help you further. -
I suspect GameRanger is the problem. Everything seems correct, but there were many reports,
that gameranger doesn't work. We do not support gameranger anyway. Try if it works like that with a normal server, if it does, gameranger is the problem. -
Then the path is still wrong. Check if the logfile you are referencing has content.
-
You can, but we can't guarantee it works and we will not give any support for problems related to cracked.
The error hints that you might have broken the syntax, by accidentally removing a " or a , or a }.
Redownload the mod, use replace the configs, and only edit the auto to the path of the logfile. -
We do not give support by TeamViewer or any other private means. I'm sorry.
-
1. Change it to the actual path, like the php path, and not to manual
2. Pay attention on the syntax, do only change the auto to the path, do not change anything else.
3. Your server seems cracked. We hate that. -
Zitat
"logfile" : "auto"
If auto doesn't work change it to the path to your games_mp.log of your cod server. -
No. You need to insert the correct config path into config.json / config.cfg.
-
If you can't execute commands, the path to your logfile is not correct.
-
Seems correct.
-
By installing and using the new php-version you downloaded. Change the path of php to the new php.exe
-
Your error is because your PHP-Version is below 5.4, but you need 5.4.
You can ignore the update message, this is due to a little mistake in the latest version.
If you can't execute commands, the path to your logfile is not correct. -
-
You are using a too old version, use 0.12 or the new beta files.
-
Check your logfile path.