As we all know, in the element properties, we can see amount of such elements placed in the level and the percentage of playfield they occupy. It works as intended, until we come to MM and DF walls, since these are such kind of element which usually exist in 15 (technically, 16) combinations of their layout among all 4 sub tiles. In other words, when you place some DF steel walls on the playfield and check the properties of that wall, we can see it saying that it's placed nowhere. Technically, such walls can't ever be placed since they're just items to place other elements, which are usually not intended to be seen in editor, so df_steel_wall, df_wooden_wall, mm_steel_wall, mm_wooden_wall, mm_ice_wall and mm_amoeba_wall will never show at least '1' after the line "In this level:".
- kufgdskbkdus.png (117.75 KiB) Viewed 747 times
- sdkfbkdskfj.png (111.53 KiB) Viewed 747 times
I think this can be fixed if you hardcode these elements instead to count sums of their in-game variations being df_steel_wall_2-16, mm_steel_wall_2-16, etc. (considering mm_[any]_wall_1 is just empty, it should be ignored), where four of all combinations should count as '1' each, then six of them as '2', four of them as '3' and last one as '4'.
Here are all combinations:
- ifisdklnfkds.png (51.32 KiB) Viewed 747 times
And speaking of properties, something silly is going on with the properties of DF/MM elements overall. Obviously, they don't list their functionalities as they're not supported outside of MM engine, so that's why, for example, MM Pacman has no properties despite being able to move around and eat amoeba walls, or MM steel wall having no properties despite being presumably (?) indestructible. Well, to be real, that tag lists only "standard properties", and MM doesn't really have any "standard" properties aside from pacman movement, which is, again, restricted just to MM, so that might be pretty much faithful to the title.
- fdlfdsnlfkds.png (17.75 KiB) Viewed 747 times
