@SlySven it set all the userdata for indoors, so every outdoors room had to be re-marked as outdoors. Though, that just seems to have been a one-time thing? Perhaps linked to another part of the "audit" process? Another issue, that seems to be causing a lot of problems with things like &qu...

Though for some reason the map audit forced every outdoors room on my map to be indoors.

Thanks! Working beautifully, it seems. Also includes some documented mapper functions that I've been waiting on foevah. Darker colors seem more readable too. Cheers.

Don't suppose you have a compiled version of either of those lying around for windows?

Happening on mudlet 3.0.0-delta. This map is not freshly-loaded.

"setRoomArea: bad argument #2 value (area Id must exist.)"

As the second return. Using setAreaName. The area name is unique.

And after testing with missari's workaround, it looks like an issue with moving rooms into empty areas, instead of an issue with area creation. After moving a room into an area with the mapper window, setRoomArea works fine.

Oh hey, someone encountered the same bug as me. It's a setRoomArea bug with mudlet 3.0. I'm not sure if it's a problem with area creation or a problem with setRoomArea not working properly with empty areas, but if you create a new area on 3.0delta, you can't move rooms into it. 2.1: setRoomArea retu...

setRoomArea() doesn't work properly for new areas on mudlet 3.0 (win10 and mac tested). If you create a new area, the area seems to exist properly, shows up on 'area list' through map loads/restarts, etc. The issue comes when you try to move a room into this new area. 3.0: setRoomArea() returns true...