{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihmmmqd3sb7wbinulnpdvv7aweaph7h5uljp57of6axa72h3p6j34",
    "uri": "at://did:plc:dxjzgxe7cvirxkwfjr2tjspt/app.bsky.feed.post/3megcwmekcre2"
  },
  "path": "/t/does-jme3-attach-a-unique-id-to-every-element-of-a-scene/49410#post_7",
  "publishedAt": "2026-02-09T09:42:59.000Z",
  "site": "https://hub.jmonkeyengine.org",
  "textContent": "I never worked with the SceneComposer, but at the top of my mind are two solutions for your mapping:\n\n(1) Use the name field as unique identifier, with the drawback of keeping a record of all the names and potential performance issues searching for objects when you have a larger number of objects.\n\n(2) Add a ‘GameEnity’ control (extend AbstractControl) holding a unique ID. You can set the ID field in the SceneComposer. When you start the game you read these controls into a registry and validate (duplicate). Then in your script you call the registry for the ID and get the correct object very quick (without searching via name).\n\nI hope this helps.",
  "title": "Does JME3 attach a unique ID to every element of a scene?"
}