Deleting content that is not in content folder?

[Shadowblitz16]

If someone renames a file this breaks.
Try to check if the file still exists that is referenced in the mgcb, if it doesn't remove it before trying to add it back again

[Ellpeck]

Hi! Contentless doesn't remove content items from the content builder file if they were moved or don't exist anymore, and it's not meant to do so either. Contentless only adds new content files to the content builder based on its default rules or the rules laid out in your Contentless.json config file. If you remove a file, you have to remove it manually from the content builder file as you would if you weren't using Contentless. I hope that answers your question, but let me know if it hasn't!

[Shadowblitz16]

@Ellpeck
Why is the content not synced with the stuff in the folder though?
It's suppose to be contentless not require us to open the mgcb every time a reference breaks.
If someone renames or deletes a asset it should update it accordingly in the content.
At least make it an option.

[Ellpeck]

As advertised, Contentless is a tool for adding assets to the content pipeline, not updating or changing existing ones. A key part of the philosophy of Contentless is the following, as described in the README:

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.

Sorry if this is not a policy you agree with!

[Ellpeck]

Hi! I've gone back and forth on this and decided that, especially with #3 as a new suggestion, it might be nice to have this as a feature that is disabled by default, but can be enabled in the Contentless.json file per project!

[Lurler]

As I understand you have implemented this feature?
But how can I enable it?
I don't see any documentation on it neither on the main page nor in the config example.
Can you please clarify how to enable it?

[Ellpeck]

Hi! This feature is not yet implemented, which is why this issue is still open :)

[Lurler]

I see, I was confused by your previous message 😅
In that case looking forward to have that feature available in the lib!
Any ETA?

[Ellpeck]

I don't have an ETA unfortunately, since this is not a feature I personally need, and so it's not something I'm really all that desperate to add. Once I get some work done on the tool again, I'm hoping to be able to also get this implemented though.

[Lurler]

I see, that's understandable.

In that case I will just add that I do agree with the OP, the best part of this tool is that it allows me to forget about the atrocious MGCB and just drop files into the project without thinking twice and they will automatically be processed.

But then if I change anything I have to go back and clean the mgcb of the old stuff again for no good reason which seems like a fault in behavior.

Yes, I do understand your logic as well, but many people just want to set it up once and forget about it.

But anyway, I understand. I will be patiently waiting for a new version 🙂