Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

You know you can go to your settings and activate ‘Prefer Markdown input where available’.

Then you will be able to use the triple back-ticks (```) to enclose codes, tracebacks, errors, etc.
Like:

```
SCRIPT ERROR: Invalid get index 'L59L1  21' (on base: 'Dictionary').

   at: update (res://gui_modules/Exploration/Scripts/room.gd:24) - Invalid get index 'L59L1  21' (on base: 'Dictionary').

SCRIPT ERROR: Invalid get index 'L59L1  22' (on base: 'Dictionary').

   at: update (res://gui_modules/Exploration/Scripts/room.gd:24) - Invalid get index 'L59L1  22' (on base: 'Dictionary').
```

That will give :

SCRIPT ERROR: Invalid get index 'L59L1  21' (on base: 'Dictionary').

   at: update (res://gui_modules/Exploration/Scripts/room.gd:24) - Invalid get index 'L59L1  21' (on base: 'Dictionary').

SCRIPT ERROR: Invalid get index 'L59L1  22' (on base: 'Dictionary').

   at: update (res://gui_modules/Exploration/Scripts/room.gd:24) - Invalid get index 'L59L1  22' (on base: 'Dictionary').

Isn’t that better to read?


Edit : Or you can also click ‘’ (that is the Format button) then ‘Code’ when not using Markdown.