worktycho

Theres a lot of classes that fall under the heading threading (mutex/cs, CSLock, ...). Also we have a lot of ad hoc Functor classes that could be replaced with lambdas...

Also fixed width types: Byte, char -> int8_t unsignedchar -> uint8_t Int16 -> int16_t UInt16 -> uint16_t and so on.

The thing is we currently use chars in two ways. One is a value that is capable of holding values in the range -127 to 127 which would not be...

A few other types will need splitting as well. Int64 in some places should be replaced by int64_t and in others int_fast64_t or int_least64_t.

Torches don't have a BlockEntity, so the data would have to be stored by the simulator. I think we would need to clean up the simulator first, but then this...

Also, if the functions are inlined as they will be in a loop, it quite frankly doesn't make the blindest bit of difference. With the following use functions there is...

@peterbell10 But we avoid functions in other translation units in tight loops, and in non-loop code, the cost of loading the code will probably hide it. If you know any...

Hmm, maybe we should try optimizing DoesIntesect. Using `return (a_Min1 < a_Min2 & a_Max1 > a_Min2) | (a_Min1 >= a_Min2 & a_Min1 < a_Max2);` as the interval intersection, moving the...

So basicly the physics engine needs to have full bounding box support.

That was an accident. Are there any blocks that aren't either empty or half blocks?