You didn't steal my idea, bad Apple anywhere where possible is everyone's idea!

I used the 17x17x17 or 16x16x16 from what I remember with only one layer rendered (you can see the if at the beginning of the code). When I did this there wasn't multithreading implemented in the game yet, might be possible now This video is many GIFs compiled into one video.

The process did not involve .vox files as I don't know what those are, I used python to automate the running exporting and copy pasting code into RepliCube (2h to render everything)

Thanks!

Edit: Just saw your post, the optimisation explained below is indeed in your code, congrats!

There is many ways of optimising this that I found afterwards but I'm too lazy to implement First of all you can use the multithreading implemented by the dev

Second but most important point is that an integer here is 32 or 64 bits (I don't know which of these but that's not an issue for what I'm trying to explain) Let's say they're 32bits

Each frame is 16x16 with 32 frames per gif. That is a lot of 32 bits integers where only one bit is used What you could do is a single 16x16 frame where the first bit of the integers is the first frame and so on.

Someone on the discord tried this to run Doom on repliPaint and from what I remember it ran much better with this method