FiveM Player Interaction Scripts
Budget: $50 – $0 USD
I’m building out a FiveM server and need a skilled scripter to create custom gameplay scripts focused on player-to-player interaction. In practical terms, I want lightweight, well-structured Lua (or C# if you prefer) resources that plug straight into my existing framework and let players:
• Interact directly with one another (e.g., request/accept trades, give or receive items, share cash).
• Perform simple cooperative actions (carry, escort, drag, or seat-share).
• Trigger contextual animations or chat prompts tied to those actions.
• Respect server-side permissions and anti-cheat safeguards.
Key expectations
• Code must follow FiveM best practices—event-driven, server/client separation, minimal network overhead, and clear comments for future tweaks.
• Configuration files (JSON/Lua tables) so I can edit keybinds, item lists, and text prompts without touching core logic.
• Compatibility with the latest fxserver build and ESX/QBCore hooks (I currently run QBCore but may swap later, so clean abstraction is a plus).
• A brief README explaining installation, dependencies, and how to extend the script for new interaction types.
I’ll test on a live staging server; we’ll iterate quickly if any edge-case bugs pop up. Deliver the finished .lua (or .cs) files, config files, and README in a tidy resource folder ready to drop into my /resources directory.
• Interact directly with one another (e.g., request/accept trades, give or receive items, share cash).
• Perform simple cooperative actions (carry, escort, drag, or seat-share).
• Trigger contextual animations or chat prompts tied to those actions.
• Respect server-side permissions and anti-cheat safeguards.
Key expectations
• Code must follow FiveM best practices—event-driven, server/client separation, minimal network overhead, and clear comments for future tweaks.
• Configuration files (JSON/Lua tables) so I can edit keybinds, item lists, and text prompts without touching core logic.
• Compatibility with the latest fxserver build and ESX/QBCore hooks (I currently run QBCore but may swap later, so clean abstraction is a plus).
• A brief README explaining installation, dependencies, and how to extend the script for new interaction types.
I’ll test on a live staging server; we’ll iterate quickly if any edge-case bugs pop up. Deliver the finished .lua (or .cs) files, config files, and README in a tidy resource folder ready to drop into my /resources directory.
Related categories:
Game Design
C# Programming
Game Development
JSON
Lua
Scripting
API Development
Game Programming