Sorry if this seems obvious, but it's non-obvious over here and I was hoping somebody would help me out.

How do I get the pointer to the Attachable foot objects on AHumans reliably? I just need to do this during Create(). I'm a little fuzzy about how one iterates through an AHuman to find objects in general, but in this case I need that specific pointer so that I can do some physics stuff to fix an issue in my mod

You'd only be able to get a pointer to them if they're GetsHitByMOs = 1. What you'd do is simply iterating through all MOs and checking to see if their RootIDs match your actor, and a PresetName check to see if they're the specific foot.

Ah. I can shut off that property after I've found it, though?

Or will that be read-only with an Attachment datatype that isn't a HeldDevice?

I'll test it when I get home, just wanted to know in advance if there were any other issues I'll have to work around

Well, so much for this being straightforward, lol.

Here's my script searching all the MOs for the feet:



Here are the values in the INI:


...yet the PresetName isn't printed. Legs, arms, helmets, guns... no feet. I guess that they're "invisible" since the Atomgroup's what really does stuff. I don't suppose I can use an Attachable there instead and... heck, I'll just try it and see...

Should probably have posted this before you wasted your time but yeah, I can confirm that you can't find them like that. When you first put up this thread I tried the exact same thing and got the same result. I guess they're not attachables, I can only assume your theory is right.

Feet are AtomGroups.

The reference to the visual foot is some special feature of the AHuman Leg, which is a non-standard Attachable.

AtomGroups' exposure to Lua isn't documented, if it exists at all.

But the foot AtomGroup is in charge of leg extension, instead of the other way around, so if we change RotAngles of legs, they're offset from the foot bitmaps... that are supposedly Attached to them but in fact have no Lua-accessible pointers so far as I can tell.

In fact, the Foot section can be removed, getting rid of the visual foot, without crashing or causing any other issues. But if you remove the AtomGroup or name an Attachable datatype, crashy-crashy, because the engine expects an AtomGroup.

The only thing I haven't tested is whether AtomGroups are allowed to have a representative bitmap; guessing no. Not that matters, because I still can't get a pointer to them, rotate them, whatever.

Really unsure why it works this way