Author Topic: Crash when i spawn  (Read 1565 times)

Okay, so i start my server i spawn in. I spawn in the sky.i falll when i hit the ground my screen tilts sideways and blockland crashes,

Post console log.

Why do people not read the stickied topics? Seriously?
We can't really find these issues simply without a console log (sometimes we can't find them in the log but it helps figure out what you should remove)

Sorry i'm new to the fourums, but how do i send a picture?

The topic also tells you how to post a console log (it's in the sticky thread). Before you post, there's "additional options" text, click it, and you can post your log from there from the "attach" option.

Do i take a screenshot of the log manually?
Or does it do it automatically?

Console log is located in your game folder. It's called console.log

From what it looks like you don't use steam, but I'll put both files anyways: do not run blockland at all during this
Documents/Blockland/console.log
Program Files (x86)/Steam/SteamApps/Common/Blockland/console.log

since you don't seem to understand, the console.log is a text file that contains useful information about what happened in your game before you crashed. The black box that always sits behind your blockland window is the console log, as it is being written by the game as it does things.

Ok...

i assume blg is blockland glass, but what is a heartbeat?

the console log doesnt show enough info; can you do a trace? basically, start the game, open up the console with ~, and type in and enter "trace(1);", then duplicate the crash. post the resulting console log

i assume blg is blockland glass, but what is a heartbeat?
It's when it authenticates to the Blockland Glass server. Much like Slayer's handshake but this heatbeat is a constant ping to the BLG servers.

So it's blockland glass? And i'll post a new console log when i get home.

So it's blockland glass? And i'll post a new console log when i get home.
Nobody said it was.
the console log doesnt show enough info; can you do a trace? basically, start the game, open up the console with ~, and type in and enter "trace(1);", then duplicate the crash. post the resulting console log

the console log doesn't show enough info because he didn't start his server when he ran BL, before posting the log.