Using logic for resource dependencies

My idea was basically like the server dependency constraints, but using @ (like when referencing a resource) instead of /, and having tags like server and optional.

optional would be good enough for this case imo - basically being dependent on the resource if it exists.