Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
Pages: 1
Sometimes you wanna erase something, but it be too big for your tiny little erasing hands and you don't wanna clear it neither. Cause you spend a long time making all them hook jumps and don't wanna hafta go through the tedious process again. That's why I suggest ERASER BRUSHES! Different sizes of erasers for everyone's erasing needs. Smart, right?
Offline
I would suggest that you use EEDitor with selection tool. Hookjumps, not even fun.
Offline
Offline
i think they mentioned at one point that they were working on a fill feature
I can see rectangles working as clients only need to be told 2 coordinates of opposite corners to enact the shape (it'll take as much data as placing 2 blocks no matter how big the rectangle) while filling clients will need to be told the edge of the fill (which will require lots of blocks which some may fail causing the fill effect inside).
I have assumed that fill feature will not be a fill message on its own as blocks can be removed which some clients will recognise and others won't which will cause differences between players.
The rectangle can be a rectangle message as it isn't dependent on other blocks in the world.
I vote for rectangles and not fills.
Thank you eleizibeth ^
I stack my signatures rather than delete them so I don't lose them
Offline
I would suggest that you use EEDitor with selection tool. Hookjumps, not even fun.
It was a joke, I wasn't actually making hook jumps.
Also I shouldn't have to download a client just to be able to use common sense features like that
Offline
Also I shouldn't have to download a client just to be able to use common sense features like that
well you either use the bot or go the hard way and wait for the feature to be officially implemented, which might take a while. that is, if the feature will be ever implemented
Offline
Pages: 1
[ Started around 1732759900.8452 - Generated in 0.053 seconds, 12 queries executed - Memory usage: 1.47 MiB (Peak: 1.6 MiB) ]