Post #2895247

2026-05-11 13:14 UTC

@bryce@mastodon.brycedixon.dev @memoriesin8bit@mastodon.gamedev.place @tracefree@mastodon.gamedev.place Basically, nodes and resources do not do any rendering. They are just lists of commands for the rendering server to draw something. Resources don't even hold any rendering context, they use the canvas item RID passed to them. Given that information, consider this: you can create a custom resource that contains all the rendering commands you need, whatever they are. I have a custom texture type that draws styleboxes, for quick prototyping, for example.

Replies (1)

@yurisizov@mastodon.gamedev.place 2026-05-11 13:20

@bryce@mastodon.brycedixon.dev @memoriesin8bit@mastodon.gamedev.place @tracefree@mastodon.gamedev.place As an extra bit: texture resources don't even need to exist on disk to work with RTL. You can give them any resource path, even a completely made-up one, and that will still work as long as the resource is loaded in memory. In GDQuest I used this in the GDTour framework to make copies of all editor icons at runtime, assign them fake paths, and then put them in RTLs used to render tour contents for the user. This should also be helpful for the task at hand.

Open ##2895248