It's intentional. It allows you to quickly check if the collision mask has a value in the Lua state by simply checking if the key exists in the dictionary. If it was exported as the prototype definition does it: you would have to iterate over the entire list to check if 1 value existed.kovarex wrote:That is probably boost property tree construction limitation. It accepts array of strings without values, but the export contains the values. This will be changed in the future versions (0.15 probably) once we start using our own property tree implementation.
I checked tiles.lua for the keys. Maybe this is still accurate: https://wiki.factorio.com/index.php?tit ... lisionMask. I don't see any sign of having any new collision mask since 2015.aubergine18 wrote:Is there a list of possible keys for that dictionary anywhere? I was trying to find list of available options last night but other than scraping data.raw I didn't get very far.
Yes, I vote for dictionary too. Thanks!Rseding91 wrote:It's intentional. It allows you to quickly check if the collision mask has a value in the Lua state by simply checking if the key exists in the dictionary. If it was exported as the prototype definition does it: you would have to iterate over the entire list to check if 1 value existed.kovarex wrote:That is probably boost property tree construction limitation. It accepts array of strings without values, but the export contains the values. This will be changed in the future versions (0.15 probably) once we start using our own property tree implementation.
