why static? it can not be skinned like deployed can.

You can spawn any chair entity you want. Can you be more specific with your question?

Thinking on this some more, is your question: "why does the default config have the following mapping?"

"chair": "assets/bundled/prefabs/static/chair.static.prefab"

One reason was that it avoids the "pickup" prompt, though admittedly I didn't put a lot of thought into the default config values for "DeployableOverrides"; it was mainly derived from running a program to scan the prefabs to ascertain which deployable entities had static variants, then I just applied those. I completely overlooked that chairs can be skinned, since I don't play the game nor own any skins; I primarily discover use cases by looking at the game code, and by getting user feedback.

If your followup question is: "how can I spawn the deployed chair?", then you can do that several different ways.

• Change the config to use assets/prefabs/deployable/chair/chair.deployed.prefab, then spawn a new chair with maspawn while holding the deployed chair
• Run maspawn chair.deployed to spawn a new deployed chair explicitly
• Change the profile data file to refer to the deployed prefab, then reload the profile

> reason was that it avoids the "pickup" prompt\n\nunderstood