Sign in to follow this  
Followers 0
Spartan

killplayer Database Problem

2 posts in this topic

Hey gang,

I'm having trouble with my server, specifically when dead players respawn they are frequently getting trapped in a loop where their player is dead and a new player is not being added to the database. I've been researching and looking through my logs and I found this:

[04:50:28:501753 +00:-1] [Thread 5108] extDB2: SQL_CUSTOM_V2: Trace: UniqueID: 1 Input: killPlayer:184
[04:50:28:501753 +00:-1] [Thread 5108] extDB2: SQL_CUSTOM_V2: Error No Custom Call Not Found: Input String killPlayer:184
[04:50:28:501753 +00:-1] [Thread 5108] extDB2: SQL_CUSTOM_V2: Error No Custom Call Not Found: Callname killPlayer
[04:50:28:501753 +00:-1] [Thread 4200] extDB2: Output to Server: 

In this case, I was player 184. I think this is causing the problem, as I'm seeing this when other affected players are killed, but  I'm not sure why it's doing this. Any suggestions?

P.S. I also found this but not sure if it's relevant.

[04:50:43:498611 +00:-1] [Thread 4200] extDB2: Input from Server: 0:235664:hasAlivePlayer:MYGUID
[04:50:43:498611 +00:-1] [Thread 4200] extDB2: SQL_CUSTOM_V2: Trace: UniqueID: 1 Input: hasAlivePlayer:MYGUID
[04:50:43:565615 +00:-1] [Thread 4200] extDB2: SQL_CUSTOM_V2: Warning: Number of Output Options: 1, Number of SQL Columns: 0, this warning only exists in Debug Version. Its just to let you know of a possible mistake
[04:50:43:566615 +00:-1] [Thread 4200] extDB2: SQL_CUSTOM_V2: Trace: UniqueID: 1 Result: [1,[[true]]]

Any help would be much appreciated.

Share this post


Link to post
Share on other sites

Ok, my mistake. I feel really stupid.

I had an overwrite on MpKilled file for some custom stuff on my 0.9.3.5 server.

Somehow when I was going through the overwrites for the 0.9.4 server I used the old MpKilled overwrite file instead of pasting my stuff into the newly released file.

There is no killPlayer anymore, it's deletePlayer, and who knows what other changes were made to MpKilled. :)

So, yeah, that's not gonna work. Good news is I think I got it fixed.

Let this post stand as a testament to what happens when you do dumb things.

Share this post


Link to post
Share on other sites
Advertisement

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.