oh, completely forgot! sorry.
No, it's fine! Tell me if it actually works lol. It did for me.
mostly works-but I get ERROR - cannot operate on a deleted sprite every once in a while when combining elements.
Odd...I didn't change anything related to sprite deletion. Was it like that in the original?
At least I was able to make it faster!
I'm sure.
Why I left it like that? It's not something very important, only to stop confusion from new players.
I forgot how to get columns from a single item () of () easily until I read list topics again. 
Later, I will roll out the changes to the original.
Good News!
Everyone who tested this game, happier? I finally optimized the game thanks to @blockpointstudios for helping me with that. If you combine elements, it won't lag that much now! Have fun!
If you don't mind, I'm going to unshare my optimization now. I want to make sure you get the credit! Congrats on the release!
I found a 
bug. When you combine a 
stone and 
fire, it says Hmm... expecting a list but getting a text if you move fire above stone (error didn't happen when you drag stone on fire).
This is probably because of the dust being unobtainable.
Can you replicate?
List of combinations creating this issue:
- Water and fire.
- Stone and fire.
- Water and earth.
- Energy and water. 〠
...and many more combinations.
Can reproduce. Doubt Dust causing issues as I removed all its combinations for creating Dust, so I don't know how will they mess up... Strange.
I'm up late at night right now. I will examine at daylight.
Presumably it sounds like that certain Snap! reporters report a list if multiple inputs are provided but the only item if only one is.
I had a problem with this in one of my projects; reshape [] to () @delInput@addInput helped a lot for me.
So I looked in my code and it's too much of spaghetti still. I don't know where to put the block...
I fixed the combinations. You should be able to get Stone by Lava + Air.
I can definitely help you, but I need to know: which reporter primitive was causing the problem?
I'm sure one of these blocks is the culprit of the error. The dodgy editor isn't telling me which block by itself...
I have no idea how this happened. I'm bamboozled by this.
try single stepping :)
also, why do you have two predicates twice that are the same in the find first item (<>@addInput) in @list?
That was a mistake! I am fixing it, thanks for pointing it out!
I fixed the bug. It was an oversight in the code.
is this infinite
no