[Resource Manifest] server_only dependencies break loading client-side

Notes:

  • Server artifact 4557 Windows

Expected behavior:

If resource A depends on resource B, but resource B is server_only. Then resource A should not depend on resource B client-side.

Current behavior:

If a resource A marks resource B as a dependency. But resource B has server_only 'yes' set. Then clients will be unable to join since client-side, resource A can’t load the non-existent resource B.

Repro:

FxManifest Resource A

fx_version 'cerulean'
games { 'rdr3', 'gta5' }

dependencies {
    'resourceB',
}

FxManifest Resource B

fx_version 'cerulean'
games { 'rdr3', 'gta5' }

server_only 'yes'

Server loading will work fine, however the client will be unable to join the server since it can’t start resource A.

This is non-trivial to fix, since the client doesn’t know of the existence of the server_only resource.

One potential solution could be to generate a stub resource for these without a manifest/packfile requirement, however.

1 Like