We have server dependency constraints such as:
dependencies {
'/server:4000',
'/server:999999',
'/server:696969',
'/policy:subdir_file_mapping',
'/policy:meow',
'/onesync',
'/gameBuild:h4',
'/native:0xE27C97A0',
'/native:0xDEADBEEF',
}
It would be useful to add similar restraints for resource dependencies, as they are currently limited to “is this resource running”.
-- check if a resource is running in the server context
-- allows for server-only resources to be ignored for client dependency checks
dependency '@resourcename:server'
-- if the resource exists, treat it as a dependency - otherwise ignore it
dependency '@resourcename:optional'
Version checking would also be useful, but likely a nuisance due to different versioning standards, weird syntax, etc.