Upload the right package
For bugs spanning multiple files, upload a ZIP of the affected resource with fxmanifest.lua, client, server and configuration files. Describe relevant dependencies and database schema. Encrypted or unreadable content cannot be edited like open source code.
Narrow down a bug
- Keep a backup and reproduce the bug.
- Copy the exact console error with filename and line number. Describe what triggered it in game.
- Ask for the cause, affected files and proposed correction.
- Apply the result to a test environment and repeat both the failing case and a normal workflow.
Work with the Config Editor
Recognised configuration files can be edited in the Config Editor. Available fields depend on the file and its structure. Review values, types and changes before saving; a configuration does not replace a missing resource or automatically install a dependency.
If the result is incomplete
Report missing files using their exact path and the original request. If you requested only an audit, explicitly ask for implementation. When a run fails or its outcome is unclear, check the existing run before submitting the same paid task again.
Example prompt
Parking produces “attempt to index a nil value” in server/garage.lua. The ZIP includes the manifest and config. Steps: buy a vehicle, take it out, park it. Identify the cause first and repair only the affected workflow.