TLDR

WebConsole lets you write and run Lua on a live DCS server from your browser with instant feedback. It lives in the NimbusPulse Control Panel and is available only through our endpoint. The in-game console comes from the community project WebConsole.lua. We built the NimbusPulse backend integration and the entire frontend.

Credit: WebConsole.lua by Actium. (Forum thread)

Introduction

Mission scripting and server operations often turn into a loop: edit, restart, test, repeat. WebConsole trims that loop to seconds. Open your server in the Control Panel, write Lua, press Execute, and see the result right away. It sits next to missions, players, and settings, so you stay in one place.

We use the community Lua console inside DCS. The NimbusPulse part is the secure endpoint, validation, history, and the full browser experience.

Why WebConsole

Fast iteration turns ideas into working missions. Try logic in the mission state, adjust values while the session is live, run diagnostics, and moderate without leaving the Control Panel. The loop becomes type, execute, inspect, adjust.

What you get

• Instant execution Run Lua on your DCS server and get immediate feedback.

• Focused editor Write code in a clean editor with Lua syntax highlighting.

• Execution history Review previous runs with their code, result, status, and timestamp.

• Built-in guard rails Execution is available only when the server is running and WebConsole is active.

Availability on NimbusPulse

WebConsole on NimbusPulse is only reachable through our Control Panel endpoint. The generic local socket from the standalone mod is not exposed on NimbusPulse. Every call is tied to your account, scoped to the server you own, and recorded in history.

Getting started

1. Create a server with WebConsole enabled, or add it to an existing server in the Control Panel.
2. Open the WebConsole tab on that server.
3. Write Lua in the editor.
4. Press Execute and review the result.
5. Open History to inspect previous runs and rerun useful snippets.

API access

If you want to automate WebConsole, use the NimbusPulse API. WebConsole is not exposed through the standalone local socket on NimbusPulse, so API access goes through the NimbusPulse endpoint.

You can find the full documentation here:

• NimbusPulse Docs
• WebConsole execute endpoint

Endpoint

POST /game_servers/{id}/mods/webconsole/execute
Authorization: Bearer <token>
Content-Type: application/json

Body

{ "code": "return 1 + 1" }

Refer to the API reference for the full request and response schema, authentication details, and any endpoint-specific notes.

Examples you can paste

Who is online right now

local players = {}
for _, id in ipairs(net.get_player_list()) do
  players[#players + 1] = net.get_player_info(id)
end
return players

Quick server sanity check

return {
  time = os.time(),
  mission = DCS.getMissionName()
}

Log a custom marker

env.info("NP WebConsole marker at " .. os.time())
return "logged"

Security notes

All runs go through NimbusPulse with account auth and per-instance ownership checks. We verify that the server is running and that WebConsole is active before any execution. The local socket of the standalone mod is not reachable on NimbusPulse. If you call the API, keep your token safe and only grant the roles that need execution access.

Good workflows

Server administration Apply live tweaks, pull diagnostics, manage players, and check status without restarts.

Mission development Experiment in the mission state, trigger events during a session, balance values while people are flying.

Education and training Show DCS API calls with immediate results. Good for onboarding and workshops.

What we built vs what we use

Community core WebConsole.lua by Actium provides the in-DCS console.

NimbusPulse work Control Panel frontend, secure endpoint, validation, execution history, and the user experience around it.

Tips

Use History to build a small library of repeatable snippets. Keep runs short and focused. Very large dumps can freeze the server while data is serialized. If you need to share a result, copy it from the JSON view or export from History.

Closing

WebConsole turns NimbusPulse into a real-time Lua workspace for DCS. It saves time, reduces context switching, and makes iteration feel immediate. Try it during your next session and see how much smoother your work becomes.