UnknownShadow200

Not fond of having finite water sometimes behave in an infinite manner, will do proper review tomorrow though

My mistake for being vague - I mean finite water in general, not just the finite water block This change does seem to make it harder to trigger finite water...

The issues raised here made me think that some things about block physics in general need to be properly looked at and potentially redone, I just haven't found the time...

What exactly do you mean by that your chatbox becomes broken and that you are required to close the game to fix the issue?

I attempted to reproduce with both a classic mode and enhanced mode client connected, but 1) the classic mode client was sent `Wood` 2) the enhanced mode client was sent...

Note: this issue is actually about disabling the CustomBlocks extension server-side Extension support implies the following: - If CustomBlocks extension is supported, blocks 50 - 65 are supported and defined...

After five years, first issue (CPU usage showing 0.00%) was resolved in a1a7704d066ea525735c96d976c4adf4d054d61d (note: mono expected process ID instead of process name in performance counter, which was why it showed...

What issues are you having with loading the GUI? What settings are scattered around? What exactly are you proposing should be changed?

You're quite correct in that it's far from ideal how some settings files are in text folder - however, for the sake of maintaining backwards compatibility, I'm a bit reluctant...

Not sure what advantage there is in implementing that, compared to just editing using an existing text editor like nano