DML Limitations

[67425e6849791voodoo47]

I've never tried it, but that might just be the case - basically the syntax of dml clashing with the syntax of strings. not sure whether something can be done.

[67425e6849a5bZylonBane]

Worst-case, use '' instead of ".

[67425e6849ba0Yankee Clipper]

If you weren't looking for it, I doubt many people would even notice that those are 2 single quotes instead of a proper double. I just hope I can learn to live with the knowledge that it just ain't right.

[67425e684a02fvoodoo47]

The limitation that I have found to be the most, well, limiting, is the inability to create anything new. Not only can't you create a new class of something

as of 2.48, this is no longer true, and new archetypes can be created via dml (see the documentation). this means very complex dml mods are now possible (you can create new metaprops, stims, basically anything that has a negative object id). when doing such a mod, remember that everything that gets created needs to be referenced by archetype names, not object ids.

found one limitation though - currently, only archetype ids are allowed for Receptrons target/agent object, so if your mod requires using a dml created archetype at that exact spot, you are out of luck.