Object reference not set to an instance of an object.

Suminagashi said:
I had this issue crop up twice on a private multiplayer server with some friends. Here is the thing: the console error spam happened during the week before the latest update to 19.1. The server was created on A19 (b180) and the errors happened on that very same version. For reference I had detailed the situation in a Steam post merely trying to find a possible solution to continue using electric fences. I'm not quite sure what the problem could be if it isn't tied strictly to continuing an old save, but I wish you guys the best of luck in getting this one resolved.
Click to expand...
So did it happen with a clean. new 19.1 build?

 
Jugginator said:
So did it happen with a clean. new 19.1 build?
Click to expand...
As of yesterday we were still playing the same game world as before. It's just that we stopped using electric fence posts for horde nights shortly before the 19.1 update to avoid the crippling bug happening (still had some fence posts around the home base but never had a problem with them). Coincidentally, it looks like our group is keen on starting a new game soon, so I will be sure to push to try out electric fence posts again in that one and let you know if we encounter any more issues with them!

 
Jugginator said:
Update: so far I can only confirm this with electrical wiring to fence posts done in a continued world/save from a previous build. Delete power.dat and the backup from your saved folder (will delete all wiring done, caution) or start a new save. That worked in 2/2 cases, one on a hosted-server with the same issue and another was on a test world I did to repro the issue.
Click to expand...
So I'm not sure if this is a new development but thought I would tell you just in case it helped out your tests.  Whenever a zombie walks in to that section of the fence I get the error to pop up but we noticed my wife doesn't.  She gets the error on a different section.  We just thought it was strange.

 
Sjustus548 said:
So I'm not sure if this is a new development but thought I would tell you just in case it helped out your tests.  Whenever a zombie walks in to that section of the fence I get the error to pop up but we noticed my wife doesn't.  She gets the error on a different section.  We just thought it was strange.
Click to expand...
Yeah that's another issue  related to old save. That was one of the issues I solved in the hosted-server by deleting power.dat.  I have yet to see it in a clean game, but I plan on hooking like 50 or 100 fence posts in various configs and running horde nights at it for a while

 
Big recommendation if your use electric fence go there and delete your server file before launching the game:

for windows : %localdata%/7DaysToDie\SavesLocal\ 
for linux ~/.local/7DayToDie/SavesLocal/

find the correct server folder and delete it , this will force the redownload of t he map content when your reconnect , , I tried and it worked

if you want you can delete everything . this folder content only files from server which can be redownloaded , password for server is not in this folder so don't be scary to lost it it's remaing after , also if a dev can tell to us how to prevent the console to popup to prevent unfunny moment, mostly in raid. Thanks

 
Suminagashi said:
As of yesterday we were still playing the same game world as before. It's just that we stopped using electric fence posts for horde nights shortly before the 19.1 update to avoid the crippling bug happening (still had some fence posts around the home base but never had a problem with them). Coincidentally, it looks like our group is keen on starting a new game soon, so I will be sure to push to try out electric fence posts again in that one and let you know if we encounter any more issues with them!
Click to expand...
We've been playing in a new world of 19.1 for a while and have done several horde nights using electric fences without anyone in our group of five getting the error messages from them. Admittedly we aren't using very many fence posts this time around but I thought I'd at least give an update that we've encountered no issues with the newer world. Still no idea why we had the problem in 19.0 before 19.1 dropped 'cause I don't think 19.1's patch notes actually said anything about fixing it, but whatever. I'm just glad we've been able to make use of electric fences without someone getting the shaft. We're probably going to start anew once more after the next stable update but I may try to persuade my friends to do one last horde night before a server wipe just to see if we get any errors from the fences after updating.

 
Wouldn't you know it, horde night of day 175 was giving me the error spam once again. I don't understand why it's been fine up until this point, then out of nowhere rears its ugly head again. Two other players were present and they were fine; it was only me with the console taken hostage. Please let me know if there's any pertinent details to provide.

 
I believe this is the right file. Bear in mind, looking through it the first 1/6 or so is irrelevant stuff from a single player game before joining the multiplayer server. The actual error messages start to appear maybe 2/5 into it, or nearly halfway, and is easy enough to locate using Ctrl + F and searching for NullReferenceException. The server is now using some mods and custom things but we were using no mods back when this bug first surfaced for us on a previous 19.0 server so I don't believe there is any correlation there.

View attachment output_log__2020-10-17__16-06-17.txt

 
For the electric fence errors I think the only fix is to delete the "power.dat" file from the server, which will remove all the wiring connections.

They'll have to be redone.

You also have a ton of failed prefab loads, which is something you'd need to discuss with the server manager. They are loading prefabs in the

world that you do not have.

 
Beelzybub said:
For the electric fence errors I think the only fix is to delete the "power.dat" file from the server, which will remove all the wiring connections.

They'll have to be redone.

You also have a ton of failed prefab loads, which is something you'd need to discuss with the server manager. They are loading prefabs in the

world that you do not have.
Click to expand...
Thank you. I will relay the message. However, I'm unsure if we'll be deleting that file because 1. it would be a pain in the rear re-wiring everything and 2. I imagine that's only a temporary fix considering we've had this same problem happen on two different worlds (hosted on two different dedicated servers, mind you).

As for the failed prefab loads, yeah I saw that too and rolled my eyes. I think next time we won't be trying out player-made POIs because most of them are pure garbage anyway from what we've seen.

 
Well I was going to just edit my previous comment to avoid spamming/bumping the thread, but after some confusion as to how I even do that, followed by some research, I guess that's not possible anymore. Anyway, kind of inconvenient but that's neither here nor there.

Beelzybub said:
For the electric fence errors I think the only fix is to delete the "power.dat" file from the server, which will remove all the wiring connections.

They'll have to be redone.
Click to expand...
What I wanted to say is that my server admin decided to try deleting power.dat anyway, which is fair since he's the one who did the wiring this time around anyway. It's a really good thing he made a backup of that file first, however, or we'd be pretty miffed right now. In the future, when giving such advice, please be aware that deleting power.dat doesn't merely remove wiring, but also completely deletes any Engines/Batteries/Solar Cells placed inside power banks. Losing a bunch of Quality 6 Solar Cells would be awful so I'd say that first removing items from power banks would be a pretty significant disclaimer that should be mentioned on top of the minor inconvenience of merely having to rewire everything.

 
You must log in or register to reply here.
Back
Top