GMRoomLoader made it to the Shortlist last year, and it would be amazing to win this time around! It has grown a lot since then, especially with the recent v2 release.

If you feel like the library deserves it, please consider nominating it in the Best Tool category!

#GameMaker

We also have our first video tutorial by @dragonitespam.bsky.social! Michael introduces GMRoomLoader basics and goes over a few interesting edge cases. Thank you for making it!

www.youtube.com/watch?v=mZeg...

The documentation has moved from GitHub Wiki to VitePress - an amazing SSG documentation builder made by @evanyou.me.

This was my first time building something like this and VitePress was an absolute pleasure to work with. Thank you Evan!

Some of the features include scaled and rotated loading, merging layers and tilemaps, fluent state management with a Builder pattern, Data and Payload enhancements, and overall cleanup/optimization.

github.com/glebtseretel...

Last week I released a major v2 update for my #GameMaker library GMRoomLoader, used for loading room contents at runtime!

It brings massively improved documentation, a revamped demo with an ImGui interface, a full PascalCase API overhaul, and many new features - listed below.

The first Cookbook really motivated me to finish and release my first library, GMRoomLoader.

I highly recommend joining this one if you've got a new library idea or something that's been sitting on the backburner for a while. Great chance to put it out there and get some eyes on it!

#GameMaker

room_get_info() is the best, love it.

Yep, structs are definitely the way to go here. Not to mention json_decode() returns the mostly obsolete and inferior ds_map instead of a struct.

I'd also store this data globally so it's initialized once instead of creating a new struct every time the function is called.

Apart from that - absolutely, arrays/structs are much better to work with.

There are still a few places where you have to use them, like list-based collision functions (ds_list) and Async events (ds_map).

And althought you can recreate any ds using arrays/structs, built-ins still outperform them in "heavy computation" with lots of push/pop.

I remember trying this back in the day and thinking it was really cool (same with image-based dungeons), but setting something like this up now feels far more cumbersome than just building rooms in the room editor and loading them in.

Looking forward to this!

#GameMaker Well, now it's a trilogy. This last one (for now) displays room history and helps you make sure your transitions and room flow are set up correctly.

Just the debug overlay version this time: gist.github.com/glebtseretel...

#GameMaker And here's a little follow-up. This one displays the amount of instances per object, sorted in descending order. Objects with 0 instances are ignored.

Overlay: gist.github.com/glebtseretel...
ImGui_GM: gist.github.com/glebtseretel...

Overlay: gist.github.com/glebtseretel...
ImGui_GM: gist.github.com/glebtseretel...

Hey #GameMaker devs! Here are 2 quick functions for displaying the ResourceCounts data you can fetch from the debug_event() function - one for the built-in GM debug overlay, another for @nomm.dev's ImGui_GM.

Super helpful for tracking down memory leaks!
Links below 👇