Debugging

Sometimes the game crashes after you've changed a .dat file or added new content and knowing why is obviously extremely helpful to solve the problem or reporting it as a bug.

To run the game with debugging output there are a few steps you'll have to go through.

WINDOWS

Press [Windows key]+[R], type in CMD and press enter.

The command prompt should appear.

Write 'cd' and the director of your .jar file, eg. "cd c:\delver".

Now, write "java -jar <delver.jar> where delver.jar is the name of the jar file, eg. "java -jar delver-alpha-7-11-12.jar" and then press enter.

This should launch the jar file and you'll be seeing messages in the command prompt window.

Now if the game crashes you'll see some kind of message, and by pressing the [up arrow key] in CMD you can easily launch the game again without having to go through the previous steps.

Running delver in CMD

Note: Because my Delver folder is on my P:\ hardrive I had to first write P: to switch to that drive.Edit

MAC (2 methods)

Open Terminal (under applications, utilities)

Command window should appear

Write 'java -jar '

Drag the .jar file onto the terminal window

Your window should look like the second picture

Hit enter and you will get a debug window

Console method

Open Console (under applications, utilities)

debug window should appear

Click "clear display" and run your .jar

Debug text will appear and tell whats missing or broken

To access the ingame test UI, open steam, right click on delver(must be latest beta), launch arguments, "debug=true", then press K ingame to open menu. L jumps you down a level, J up (dont use on first or last levels)