24.08.2017, 13:43
Ahh... make another update on the crash detect I think the plugin is not the latest it crashes the server when it does that.
Next time post the whole serverlog don't chip anything away it would give us more details.
I have somethings that you might do..
If you create your logs, adminlogs, playerlogs, and load them during The gamemode start or when a player connects make sure that this logs already exist..
If you are using folders or as such for somethings such as player accounts if you're using y_ini or and file system functions then make sure the folder is also present...
Make sure that every plugin and and include matches
if your one of your include says that it uses this current version of a plugin from another include then make sure it matches..
Usually Crashdetect does the error since the old includes does not get updated to use the new revisioned one...
If you are using sscanf, streamer, and includes that calls out the crashdetect plugin then update them to the crashdetect plugin or the other way around. Just make sure they match correctly... Since some includes could not be updated because of the gamemode.
Lastly look for loops that loops through things... One wrong extra loop could cause a crash... also make sure to call the exact variable such as if you set your variable like this:
if you try to call all this variable through a for loop like this:
make sure that the count is equal to the variable or it will cause an error... Yes yes I understand the compiler will give a warning but sometimes the compiler does not give the warning back specially when there is too much to warn you it will just completely compile everything like nothing is wrong...
and since you are using a filterscript
make sure that not one of the calls in the filterscript go against the gamemode. such as
This will cause an error since both contradicts each other... But that code up there is just an example the code works you get full health but you still die in the end... or the other way around...
What I mean on top is those that really really contradicts like player actions or commands or something like that...
There's so many I can hint but since the serverlog is really chipped, that's one of the problem... So just try to do some of the above and when the symptoms persist... Ask for help...
Next time post the whole serverlog don't chip anything away it would give us more details.
I have somethings that you might do..
If you create your logs, adminlogs, playerlogs, and load them during The gamemode start or when a player connects make sure that this logs already exist..
If you are using folders or as such for somethings such as player accounts if you're using y_ini or and file system functions then make sure the folder is also present...
Make sure that every plugin and and include matches
if your one of your include says that it uses this current version of a plugin from another include then make sure it matches..
Usually Crashdetect does the error since the old includes does not get updated to use the new revisioned one...
If you are using sscanf, streamer, and includes that calls out the crashdetect plugin then update them to the crashdetect plugin or the other way around. Just make sure they match correctly... Since some includes could not be updated because of the gamemode.
Lastly look for loops that loops through things... One wrong extra loop could cause a crash... also make sure to call the exact variable such as if you set your variable like this:
PHP Code:
new LocalVariable[8];
PHP Code:
for(new i; i < 8; i++)
{
LocalVariable[i];
}
and since you are using a filterscript
make sure that not one of the calls in the filterscript go against the gamemode. such as
PHP Code:
//filterscript side
public OnPlayerStateChange(playerid, newstate, oldstate)
{
if(newstate == PLAYER_STATE_DRIVER && oldstate == PLAYER_STATE_ONFOOT)
{
SetPlayerHealth(playerid, 100.0);
}
return 1;
}
//gamemode side
public OnPlayerStateChange(playerid, newstate, oldstate)
{
if(newstate == PLAYER_STATE_DRIVER && oldstate == PLAYER_STATE_ONFOOT)
{
SetPlayerHealth(playerid, 0.0);
}
return 1;
}
What I mean on top is those that really really contradicts like player actions or commands or something like that...
There's so many I can hint but since the serverlog is really chipped, that's one of the problem... So just try to do some of the above and when the symptoms persist... Ask for help...