Operation:Infiltration (IT'S DEAD, HOW NICE)

Poll

Would you donate?

Yes
6 (14.3%)
No
30 (71.4%)
Still deciding.
6 (14.3%)

Total Members Voted: 42

Author Topic: Operation:Infiltration (IT'S DEAD, HOW NICE)  (Read 49467 times)

I'm just saying that that is not the problem.
Yes it is! When I close an infevted server, lag on m own stops!
I'm not stating what is causing the usage to go to 25%. I am saying that the usage is 25%.

Yes it is! When I close an infevted server, lag on m own stops!
I'm not stating what is causing the usage to go to 25%. I am saying that the usage is 25%.
Probably not.
I will figure the real error out by tracing the console, checking the log and everything.

« Last Edit: August 07, 2012, 08:00:56 AM by ScratchTehEPICSpaceDude »

Oh my Lord, please don't start fighting again.
I don't want to. He just thinks the problem is something without checking. I want to trace the console and everything.

We restarted the server so that pacnet can check the server log, we should have this problem fixed soon.

2 problems found with console trace :


Major console spam :

Add-Ons/Script_AutoSaveLoad/dedisave.cs (1) : Unable to find object : '' attempting to call function 'getName'


and


AutoSaver saves too often, that too 30k bricks.

Ok I an fix the autosave from the preferences.
As for the other problem I don't know.

Suggestion : Make the autosaver save less often, remove it once the whole build is complete, and disable the AutoSaveLoad addon and just use /reloadbricks when you spawn in the server right after starting up.

Ok.
When is it going up again?

If you would like I can fix these errors quickly and then start it up.

Of course.
The better the experience the happier I am.

Fixing these major problems is not going to be quick.
The event loss may lie in the autosaver and autoloaders and stuff, but idk about the fake kill brick thingy.

Fixing these major problems is not going to be quick.
Nope.avi

Already fixed the lag issues and starting up to test if they are gone.