Merged with a previous thread with the same suggestion.

Thanks for the note, I added more descriptions to the prototype for the next release.

Quezler wrote: Mon Feb 23, 2026 7:00 pm Figured that'd be the response, kinda odd that destroy_on_empty is an option at all then honestly.

It allows you to make a time limited container that doesn't care about whether it's empty or not. Just set time_to_live and make the alert timer longer than the time_to_live.

For the usecases listed here, it sounds better to me to expose that specific information (add mod thumbnail to SpritePath and so on), since we prefer higher level apis over lower level access. Is there some specific reason you'd want lower level access in the runtime stage?

Backported to 2.0.

Thanks for the note. I've adjusted the description of "picture" to make clear it's only loaded if "pictures" is not defined.

Thanks for the note, I've modernized the description for the next version.

The doc says "The width and height of the sprite.", not "picture" because it is indeed the width and height of the sprite that is displayed in-game. "Frame" would be misleading here because a sprite doesn't have animation frames.

::width and ::height however said "picture" and I've changed that to ...

Thanks for the note, doc updated for the next version.

Not an expert at Mac/graphics at all, but "Initial atlas bitmap size is 4096" looks suspicious in the slow logs, try setting it (max-texture-size) higher, like 16384. It may be helpful to just load the game and press reset in the graphics options, normally the game should be clever enough to select ...

Thanks for the note, I added this to the docs for the next release.

Added LuaEntityPrototype::inserter_max_belt_stack_size read for the next release.

The description belonged to a property that was removed from the prototype and indeed no longer applies. I've fixed the docs for the next release, thanks for the note.

I noticed that this was documented on the various draw_* methods but not LuaRenderObject itself, so I've adjusted the LuaRenderObject documentation for the next release.

Thanks for noticing this, it should indeed be ItemIDFilter and item_quality shouldn't be there. Fixed for the next doc release.

In the future, please don't post in threads in the resolved subforum, but instead make a new thread, new posts are easily missed here.

Added to the docs for the next release.

Thanks for the note, doc fixed for the next version.

Confusing indeed, description added to the docs for the next version.

The only intended way to access sounds at runtime is via the soundpath, so since it's available there this already exists.

The wiki pages for the two recipes list the changes in more detail. The official changelog doesn't usually change after the fact, so it'll stay the same (slightly ambiguous).