Mistakes are easy to make and you want them to show up immediately instead of randomly at runtime. If you have lots of tiles, change the fields later, or manipulate the data in code you'll make a typo or forget something eventually.

With a class, every tile is guaranteed to have all the fields, and if you give the fields explicit types, they're always guaranteed to be the correct type. If you do something wrong, you won't have to figure out why it's broken later, because the editor shows red before you even run it.

Also, the editor autofill only works when it knows what it's working with.

You should probably use a class instead of a dictionary for tile attributes.

Going through the property list is pretty weird too.

Cool, thanks!

Hey I have one!

https://github.com/sevonj/scratchmark

It happens to already have Brazilian Portuguese, but the translation is way out of date and is missing a lot I've added in the past couple months.

OpenSCAD is like programming a model. You can do pretty cool things with it, but it's not necessarily intuitive to most. See also: https://cults3d.com/en/3d-model/various/editable-bike-pump-mount

Oh boy. Well, maybe the hug of death gets the message through even clearer.

That's pretty much guaranteed. Some said the safe threshold is 1,2 m, but who knows how the number actually looks after validation. So any signature is still important.

Could you just forget about this guy already? What he did is more than undone by now and bringing him up is just useless drama.

I'm guessing mining for lootboxes and items. Never underestimate people's ability find money in an absurd waste of resources.