[2Lynk]

Hi there,
I am having a problem with writing and using plugins.Everytime I write a plugin, I do so on my own computer, when it is done I compile it and move to via FTP to my server, when my server then runs the plugin I get an error and I can see the plugin tries to call something that is on my PC...

The same thing happens when modding other plugins like Multi1v1 by Splewis. After my edits, I compile it, upload it and then the same type of error happens.
This is what I got after editing multi1v1.sp:
[SM] Call stack trace:
[SM][1] Line 864, C:\Users\admin\Projects\multi1v1_1.1.9\addons \sourcemod\scripting\multi1v1.sp::Event_OnPla yerDeath

Even though it runs on my server and not on my machine...


I have been trying to find a solution for a couple days now but to no avail. I could not find any awnsers online or on the forum here...

Any help is greatly appreciated!

[andi67]

That's not the complete error...

[2Lynk]

It is... Happens when someone leaves the server.
And it still leaves me with the question, why is it trying to load something on my C:\ drive even though its the server and I have not hard-coded a location in the code?
The only thing I have done is to open the .sp file, changed the version number, compiled it and moved it to my server and then it shows

[SM] Call stack trace:
[SM][1] Line 864, C:\Users\admin\Projects\multi1v1_1.1.9\addons \sourcemod\scripting\multi1v1.sp::Event_OnPla yerDeath

instead of

[SM] Call stack trace:
[SM][1] Line 864, ./scripting/multi1v1.sp::Event_OnPlayerDeath

[andi67]

Well first you can try to update your SM to the latest stable version. Secondly you can post your Code here and maybe someone here can help you to fix this...

[Peace-Maker]

The path shown in the error message is pointing to the source code location where the plugin was compiled from. It isn't used again after compilation. It's there to help you locate the source code to look at the reported line to fix the error.

As andi67 said, you're missing the actual error message which is printed right above the stack trace.

[2Lynk]

Originally Posted by Peace-Maker The path shown in the error message is pointing to the source code location where the plugin was compiled from. It isn't used again after compilation. It's there to help you locate the source code to look at the reported line to fix the error. As andi67 said, you're missing the actual error message which is printed right above the stack trace.

Ah, thanks a bunch! It had me really confused as to why it was calling that location...