A resource started, but with hundreds of warnings

What the console says

Started resource <resource> (<warnings> warnings)

What it means

<resource> started with **N** warnings. It is running, but that many complaints means a lot of it is not doing what the manifest says.

How to fix it

1. Read the warnings above the 'Started resource' line — they name the exact files. They are almost always missing files the manifest declares.
2. For a car pack, this usually means metas or stream files that were never shipped, or a folder structure the manifest does not match.
3. Fix it at the pack level rather than file by file. A resource emitting thousands of warnings was assembled wrong, not damaged one file at a time.

When it is not this

That is exactly why this is worth surfacing. Do not treat it as an outage though — it is a quality signal, not a failure, and a resource can run for months like this. Judge by the number: dozens can be vendor sloppiness, thousands cannot.