I guess I’m the only one who likes it huh? We’ll see if that changes as I release more libraries though… the second one is still pretty enjoyable, at least so far 😀

I don't like this rock. Robert, it's pissing me off.

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...

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!

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