Question 1

How do I preload all assets with Cargo in LÖVE?

Accepted Answer

Call the cargo table or its children as functions, like assets() or assets.sound.background(), to preload assets recursively or selectively, as explained in the preloading section to avoid runtime hitches.

Question 2

Can Cargo handle custom file types not in the default loaders?

Accepted Answer

Yes, you can define custom loaders in the options table, mapping extensions to LÖVE functions, allowing integration with any asset type, as shown in the advanced example with jpg files.

Question 3

What's better for LÖVE, Cargo or manual asset loading?

Accepted Answer

Cargo is better for reducing boilerplate and organizing complex asset directories, while manual loading offers more control for simple projects or specific loading sequences where overhead is a concern.

Question 4

How to set up image filters for all images using Cargo?

Accepted Answer

Use processors in the options table with Lua patterns, such as ['images/'] = function(image, filename) image:setFilter('nearest', 'nearest') end, to apply post-processing automatically after loading.

Question 5

Does Cargo work with LÖVE's latest versions?

Accepted Answer

Cargo relies on LÖVE's asset loading functions, so it's compatible as long as those functions remain stable; check the README for any version-specific notes, but it generally supports standard LÖVE releases.

Question 6

How to clear cached assets in Cargo to free memory?

Accepted Answer

Set an asset to nil in the cargo table to remove it from the cache, but note it only garbage collects if no other references exist, as mentioned in the advanced section for manual management.

cargo

What is cargo?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions