Map & MLO Inspector
Checks a map or interior for missing collision, duplicate names and hash clashes.
Start here
Run Map & MLO Inspector on a copy of your source files
PulseConvert → FiveM tools → Map & MLO Inspector
Open the workflow: PulseConvert → FiveM tools → Map & MLO Inspector. If the tool is locked, check its access notice instead of assuming it is available to your account.
Prepare the exact kind of input listed for this feature: Input: A map or MLO resource zip. Keep an unchanged backup and ensure you have permission to reuse the assets.
Open the tool page and provide the requested source files and any displayed options. Check that the detected file types match the input requirement; do not replace unrelated files just to make an upload succeed.
Review the resulting files or job details. Expected outcome: Expected output: Archetype problems and clashes with vanilla objects. Review duplicate archetype names and collision coverage before combining or disabling map resources.
Compare the result with your original in a local editor. For resources that load in FiveM, start with an isolated test server; inspect the first client/server console error and test the asset in game before installing it for players.
Practical example
Checks a map or interior for missing collision, duplicate names and hash clashes. Keep the original file beside the result so you can compare what changed.
Before you begin
- Input: A map or MLO resource zip.
- Sign in to PulseConvert before opening this tool.
- This workflow may use PulseConvert's server-side processing; keep source assets private.
Overview of the setup
Prepare the input
Work on a copy of your originals. Gather: A map or MLO resource zip. Check that any source asset can legally be reused.
Run Map & MLO Inspector
Open Map & MLO Inspector in PulseConvert and supply the requested input or settings. Review duplicate archetype names and collision coverage before combining or disabling map resources.
Review the result
Expected result: Archetype problems and clashes with vanilla objects. Read reported warnings, inspect the generated files and try the output in a separate test server or appropriate editor before production use.
Features explained
What each feature does and what to check before publishing or installing the result.
Purpose
Checks a map or interior for missing collision, duplicate names and hash clashes.
Input and preparation
Bring A map or MLO resource zip. Keep an unchanged copy for comparison and rollback.
Result and verification
Expected output: Archetype problems and clashes with vanilla objects. Review duplicate archetype names and collision coverage before combining or disabling map resources.
If it still does not work
- If the tool rejects the input, compare your file extension and the files inside the archive to the input requirement above. Source files inside nested folders may need extra review.
- If the tool reports success but the result does not function, do not assume the file is compatible: inspect warnings, actual output names and their references, manifest files, and version compatibility.
- Review warnings and test the output before putting it on a live FiveM server.
Troubleshooting and safety checks
- Unsupported format or missing files? Verify the input matches the exact type described above and that the archive isn't only a screenshot/readme.
- Output exists but fails in FiveM? Check the resource folder, generated manifest, file references, first client/server console error and version compatibility.