Ellpeck/Contentless
1
0
Fork 0
mirror of https://github.com/Ellpeck/Contentless.git synced 2024-11-22 07:23:30 +01:00
Code Issues Projects Releases Wiki Activity

document references

Browse source
This commit is contained in:
Ell 2023-12-21 18:39:15 +01:00
parent 95dba50148
commit e69aa3e089
2 changed files with 6 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
README.md
View file

@ -59,7 +59,10 @@ If you want to change the way Contentless works, you can use a configuration fil
"TextureFormat": "Compressed" "TextureFormat": "Compressed"
} }
} }
} },
// A set of content pipeline library references that should optionally be added to the content file, or whose paths should be changed in the content file if they don't match the project's package references
// Default: []
"references": ["MonoGame.Extended.Content.Pipeline"]
} }
``` ```
For an example of a config in use, see the [test config](https://github.com/Ellpeck/Contentless/blob/main/Test/Content/Contentless.json). For an example of a config in use, see the [test config](https://github.com/Ellpeck/Contentless/blob/main/Test/Content/Contentless.json).
@ -69,4 +72,4 @@ When running Contentless and supplying the location of a MonoGame Content Pipeli
Contentless figures out which importer and processor to register for any given file by generating a list of all the importers and processors that are available, both inside of MonoGame, and inside of References added to the `Content.mgcb` file. This process is similar to what occurs when adding an existing file through MonoGame's Content Pipeline tool. If Contentless sets the wrong importer or processor for any file, the user can simply open `Content.mgcb` in MonoGame's Content Pipeline tool and edit it manually. Contentless figures out which importer and processor to register for any given file by generating a list of all the importers and processors that are available, both inside of MonoGame, and inside of References added to the `Content.mgcb` file. This process is similar to what occurs when adding an existing file through MonoGame's Content Pipeline tool. If Contentless sets the wrong importer or processor for any file, the user can simply open `Content.mgcb` in MonoGame's Content Pipeline tool and edit it manually.
As Contentless never changes any existing content of a `Content.mgcb` file, all changes that are made to it by hand or using the Content Pipeline tool will not be overridden. As Contentless never changes any existing content of a `Content.mgcb` file, all changes that are made to it by hand or using the Content Pipeline tool will not be overridden.

2
Test/Content/Contentless.json
View file

@ -5,7 +5,7 @@
"Ex*.png" "Ex*.png"
], ],
"logSkipped": true, "logSkipped": true,
"references": ["monogame.extended.content.pipeline"], "references": ["MonoGame.Extended.Content.Pipeline"],
"overrides": { "overrides": {
"Copy.*": { "Copy.*": {
"copy": true "copy": true