Dev Console

## Dev Console

A mod that aims to improve the modding experience by providing an ingame console, as well as a number of utilities.

Github repo: https://github.com/TaroEld/mod_dev_console

Download the zip and use the docs/readme.md for a more formatted readme, I don't wish to translate this to BBCode.

# How to install

Just copy the .zip into your data folder. This mod requires MSU. If you don't want the MSU requirement, there's an older version available on Nexus.

# Capabilities

The console can be shown in any state by pressing ctrl+g. It toggles between half-width and fullscreen with subsequent presses.\

The console screen three main elements: a textarea to enter commands, an output window, and a footer bar.\

In the textarea, you can enter any valid Squirrel or JavaScript syntax. The default language is Squirrel. To switch to JS, press the "Squirrel" footer button.\

You can run the command in two ways: while staying in the console window ("Run in console" or shift+enter), or after closing the console window ("Run" or shift+ctrl+enter). The latter can be necessary in some cases, for example to invoke events.\

The commands are evaluated using `compilestring(_input).call(this);` in SQ and `Function(_input)()` in JS.\

As these inputs are executed as functions, you will need to return a value if you want to print it (or use ::logInfo() or console.error(), of course): return 1+2;

The currently executed command, as well as any return values, are printed to the console.\

Furthermore, I have added the global functions `::logConsole` (SQ) and `logConsole` (JS) to print to the console.\

Finally, print statements by the game engine(s) (`::logInfo`, `::logWarning`, `::logError`, `console.error`) are also printed to the console.\

In JS, objects can generally be printed rather easily, either directly or by using `JSON.stringify`. For SQ, you can use the MSU function `::MSU. Log.printData` to print tables and such.

## Debug Keybinds

I've included a number of useful debug keybinds. They've been lifted from the unused ingame debug module, respectively the Debug Mod by VilainJoueur.\

Debug Keybinds are disabled by default. They can be enabled by toggling the `Enable debug keybinds` setting.\

To get a list of available keybinds, check the Mod Settings.

## Element Inspector

I've added a HTML element inpector based on a suggestion/idea by KFox#2537.

This allows you to look at elements below the cursor to see details such as the type, classes, and styling.

#### States

At this time it has 4 states, which can be toggled via ctrl+i (modsetting keybind):

- None: Disabled

- Simple: Type, Class

- Border: Simple plus renders a border around the current element

- Full: Adds CSS s