Hot‑reload demo wows devs
@ProceduralLevel demoed hot‑reloading of assets and shaders inside a from‑scratch engine and called the workflow 'incredibly satisfying' — the clip grabbed attention and shows how fast iteration can transform indie tooling. The demo's community reception (several likes) underlines how much indie devs prize live editing for procedural systems and shader work. (x.com)
The clip was posted from the account tied to Procedural Level, the studio credited as Voxelgram and Voxelgram 2’s developer on Steam. (store.steampowered.com) Voxelgram 2 carries a Steam release date of August 14, 2025, and Procedural Level’s site and store pages advertise active community features including Workshop support and hundreds‑to‑thousands of user puzzles. (store.steampowered.com) The demo itself was shared on the studio’s X profile (the post URL provided in the card points to that account) and is surfaced from the same official social links listed in public store metadata. (x.com) The clip’s behavior—live shader/asset changes appearing in a running build—matches a file‑watcher + runtime‑reload pattern commonly implemented by indie engines; that implementation pattern is documented in shader hot‑reload writeups and engine examples such as community guides and Bevy’s hot‑asset example (this is an inference from the visual behavior). (wejdell.github.io) Procedural Level’s public pages list X and YouTube as contact/social channels and show an ongoing update history for their games, indicating the account that posted the demo is tied to an actively maintained indie studio. (steamdb.info)
