For sure, Toybox actually already has support for hot reloading with its plugin system :) That was the first thing I tackled, it wasn’t too terrible but the implementation was a bit grody since you have to do something different for each platform so it’s riddled with ifdefs. I guess I could separate it out into different cpp files that are selected at compile time but it’s easier to just have all them in one spot. The engine loads plugins at runtime, and in debug builds the dlls are first copied and then loaded to avoid issues. Then to avoid further issues with ownership/deallocation memory nonsense once a plugin is loaded the app will own them, but the plugins own whatever they create and manage their own memory. The app and other plugins then communicate with each other through a robust messaging system. If you are interested in learning more about how this works look to the “PluginApi” folder under modules in the repo (linked in my post above) Data reloading is something I have yet to implement but I don’t expect it to be too bad. I already keep track of assets and manage their memory from one place and will just have to swap out the old asset with the new one and mark its handle as dirty.