Build and debug BeamNG.drive and BeamMP mods/resources using Lua. Use this skill whenever the user mentions BeamNG modding, BeamMP server plugins, `Resources/Server`, `Resources/Client`, `modScript.lua`, `extensions.load`, `MP.RegisterEvent`, `AddEventHandler`, or client/server event wiring.
Scanned 9/4/2026
Install to Claude Code
npx -y skills add NeverSight/skills_feed --skill beamng-mods --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Beamng Mods?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/neversight-beamng-mods)More formats (shields.io, HTML) on the badges page.
---
name: beamng-mods
description: Build and debug BeamNG.drive and BeamMP mods/resources using Lua. Use this skill whenever the user mentions BeamNG modding, BeamMP server plugins, `Resources/Server`, `Resources/Client`, `modScript.lua`, `extensions.load`, `MP.RegisterEvent`, `AddEventHandler`, or client/server event wiring.
source: local
license: MIT
---
# BeamNG + BeamMP Modding
Build, scaffold, and debug:
- BeamMP server plugins
- BeamMP client mods (`modScript.lua` + GE extension)
- BeamNG Lua extensions (`common/ge/vehicle`)
Keep responses concise and implementation-first. Prefer small working patches.
## First Decision
Choose one target before writing code:
1. `beammp-server`
2. `beammp-client`
3. `beamng-only`
If target is unclear, ask one short clarifying question.
## Progressive Loading
Load only what is needed.
For `beammp-server`:
- `references/layouts.md`
- `references/beammp-server-api.md`
- `examples/beammp-server-main.lua` (when scaffolding code)
For `beammp-client`:
- `references/layouts.md`
- `references/beammp-client-api.md`
- `examples/beammp-client-extension.lua`
- `examples/modScript.lua`
For `beamng-only`:
- `references/layouts.md`
- `references/beamng-extension-api.md`
- `examples/beamng-ge-extension.lua` (or adapt for common/vehicle VM)
## Core Rules
- Namespace custom events as `pluginName:eventName`.
- Use JSON payloads for client/server boundaries and validate inputs.
- Keep event handlers short; avoid long blocking loops/sleeps.
- Prefer one small, testable feature per iteration.
- If any local stubs are provided, treat them as helper hints only; prefer official docs on conflicts.
## Output Format
When implementing/scaffolding, include:
1. Target type (`beammp-server`, `beammp-client`, or `beamng-only`)
2. Final file tree
3. Code changes
4. Quick test steps
## Sources
Prefer official docs first:
- https://docs.beammp.com/scripting/server/latest-server-reference/
- https://docs.beammp.com/scripting/mod-reference/
- https://docs.beammp.com/guides/mod-creation/server/getting-started/
- https://docs.beamng.com/modding/programming/extensions/
- https://docs.beamng.com/modding/programming/virtualmachines/
Optional local sources (only if present in the current repo):
- BeamMP/BeamNG Lua stubs
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!