What is a code editor?
A code editor is software for reading and writing plain-text files such as source code and configuration. On the desktop, the popular choices are lightweight editors like Visual Studio Code, Sublime Text, and Notepad++, while full IDEs from companies like JetBrains add project management and debugging, and web-focused tools like Adobe's Dreamweaver add site management and live preview. What they all share is a comfortable, colored view of text that a basic notepad cannot give you. The editor on this page brings that core experience into your browser, so you can edit server files without downloading them first.
What is syntax highlighting?
Syntax highlighting is the coloring you see in a code editor: keywords, strings, numbers, and brackets each get their own color, so the structure of a file is obvious at a glance. It makes mistakes stand out, because a missing quote or an unclosed bracket is far easier to spot in color than in plain black text. This editor is built on CodeMirror, a widely used editor library, and it recognizes the common file formats you run into on a server.
What files will you edit on a server?
Most server configuration lives in a few text formats, and each has its own rules that the editor's highlighting is tuned to help you follow:
| Format | Used for | Looks like |
|---|---|---|
| key=value | server.properties | One setting per line |
| YAML (.yml) | Most plugin and server configs | Indented key: value blocks |
| TOML (.toml) | Many Forge mod configs | key = value grouped into sections |
| JSON | Whitelists, operator lists, data files | Brackets, quotes, and commas |
| Plain text | Log files | Text you read, not edit |
Editing YAML and JSON without breaking them
YAML and JSON are strict about structure. JSON needs every bracket and quote matched and commas in the right places, and a single wrong character in either can stop a plugin from loading or keep the server from starting, which is why the editor highlights the structure and why it helps to change one thing at a time.
YAML is whitespace-sensitive: the indentation is the structure, and mixing tabs with spaces is the single most common way to break a config. When in doubt, indent with spaces only, and never let a stray tab sneak in.
The browser editor vs a desktop editor
The browser editor is instant: you open a file, change it, and save, with no download or upload step, which makes it ideal for quick config tweaks. A desktop editor like VS Code is better when you are working across many files at once, need find-and-replace over a whole folder, or want extensions and version control. For running a game server, the browser editor covers the large majority of day-to-day edits.
Editing files safely
A broken config can stop your server, so a little care goes a long way. Take a backup before a significant change so you can roll back instantly. Keep the file's format intact, with matching quotes, brackets, and indentation, and change one setting at a time so you know the cause if a problem appears. Most configuration is read at startup, so save your edits and then restart the server for them to take effect.