Please help me. I am having this issue with the private server.
You fucked something up.
Originally Posted by Kushala Daora
You fucked something up.
Any ideas on how to fix or what is causing this?
Originally Posted by Kushala Daora
You fucked something up.
ayeee I was going to say the same.
Originally Posted by Chase
Any ideas on how to fix or what is causing this?
Yeah, it's probably a hardware problem.
Yep something is sure damn fucked up there
You guys aren't really answering his question, I'm sure he already knows something is fucked up, the question is what is fucked up and how to fix it...
give some details please, like how much ram was used, how much ram do you have, which source, did you edit it, a picture of your wserver folder, etc. showing that error only wont get anyone much further
How much ram does your VPS have?
I'm guessing 1 or 2 GB
Originally Posted by Chase
Please help me. I am having this issue with the private server.
That's from a null pointer being accessed that was somehow not being caught by the CLR, which is interesting to say the least. Most people on this thread seem to have no idea what they're talking about - so ignore those people. The suggested low ram could be the cause I guess but I have my doubts, you would be getting a different error for that idealy. Have you made any source changes or is this a stock source you downloaded and compiled for the first time?
Originally Posted by krazyshank
That's from a null pointer being accessed that was somehow not being caught by the CLR, which is interesting to say the least. Most people on this thread seem to have no idea what they're talking about - so ignore those people. The suggested low ram could be the cause I guess but I have my doubts, you would be getting a different error for that idealy. Have you made any source changes or is this a stock source you downloaded and compiled for the first time?
Thank you for being the first one to contribute something helpful<3 | I got the source for another member of MPGH, he says it was just Phoenix Source with higher drop rates and custom pets. I have 2gb of ram on my VPS. If it is the source, is there anyway I can install a clean version of Phoenix source and save my player data? Thanks so much. Chase
Originally Posted by Chase
Thank you for being the first one to contribute something helpful<3 | I got the source for another member of MPGH, he says it was just Phoenix Source with higher drop rates and custom pets. I have 2gb of ram on my VPS. If it is the source, is there anyway I can install a clean version of Phoenix source and save my player data? Thanks so much. Chase
There will be no difference, if it is a clean phoenix like he said. Anyways why cant you just change drop rates or add pets. Its beyond easy....
Originally Posted by Chase
Thank you for being the first one to contribute something helpful<3 | I got the source for another member of MPGH, he says it was just Phoenix Source with higher drop rates and custom pets. I have 2gb of ram on my VPS. If it is the source, is there anyway I can install a clean version of Phoenix source and save my player data? Thanks so much. Chase
My question was asking how much ram you had...
But if you got your source from somebody else, it shouldn't make too much difference unless they did something to make you lose so much memory on your server that is uses 101% of your memory
In that case, I would recommend you to use the cleaner version
I gave him the source. I ended up setting it up for him. It's a clean Pheonix Source. It's a problem with every pheonix source I get, clean or not. After a certain time/something happens, the server.exe gets a error that crashes the wserver.exe, and then the restarter tries to restart the wserver.exe but it keeps crashing, until it shows this error. I believe I fixed it by restarting the server.exe with the wserver.exe.
- - - Updated - - -
@Prince Zuko
Btw bro, you finish up the Updater? I haven't seen it sent back in skype.
Alright, so here is the new 'shebang' I am just changing to a different source. Thanks for all the help on this issue.