Legacy and Enhanced: plan two build targets

Choose the target edition before you export. A project that works under one set of tools and game assets is not automatically evidence for another target.

The Cfx.re Enhanced onboarding guide points creators to Alchemist for asset conversion and to a separate page describing behavioral differences. Use that maintained guidance as the starting point rather than an old download filename.

Do not turn an archive label into a compatibility claim

This site links the supplied v30_dev46 CodeWalker archive. The author’s GTA5-Mods page gives that archive a January 29, 2024 date. Linking it does not mean it is the newest build or an appropriate toolchain for every current target.

Check the author’s current release channels and the version-specific tool documentation. Record what you actually used. A tutorial should distinguish a historical requirement from a tested present-day setup.

Separate the source from the output

A practical workspace can keep one original source project with clearly labeled target-specific export directories:

cw_workshop/
  source/
  exports/
    legacy/
    enhanced/
  releases/
    legacy/
    enhanced/
  test-records/

These folder names are a workflow suggestion, not a platform requirement. Their purpose is to prevent a release from accidentally combining unrelated outputs.

Keep conversion logs or notes alongside the resulting files. Do not overwrite the only copy of your source or your last known working package during a conversion experiment.

Verify the conversion at more than one boundary

First check that the selected toolchain accepts the source. Then inspect the generated assets using tools appropriate for the target. Finally test the actual FiveM resource under that target’s server and client conditions.

A successful conversion process is not the same as a successful gameplay test. Use the same arrival, room-transition and collision routes you used for the original build, and record any target-specific differences.

Do not apply an old forum command or an arbitrary flag because its wording mentions Enhanced. Follow the maintained instructions for the asset type and version you are converting.

State what you tested

When distributing a map, name the target edition and the conditions of your checks. Keep separate release identifiers when the output differs. Document known limitations rather than hiding them behind a generic compatibility badge.

This site’s tutorials describe a workflow and link their technical sources. They do not certify a particular archive, server build or user-created MLO. Your release record is the evidence for your project.

Start with the release checklist before publishing a second target. Reusing the same test plan is helpful; reusing the first target’s results without running the tests is not.

Compatibility checkpoint: September 20, 2026

The Cfx.re Enhanced onboarding guide now documents Enhanced server downloads, points to Alchemist for asset conversion and links a separate behavioral-differences reference. Do not describe FiveM in general as Legacy-only based on an older tutorial.

That platform documentation does not expand the capabilities of this website’s own source tools:

Maintain separate source/export/test records when converting. Confirm the intended edition before selecting game folders, importing assets or packaging resources. A conversion tool producing files is one stage; reload and gameplay checks remain separate. Read the file-format reference and release checklist before marking an edition supported.