Nice job, I liked the original suggestion. Could you make it so that breaking blocks with the hammer drops microcubes?
Not without editing Notch's classes, or doing really, really, dangerous and unstable things.
Quote from MrBaconsock »
Damn Elarnon, you went ahead and made different microblock materials compatible with each other within the same structure!!
Oh, did I ? This was intended to stay in my development version for a while and was absolutely not tested, so there might be a certain number of bugs. Each of those blocks with multiple materials is taking six times the memory of a regular microblock, though.
Quote from MrBaconsock »
- When you place a wool microblock and then combine it with another of a different colour, the second placed block turns into the same colour as the first.
- When you combine a wool microblock of any colour to an already placed microblock, it automatically turns into white wool.
These are because I forgot to copy the metadata when switching for a particular block from the single-material to the multi-materials implementation. But again, this was not intended for this version originally.
Quote from yoshi9048 »
Other things I have tested: This does some funny things with water, if you plan correctly; you can create an awesome deck for your house or awesome dock for water. Again, water does some really funny things with eighth blocks; be careful.
Yes, that's because water needs an empty block to propagate, and technically speaking, the block with microcubes is considered a full block. That's the same thing for slabs or stairs, and I fear there's nothing I can do for that one, you will have to deal with it.
Quote from Badprenup »
I just finished making a video showcasing the new features. I'll edit this post when the video is uploaded so you can update the OP if you want with the new video included.
The new video have been added to the OP. See what I said to MrBaconsock about the different materials in the same block issue (problem of copying metadata, will be fixed) and to yoshi9048 about the water ; about fire on eighth blocks, I fear that would be hard to implement, as fire is considered a block. Technically speaking, these two issues can be fixed (not really quickly, though), but I'm not sure I will fix them, as I don't find them that annoying compared to the amount of work it would need to fix them :tongue.gif:
found a glitch.
if you do this with stone eigths.
suddenly it changes and you have.. nvm just retested, its kinda at random, if you place stone eights youll see what i mean, at random times it places a bedrock, instead of a stone eight. as in FULL bedrock block.
edit- its with any block.
found a glitch.
if you do this with stone eigths.
suddenly it changes and you have.. nvm just retested, its kinda at random, if you place stone eights youll see what i mean, at random times it places a bedrock, instead of a stone eight. as in FULL bedrock block.
edit- its with any block.
I was unable to reproduce this. Could I have a few more informations about your system (OS, mods installed, etc.) ? Whatever, the full bedrock block (which you should be able to walk through) is indicating that there was a really annoying error emptying the full block... Can't understand why this particular pattern would cause this, though.
Quote from Canotsa »
Please remove the strike through :wink.gif:
It's annyoing to look at.
At y=81, all microblocks take on an invisible/sky skin. I'll test elsewhere to confirm.
*edit* Tested again, apparently, you can only build microblocks 15 high; this may have to do with the included 4 bits. In the mean time; caveat emptor. blocks 27 and 28 were normal, 29 and 30 were invisible. */edit*
I'll continue to test and see if a whole block helps remove this limit.
Alright, there's a limit to the amount of microblocks you can build without a whole block to anchor it.
This anchor distance is highly variable though, and I don't know the exact numbers.
What I do know is, until there is a bug fix (if there is a bug in the first place), this further reinforces eighth blocks as a detailing mod (it's entire design and purpose).
At y=81, all microblocks take on an invisible/sky skin. I'll test elsewhere to confirm.
*edit* Tested again, apparently, you can only build microblocks 15 high; this may have to do with the included 4 bits. In the mean time; caveat emptor. blocks 27 and 28 were normal, 29 and 30 were invisible. */edit*
I'll continue to test and see if a whole block helps remove this limit.
Quote from yoshi9048 »
Alright, there's a limit to the amount of microblocks you can build without a whole block to anchor it.
This anchor distance is highly variable though, and I don't know the exact numbers.
What I do know is, until there is a bug fix (if there is a bug in the first place), this further reinforces eighth blocks as a detailing mod (it's entire design and purpose).
Oh no. I hoped I would never heard of that. It happened to me on a random basis, but only when trying via MCP's integrated startclient, and never on my real minecraft.jar, so I hoped it came from MCP or something. Will have to fix that, then. It also sometimes happened to me on a line on the ground. And it also sometimes happened when forcing refresh of a block that was good before. I have really no idea of what it comes from, but I will do what I can to fix it (unless, as I fear it is, it comes from some very strange bug in the internals of minecraft itself).
At y=81, all microblocks take on an invisible/sky skin. I'll test elsewhere to confirm.
*edit* Tested again, apparently, you can only build microblocks 15 high; this may have to do with the included 4 bits. In the mean time; caveat emptor. blocks 27 and 28 were normal, 29 and 30 were invisible. */edit*
I'll continue to test and see if a whole block helps remove this limit.
Quote from yoshi9048 »
Alright, there's a limit to the amount of microblocks you can build without a whole block to anchor it.
This anchor distance is highly variable though, and I don't know the exact numbers.
What I do know is, until there is a bug fix (if there is a bug in the first place), this further reinforces eighth blocks as a detailing mod (it's entire design and purpose).
Oh no. I hoped I would never heard of that. It happened to me on a random basis, but only when trying via MCP's integrated startclient, and never on my real minecraft.jar, so I hoped it came from MCP or something. Will have to fix that, then. It also sometimes happened to me on a line on the ground. And it also sometimes happened when forcing refresh of a block that was good before. I have really no idea of what it comes from, but I will do what I can to fix it (unless, as I fear it is, it comes from some very strange bug in the internals of minecraft itself).
An anchor is basically just a whole block(of any type, could be a stair, half block, any actual ID block) to reset the system.
It was actually quite funny, placing a roof with a wooden anchor worked just fine. When I removed the anchor, it went invisible, placed the anchor again; it popped into life.
If it makes you feel any better, you still collide with it and the player can still walk on it. It can be oh-so-exploitable for players who want to create that invisible bridge to their castle.
An anchor is basically just a whole block(of any type, could be a stair, half block, any actual ID block) to reset the system.
It was actually quite funny, placing a roof with a wooden anchor worked just fine. When I removed the anchor, it went invisible, placed the anchor again; it popped into life.
If it makes you feel any better, you still collide with it and the player can still walk on it. It can be oh-so-exploitable for players who want to create that invisible bridge to their castle.
Yes I noticed this behaviour with what you call anchors, yet I don't understand why it behaves like that, so I will continue to investigate until I find why it works that way. I also noticed that placing water instead of a regular block do display the water, but don't enable the microblocks to be displayed.
I agree with many people—this mod rocks! could you make the micro-cobble, etc. have textures the size of their of their orginial block, like slabs and stairs have it for example?
How is it that your storing the data for the blocks, I imagine the usual method wouldn't be able to store that much data.
I don't use the usual method, I use a tile entity (the same thing that is used for chests, for instance). No, I don't know if minecraft will be able to deal with a huge number of them correctly or not, the future will tell us, and this mod can also be seen as a test for this.
Quote from Craftineer »
I agree with many people—this mod rocks! could you make the micro-cobble, etc. have textures the size of their of their orginial block, like slabs and stairs have it for example?
That's the original way I wanted them to be displayed, but I only succeeded in having really, really strange things (like, the correct size, but not the correct position, and others things that made the blocks look really strange depending on your texture pack).
One more thing about this odd disappearing microcubes bug : what I feel is really strange is that they are still collidable and everything, and the displaying method is called. Really strange thing.
One more thing about this odd disappearing microcubes bug : what I feel is really strange is that they are still collidable and everything, and the displaying method is called. Really strange thing.
That's in invisible rendering glitch (not part of the mod, it's the game's code that has this bug), just like what happens to some fences. Solution: place a block next to it.
Oh, ok. Didn't know about that glitch, but it steel feels strange ! Won't try to fix it then, however.
I really don't like things like that without an explanation, though.
Edit : Yay ! Thanks to that thread, I found the explanation and fixed the bug (which really was a stupid one...) !
It seems I shouldn't have based my rendering code off the stairs rendering one...
This deserves an award now. v0.1 was great, but it needed some fixin'; v0.2 is like having your cake and eating it, too.
There still are some problems, though. The hammer icon remains a leather helmet; I don't know if this is related to the mods I have installed (Too Many Items is one of them), but I'll try re-modding my .jar to check. Tomorrow.
Please can you add micro-redstone. The amount of downloads will go up by a lot, and I mean alot.
After a few investigating, I fear that would be as hard to implement as the pocket-dimension thing I read about on another thread, because I would have to recode most redstone-related things. That's do-able, but would be a pain in the ass, I think.
There still are some problems, though. The hammer icon remains a leather helmet; I don't know if this is related to the mods I have installed (Too Many Items is one of them), but I'll try re-modding my .jar to check. Tomorrow.
Strange. Maybe you have *that* much mods installed that there is no indices available for textures, but otherwise this shouldn't happen.
If it persists after re-modding your .jar, more informations about your system (OS, mods installed with exact versions, output of launching minecraft via a terminal, etc.) would be welcomed (PMs are the preferred way).
You should stick the eighth blocks in the world generater to see what happens. lol. I want to know if itll overload the engine. :tongue.gif:
No, I won't. That's never have been a goal for me ; I believe eighth blocks (in particular, due to some of their limitations unless I recode most parts of the whole minecraft engine - which I, of course, won't -, or I switch the implementation to a more restrictive one as of creative potential but with better integration into minecraft's engine - which I may do, but don't take it for account) should only be used to enhance your constructions, and not as a building material of its own.
Ive not tested this yet but i have a few questions:
1. can you places torchs on an eighth block?
2. can you place the 1/8 blocks under a block or will it leave a 1/8th gap between them?
3. can you place fences on 1/8 blocks?
If not there suggestions. :biggrin.gif:
1. Not in the published version, partially in the development version (which should be published... er, some time in the future). That is, you can place a torch on any face (up or sides) if it's full, but it won't be in the same block as the microblocks. Another problem I have is about the lighting system ; currently the eighth blocks are letting the light pass through, and I'm not sure I will ever find a way to solve that, so actually allowing torches *inside* the block itself (apart from the need to recode most of the torch-related things into the microblocks...) would be like... kinda hard.
2. Not sure I understood what you meant, but you can have a eighth block on the upper part of the block.
3. Same as for 1.
Strange. Maybe you have *that* much mods installed that there is no indices available for textures, but otherwise this shouldn't happen.
If it persists after re-modding your .jar, more informations about your system (OS, mods installed with exact versions, output of launching minecraft via a terminal, etc.) would be welcomed (PMs are the preferred way).
A list I made says I have eight mods installed. After painstakingly reinstalling those mods, Too Many Items listed the tiered hammers; this means the mod is working properly. :tongue.gif:
This NEEDS to be implemented in SMP one way or another. Have you thought of making 1/16 blocks?
I really hope your kidding. The main reason 1/8 blocks work is because its cube root is a whole number. The next perfect cube root we could possibly do is 27; even then, that is too numerous for practical purposes.
Because 8s cube root is two, the length of each sub-block would be 1/2 of the original. 16s cube root is 2.53, meaning the length of each sub-block would be 1/2.53 of the original.
Edit: Until now, I haven't actually thried v0.2 because of the error. I knew the changes, too. When I started testing block placement, my face lit up for awhile. Minecraft is a game of blocks, and this refines the idea so so many things can be implemented with just this.
Also, with the current block ID placement, I think we can pick a higher number and take up two or so IDs for more 1/8 blocks (like glass).
Not without editing Notch's classes, or doing really, really, dangerous and unstable things.
Oh, did I ? This was intended to stay in my development version for a while and was absolutely not tested, so there might be a certain number of bugs. Each of those blocks with multiple materials is taking six times the memory of a regular microblock, though.
These are because I forgot to copy the metadata when switching for a particular block from the single-material to the multi-materials implementation. But again, this was not intended for this version originally.
Yes, that's because water needs an empty block to propagate, and technically speaking, the block with microcubes is considered a full block. That's the same thing for slabs or stairs, and I fear there's nothing I can do for that one, you will have to deal with it.
The new video have been added to the OP. See what I said to MrBaconsock about the different materials in the same block issue (problem of copying metadata, will be fixed) and to yoshi9048 about the water ; about fire on eighth blocks, I fear that would be hard to implement, as fire is considered a block. Technically speaking, these two issues can be fixed (not really quickly, though), but I'm not sure I will fix them, as I don't find them that annoying compared to the amount of work it would need to fix them :tongue.gif:
if you do this with stone eigths.
suddenly it changes and you have.. nvm just retested, its kinda at random, if you place stone eights youll see what i mean, at random times it places a bedrock, instead of a stone eight. as in FULL bedrock block.
edit- its with any block.
I was unable to reproduce this. Could I have a few more informations about your system (OS, mods installed, etc.) ? Whatever, the full bedrock block (which you should be able to walk through) is indicating that there was a really annoying error emptying the full block... Can't understand why this particular pattern would cause this, though.
You're right. Removed.
At y=81, all microblocks take on an invisible/sky skin. I'll test elsewhere to confirm.
*edit* Tested again, apparently, you can only build microblocks 15 high; this may have to do with the included 4 bits. In the mean time; caveat emptor. blocks 27 and 28 were normal, 29 and 30 were invisible. */edit*
I'll continue to test and see if a whole block helps remove this limit.
OFFICIAL POSTING/REPLYING GUIDELINES
UNOFFICIAL POSTING GUIDE (PRT)
UNOFFICIAL REPLYING GUIDE (FTC)
This anchor distance is highly variable though, and I don't know the exact numbers.
What I do know is, until there is a bug fix (if there is a bug in the first place), this further reinforces eighth blocks as a detailing mod (it's entire design and purpose).
OFFICIAL POSTING/REPLYING GUIDELINES
UNOFFICIAL POSTING GUIDE (PRT)
UNOFFICIAL REPLYING GUIDE (FTC)
Oh no. I hoped I would never heard of that. It happened to me on a random basis, but only when trying via MCP's integrated startclient, and never on my real minecraft.jar, so I hoped it came from MCP or something. Will have to fix that, then. It also sometimes happened to me on a line on the ground. And it also sometimes happened when forcing refresh of a block that was good before. I have really no idea of what it comes from, but I will do what I can to fix it (unless, as I fear it is, it comes from some very strange bug in the internals of minecraft itself).
An anchor is basically just a whole block(of any type, could be a stair, half block, any actual ID block) to reset the system.
It was actually quite funny, placing a roof with a wooden anchor worked just fine. When I removed the anchor, it went invisible, placed the anchor again; it popped into life.
If it makes you feel any better, you still collide with it and the player can still walk on it. It can be oh-so-exploitable for players who want to create that invisible bridge to their castle.
OFFICIAL POSTING/REPLYING GUIDELINES
UNOFFICIAL POSTING GUIDE (PRT)
UNOFFICIAL REPLYING GUIDE (FTC)
Yes I noticed this behaviour with what you call anchors, yet I don't understand why it behaves like that, so I will continue to investigate until I find why it works that way. I also noticed that placing water instead of a regular block do display the water, but don't enable the microblocks to be displayed.
I don't use the usual method, I use a tile entity (the same thing that is used for chests, for instance). No, I don't know if minecraft will be able to deal with a huge number of them correctly or not, the future will tell us, and this mod can also be seen as a test for this.
That's the original way I wanted them to be displayed, but I only succeeded in having really, really strange things (like, the correct size, but not the correct position, and others things that made the blocks look really strange depending on your texture pack).
One more thing about this odd disappearing microcubes bug : what I feel is really strange is that they are still collidable and everything, and the displaying method is called. Really strange thing.
That's in invisible rendering glitch (not part of the mod, it's the game's code that has this bug), just like what happens to some fences. Solution: place a block next to it.
I really don't like things like that without an explanation, though.
Edit : Yay ! Thanks to that thread, I found the explanation and fixed the bug (which really was a stupid one...) !
It seems I shouldn't have based my rendering code off the stairs rendering one...
There still are some problems, though. The hammer icon remains a leather helmet; I don't know if this is related to the mods I have installed (Too Many Items is one of them), but I'll try re-modding my .jar to check. Tomorrow.
After a few investigating, I fear that would be as hard to implement as the pocket-dimension thing I read about on another thread, because I would have to recode most redstone-related things. That's do-able, but would be a pain in the ass, I think.
Strange. Maybe you have *that* much mods installed that there is no indices available for textures, but otherwise this shouldn't happen.
If it persists after re-modding your .jar, more informations about your system (OS, mods installed with exact versions, output of launching minecraft via a terminal, etc.) would be welcomed (PMs are the preferred way).
No, I won't. That's never have been a goal for me ; I believe eighth blocks (in particular, due to some of their limitations unless I recode most parts of the whole minecraft engine - which I, of course, won't -, or I switch the implementation to a more restrictive one as of creative potential but with better integration into minecraft's engine - which I may do, but don't take it for account) should only be used to enhance your constructions, and not as a building material of its own.
1. Not in the published version, partially in the development version (which should be published... er, some time in the future). That is, you can place a torch on any face (up or sides) if it's full, but it won't be in the same block as the microblocks. Another problem I have is about the lighting system ; currently the eighth blocks are letting the light pass through, and I'm not sure I will ever find a way to solve that, so actually allowing torches *inside* the block itself (apart from the need to recode most of the torch-related things into the microblocks...) would be like... kinda hard.
2. Not sure I understood what you meant, but you can have a eighth block on the upper part of the block.
3. Same as for 1.
[EDIT] when I said 1/16, I meant 1/64. =P
A list I made says I have eight mods installed. After painstakingly reinstalling those mods, Too Many Items listed the tiered hammers; this means the mod is working properly. :tongue.gif:
I really hope your kidding. The main reason 1/8 blocks work is because its cube root is a whole number. The next perfect cube root we could possibly do is 27; even then, that is too numerous for practical purposes.
Because 8s cube root is two, the length of each sub-block would be 1/2 of the original. 16s cube root is 2.53, meaning the length of each sub-block would be 1/2.53 of the original.
Edit: Until now, I haven't actually thried v0.2 because of the error. I knew the changes, too. When I started testing block placement, my face lit up for awhile. Minecraft is a game of blocks, and this refines the idea so so many things can be implemented with just this.
Also, with the current block ID placement, I think we can pick a higher number and take up two or so IDs for more 1/8 blocks (like glass).