Ludwig Editor

RedM Releases
,
1

ludwig_editor
ludwig_editor1920×1080 385 KB

:memo: Ludwig Editor

Edit Your Server Config Files — Without Leaving The Game

Having the trouble to either grant full backend Access or not have your staff edit Files on your Server?

LUDWIG_EDITOR puts a full code editor directly inside your RedM client. Whitelisted admins can open, edit, and save files on the fly: no file transfer, no context switching.

Links

:speech_balloon: Join my Discord
:shopping_cart: Buy on Tebex

:globe_showing_europe_africa: Supported Languages

  • :united_states: English

  • :germany: German

LanguageFile is open for you to edit it easily*

:rocket: Key Features

  • In-Game Code Editor A high quality Code IDE, running inside your RedM NUI — syntax highlighting, line numbers, find (Ctrl+F), and keyboard-native editing.

  • Lua Syntax Highlighting .lua and .json files are highlighted out of the box with full language support.

  • Instant Saving Press Ctrl+S or click Save. The file is written instantly, changes will apply after the next Resource Start.

  • Whitelist-Based Access Only IDs you explicitly trust in serverconfig.lua can open the editor. Everyone else gets flagged and logged to your Discord.

  • Per-File Whitelist You define exactly which files are editable. No file outside the whitelist can ever be opened or written, regardless of what the client sends.

  • Concurrency Lock Two admins cannot edit the same file at the same time. The second admin receives a notification and the file stays locked until released.

:pencil: Open to Edits

The following are not escrowed and can be freely customized:

  • AdminCheck Function — Swap in your own admin/permission logic

  • Discord Message Function — Adjust webhook formatting, targets, or disable entirely

  • Locale Files — Translate or tweak any UI string to your liking

A README with full setup instructions is included in the resource.

:gear: Configuration

-- Steam IDs allowed to open the editor
ServerConfig.Permissions = {
    ["steam:your_steam_id_here"] = true,
}
-- Files available in the editor menu
-- Value: { script = "resource_name", path = "relative/path/from/resource/root.lua" }
ServerConfig.FilesToEdit = {
    ["Housing Config"]  = { script = "bcc-housing",      path = "houseconfig.lua" },
    ["Markets Config"]  = { script = "ludwig_markets",   path = "config.lua" },
}

:hammer_and_wrench: Get Started in Seconds

Setting up Ludwig Editor is straightforward and keeps your server secure.

  1. Grant Access: Add add_filesystem_permission to your server.cfg for the resources you want to edit.
  2. Sync Authors: Ensure the author field in your fxmanifest.lua matches the editors author
  3. Go Live: Join the server, type /editor, and start building!

Usage

  1. Connect as a character whose Steam ID is in ServerConfig.Permissions
  2. Type /editor in chat
  3. Select a file from the menu
  4. Edit in the editor
  5. Ctrl+S or click Save to write — Escape or Close to discard

!This is an Escrowed Version of the Script!

Checklist

  • I have reviewed the latest version of the Releases rules.
  • I have included a detailed description of my work as described in the rules.
  • I have included a download link or a store link.
  • I have filled out the required information at the end of the topic

If you’re selling your resource, please include the following information at the end of your post:
Code is accessible No - see above
Subscription-based No
Lines (approximately) 22,034 (frontend included)
Requirements none
Support Yes
1 Like
2

How does this work when Sandboxing prevents resources from writing to files outside the current directory?

3

Just scroll down to HERE where you can read that if configured correctly the sandbox restrictions can be lowered so a resource can write into another Resources filesystem.

Thats also why

“A README with full setup instructions is included in the resource.”

4

Maybe something to consider putting here, or on a publicly viewable page, so people understand how much setup is required. Food for thought.

5

I’ve added the Setup section to the page! It’s actually just a single line in the server.cfg and a quick manifest edit, but you’re right—it’s better for people to see how simple it is before they buy. Cheers for the feedback.

1 Like