Pixel Crushers Forum

I'll implement that feature in the upcoming 1.6.6.3 (targeted for release early next week).

Slots are converted to strings containing the DisplayName of the referenced object.

We would like it to be configurable since the ID is unique and display name less so. We will cache a hashtable of the IDs and lookup when needed.

irve wrote:We would like it to be configurable since the ID is unique and display name less so. We will cache a hashtable of the IDs and lookup when needed.

This request is for Slots, correct? Does this apply to all Slots, or will you need to import some as IDs and some as DisplayNames?

I don't think that we need both at the same time, since mapping it for one case should solve it for all the others quite easily.

Also, I can imagine that configuration for that kind of dual logic is tedious at best.

Okay, I'll make it an all-or-nothing dropdown (all DisplayName or all ID).