PC Died on Hord Night because of a scrolling console I could not close with red text.

[Jermo]

I was almost at the end of a great hord night on top of a tall building at the top that I made my hideout for the night. I was killing away at zombies when all of sudden a console window half the size of my screen opened up with red text just none stop scrolling by saying the same thing over and over. I could hit the escape key to exit game but when I tried to hit close all the way to the right of my screen the close option would not work and the massive scrolling of text kept going. While this went on a Bird vulture was killing my character and no matter what I did I could not close the text to save myself from death. Once my Character died It let me close the box and the game went back to normal. WTF Big time???? I've played this game for over 5 years I've never ran into that issue ever. Is this a known bug? Was I in a glitched area on a tall broken up building in the town I'm camped in? I mean WTF? I died because the game seemed to auto kill me.

 

[OzHawkeye]

It happens when something goes wrong. I get it all the time when I'm modding something in and screwed something up. Why the console locks out player action, and the error just endlessly repeats is...well... unfortunate, but yeah, it does happen if something falls over.

 

[RantingMonkey]

We were having this problem. On nights 7 and 14 our game crashed as my buddy got attacked by vultures. He got the scrolling text and had to reboot the game to get past it. We got back in and he was dead.

Looks like it was a problem with vulture spit and is listed as a fix on the new build.

 

[Akrux]

Had the same problem and it happened a few times in a row. Always with vultures attacking.

I could do nothing but exit the game. However when I returned the horde night started fresh each time. Needless to say my base was wrecked.

 

[Roland]

Dealing with console errors is all part of the testing process. You should be aware that the experimental build is unfinished and buggy and those errors will come up. If you choose to opt-in to the experimental build then you have to accept the risk that your game can not only cause you to lose your life because of an error at the wrong time but it could even cause you to lose your entire save causing you to have to start over completely. The primary purpose of it is for development. Playing for fun is secondary. Of course you CAN play it for fun but it is at your own risk.

Only tell you this because of your WTF response. Hopefully now you know WTF is going on.

 

[grieferbastard]

Jam on the escape key until it lets you exit, then get back in.

 

[TSBX]

Alt+F4

 

[Kam R.]

Try typing "killall" when you get locked in the console on horde night. (In MP admin/ host has to do it, I think) Yes it's cheating at this point but you won't have to restart the game. Seen it mentioned somewhere else before that one of the Zs, possibly vultures/ radiated(?) vultures cause the lockdown.

 

[Guest]

Until the bug is fixed, you can prevent this from happening by setting the spawn chance for irradiated vultures on horde nights to 0%.

edit: bug seems to have been been fixed in the new build

 

[Jermo]

Dealing with console errors is all part of the testing process. You should be aware that the experimental build is unfinished and buggy and those errors will come up. If you choose to opt-in to the experimental build then you have to accept the risk that your game can not only cause you to lose your life because of an error at the wrong time but it could even cause you to lose your entire save causing you to have to start over completely. The primary purpose of it is for development. Playing for fun is secondary. Of course you CAN play it for fun but it is at your own risk.
Only tell you this because of your WTF response. Hopefully now you know WTF is going on.

Thank you Roland. Really my WTF was because I've never ran into that problem ever in this game. Matter fact I've only had one bad issue with this game before back in alpha 16. When I was playing lost power during a thunderstorm logged back in and my character started over from Lv 1 and not Lv 147 and I could not use nothing in my base cause my Lv was so low. I just have never had the console auto open up and die before.

 

[Vomkat]

I ran into a similar issue doing some .xml editing. It happens when an entity tries to attack an entity that it hasn't been told is a valid target, so it hits but it can't hit. My guess is the vulture needs to be given 'permission' to attack whatever it was attacking.