Assemblies, New Deployables, and this Constructor mentioned. Such a tease, I feel a little hype. Is this continuation of game items or was something learned in PP and filtered back? Can we finally build on-site?

But really, just curious

I'm more excited for the inventory visualization and wound manipulation.

Oh, and the MOID being raised up to 65535.

Influenced by the PP tearing-down and rebuilding, yup.

Very delighting, probably may need a work-around to do BG bits. But this is good, now you'll have a reason to buy dirt, heh, so you keep the terrain as it.

@4zk - That MOID (256^2), my goodness that will be a train that can not be stopped. Meanwhile, a base can be a beast with all the doodads and moveables it can have.

Hm, is the topic about a video or blog somewhere?

Maybe so, but it will still be limited by the efficiency of the engine and your own hardware. It's great and all, but what's the point in having a monster-base when it makes your FPS/sim rate slow to a crawl?

So far the only good thing 65K of MO IDs brings is that you don't break the game when you have more than 255. Still you'll probably won't live long enough to break the 65K limit due to lag.

Wait. So instead of doing "actor.ID ~= 255" what do we do? Or we simply don't have to do it anymore?

MovableMan:IsActor(actor)?
The answer probably depends on what you're trying to do with it.

I guess, yeah. Well, most mods that use that method to check if a MO still exists will probably have problems.

Where the hell can I get myself up to date on this stuff? Dev blog seems like it's been dead for a while, as has the steam page.

The twitter feed. It's a bit hard to see but it scrolls by at the top of the datarealms.com main page.

NoMOID constant is still 255 for compatibility reasons. You just can't do 'id < 255' to check for valid ID number, you should do 'id ~= 255' instead.

@Arcalane - skunkworking, dear chap, skunkworking. Stress test all the ideas.

Smart move on that one