The Meaning of Life, the Universe, and Everything.
Join Date:
6/5/2021
Posts:
50
Member Details
Ok I know half slabs that are the same block type stick together but if you make a half slab say of cobble or sandstone and try to place them one on top of another they will place an air gap in the top part of the bottom block. It would allow for better block detail building and off centring blocks.
The reason why Mojang has not "fixed" this is simple - think of how many possible combinations of every type of slab there are - that's how many new blocks would need to be added, and what happens to the block properties when you mix different types of slabs, especially wood/stone (tool requirements, flammability, mining time, blast resistance, etc)? These issues are why this suggestion warrants a firm "no" from Mojang:
Combined slabs. If you're thinking "putting two different kinds of slabs together" would be great, it is! It just isn't going to happen. (6 September 2018)
An alternative is to use a tile entity, which can render a virtually unlimited number of blocks with only one new block added (a special "combined slabs" block), which would have to only be created when different slabs are mixed (assuming it uses the "normal" block renderer and not "entity" renderer there would be no impact on FPS, though a large number would degrade chunk update time and memory usage since each tile entity stores not just the blocks it represents but its coordinates). There is still the issue of how to handle mixed block types (does a combination of wood and stone require a pickaxe? Does it burn? The fire code would need to be rewritten to be able to selectively burn only the wooden part, or have tools only be effective on the part the player is pointing at and drop that half instead of both halves, as double slabs currently do).
The reason why Mojang has not "fixed" this is simple - think of how many possible combinations of every type of slab there are - that's how many new blocks would need to be added, and what happens to the block properties when you mix different types of slabs, especially wood/stone (tool requirements, flammability, mining time, blast resistance, etc)? These issues are why this suggestion warrants a firm "no" from Mojang:
An alternative is to use a tile entity, which can render a virtually unlimited number of blocks with only one new block added (a special "combined slabs" block), which would have to only be created when different slabs are mixed (assuming it uses the "normal" block renderer and not "entity" renderer there would be no impact on FPS, though a large number would degrade chunk update time and memory usage since each tile entity stores not just the blocks it represents but its coordinates). There is still the issue of how to handle mixed block types (does a combination of wood and stone require a pickaxe? Does it burn? The fire code would need to be rewritten to be able to selectively burn only the wooden part, or have tools only be effective on the part the player is pointing at and drop that half instead of both halves, as double slabs currently do).
That's interesting information. Thank you.
Does it need to be so complicated?
What if the combined block takes the stats from the top slab? Lets say wooden slab on top and stone slab bottom.
That way both slabs would burn when exposed to fire, right?
I know that wouldn't be consistent with how those blocks normally work. But it would be easy to understand for the players.
I understand now that it's a lot of code but it seems possible we might get them someday. It's just a ton of work...
Rollback Post to RevisionRollBack
My projects:
-are abandoned for now. I might pick 'em up in the future.
For now i'm working on a private modpack that suit's my own playstyle.
I am gonna stay in modded 1.12.2 untill my potato dies. No mercy! :Q
The Meaning of Life, the Universe, and Everything.
Join Date:
6/5/2021
Posts:
50
Member Details
Would it really matter in terms of coordinated it would just give a .5 on the Y axis which is just a slightly larger way of counting on the Y axis 1,1.5,2,2.5,3,3.5 etc say it's a solid wood block it burns at the moment say it's a oak slab and birch slab it would still burn say it's an oak slab and cobblestone slab it would burn the wood and the cobble would remain say it was a wood slab on base a sand block on top and a wood slab on top and the top was torched the sand would protect the bottom slab say the fire started underneath the bottom slab would burn the sand block would drop and any flame on the ground would be extinguished under the sand so really all I'm asking is is for a .5 block height to be added to the Y axis rather than a solid block number
Would it really matter in terms of coordinated it would just give a .5 on the Y axis which is just a slightly larger way of counting on the Y axis 1,1.5,2,2.5,3,3.5 etc say it's a solid wood block it burns at the moment say it's a oak slab and birch slab it would still burn say it's an oak slab and cobblestone slab it would burn the wood and the cobble would remain say it was a wood slab on base a sand block on top and a wood slab on top and the top was torched the sand would protect the bottom slab say the fire started underneath the bottom slab would burn the sand block would drop and any flame on the ground would be extinguished under the sand so really all I'm asking is is for a .5 block height to be added to the Y axis rather than a solid block number
Block coordinates must be stored as integers (the block data is stored in an array, which can only use integer indices in Java, as well as most if not all other programming languages) so you are basically saying that the height limit should be doubled and most blocks be stored at multiples of 2, taking up a 1x2x1 (xyz) space - there is no other way around it; only entities (not even tile entities) can use decimal coordinates and at best you can use a tile entity or special block (like a double slab block) to render two different blocks in the same space. Either that, or add another "layer" to the block storage format that allows two different blocks to exist in the same space, much as they did with water in 1.13 - at the expense of resource usage and slower block data access, so a method that is specific to "double variant" slabs is most preferred (i.e. using a tile entity, which only has any impact if any such blocks are placed in the world, or "double slab" blocks for every possible combination, but as mentioned before you'll need a huge number of such blocks).
Ok I know half slabs that are the same block type stick together but if you make a half slab say of cobble or sandstone and try to place them one on top of another they will place an air gap in the top part of the bottom block. It would allow for better block detail building and off centring blocks.
I wonder how often this has been suggested. It's like a mystery. Will mojang ever fix halfslabs?
Have they even responded to this?
My guess is that they are afrait to break buildings from old maps. Could couse some uproar.
If i had a map i'd treasure becouse of that i just wouldn't update it or fix the broken slabs.
It's not like you can have only one world which is going to be griefed with every update.
My projects:
-are abandoned for now. I might pick 'em up in the future.
For now i'm working on a private modpack that suit's my own playstyle.
I am gonna stay in modded 1.12.2 untill my potato dies. No mercy! :Q
The reason why Mojang has not "fixed" this is simple - think of how many possible combinations of every type of slab there are - that's how many new blocks would need to be added, and what happens to the block properties when you mix different types of slabs, especially wood/stone (tool requirements, flammability, mining time, blast resistance, etc)? These issues are why this suggestion warrants a firm "no" from Mojang:
An alternative is to use a tile entity, which can render a virtually unlimited number of blocks with only one new block added (a special "combined slabs" block), which would have to only be created when different slabs are mixed (assuming it uses the "normal" block renderer and not "entity" renderer there would be no impact on FPS, though a large number would degrade chunk update time and memory usage since each tile entity stores not just the blocks it represents but its coordinates). There is still the issue of how to handle mixed block types (does a combination of wood and stone require a pickaxe? Does it burn? The fire code would need to be rewritten to be able to selectively burn only the wooden part, or have tools only be effective on the part the player is pointing at and drop that half instead of both halves, as double slabs currently do).
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
That's interesting information. Thank you.
Does it need to be so complicated?
What if the combined block takes the stats from the top slab? Lets say wooden slab on top and stone slab bottom.
That way both slabs would burn when exposed to fire, right?
I know that wouldn't be consistent with how those blocks normally work. But it would be easy to understand for the players.
I understand now that it's a lot of code but it seems possible we might get them someday. It's just a ton of work...
My projects:
-are abandoned for now. I might pick 'em up in the future.
For now i'm working on a private modpack that suit's my own playstyle.
I am gonna stay in modded 1.12.2 untill my potato dies. No mercy! :Q
Would it really matter in terms of coordinated it would just give a .5 on the Y axis which is just a slightly larger way of counting on the Y axis 1,1.5,2,2.5,3,3.5 etc say it's a solid wood block it burns at the moment say it's a oak slab and birch slab it would still burn say it's an oak slab and cobblestone slab it would burn the wood and the cobble would remain say it was a wood slab on base a sand block on top and a wood slab on top and the top was torched the sand would protect the bottom slab say the fire started underneath the bottom slab would burn the sand block would drop and any flame on the ground would be extinguished under the sand so really all I'm asking is is for a .5 block height to be added to the Y axis rather than a solid block number
Block coordinates must be stored as integers (the block data is stored in an array, which can only use integer indices in Java, as well as most if not all other programming languages) so you are basically saying that the height limit should be doubled and most blocks be stored at multiples of 2, taking up a 1x2x1 (xyz) space - there is no other way around it; only entities (not even tile entities) can use decimal coordinates and at best you can use a tile entity or special block (like a double slab block) to render two different blocks in the same space. Either that, or add another "layer" to the block storage format that allows two different blocks to exist in the same space, much as they did with water in 1.13 - at the expense of resource usage and slower block data access, so a method that is specific to "double variant" slabs is most preferred (i.e. using a tile entity, which only has any impact if any such blocks are placed in the world, or "double slab" blocks for every possible combination, but as mentioned before you'll need a huge number of such blocks).
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?