I forgot to make that change to cRedstone.cpp and included the same problem in cPiston.cpp. Oops
I think the redstone class should be changed to not update blocks, but to build a queue of blocks that need to be changed and send all the blocks that need to be changed to the world tick queue.
Anyone else have any ideas on this?
Also, now that I have a working fill algorithm, I should probably change it to a more efficient one. I used the easiest one to program in as a proof of concept. Currently, a 10x10x1 block of redstone requires 344 block replacements instead of just 100, and I don't know how many times it checks each block. Probably more than 344 times
I think the redstone class should be changed to not update blocks, but to build a queue of blocks that need to be changed and send all the blocks that need to be changed to the world tick queue.
Anyone else have any ideas on this?
Also, now that I have a working fill algorithm, I should probably change it to a more efficient one. I used the easiest one to program in as a proof of concept. Currently, a 10x10x1 block of redstone requires 344 block replacements instead of just 100, and I don't know how many times it checks each block. Probably more than 344 times