Debug

or: The place where developers are allowed to break things (on purpose)

This section is for the Debug Mode of vanilla9.

If you are using the app normally, you can safely ignore this area.

But if you want to test things, develop features, or figure out why software sometimes behaves strangely, this is where it becomes interesting.

Or put differently:

This is the part of the software where developers say:
“Wait a second, let me check what is actually happening here.”

Debug Mode activates additional developer features.

These can, for example:

– display additional information
– expose internal system states
– make troubleshooting easier
– or show things normal users never need to see

The mode is activated using a secret debug key.

Think of it like a small cheat code for developers.

To activate Debug Mode you need a valid key.

The key is usually generated on the server and has a limited lifetime.

In the screenshot you can see:

– valid for 12 hours
– after that it automatically expires

This prevents debug features from staying active permanently.

Because running in debug mode is a bit like driving a car with the hood open:

Very useful for inspecting things.
Not necessarily meant for everyday driving.

If the key is valid, you can activate Debug Mode.

Once activated, the corresponding debug features become available.

The mode can also be turned off again at any time, usually via a toggle or button in the interface.

So do not worry. If you accidentally enter Debug Mode, the server will not immediately explode.
Hopefully.

The Debug section is meant for development, testing, and troubleshooting.

Normal users will rarely need anything here.

But if you want to see what is happening inside vanilla9, this is the place where we open the hood.

Or, in developer language:

“Don’t worry, I will just enable debug mode for a moment.”

(Things developers say right before they are still sitting here three hours later.)