Minecraft Forums

Quote from Icy_Code»

Please make a 1.7.10 version.

Quote from AlgorithmX2»

Welcome to the Thread

[...]

Second, I don't intend on back-porting either mod to 1.7.10 or earlier so please do not ask.

Quote from C&B's FAQ page

Please Backport to 1.7.10, or I want some feature from the latest build on 1.8.

• I don't have the time to do this sort of thing but, heres the code feel free to try your hand at it.

Quote from Jake1702»

Why thank you so, so so very much!

In case you haven't got this implemented yet and still need it, here's my implementation:

Source code: https://gist.github.com/Phylogeny/40a20b4160fb369cb6261a55ad535223

JAR: https://www.dropbox.com/s/6i8n7yosi4t3nwb/cryospawn-1.7.10-1.0.0.jar?dl=0

If not, that's fine.

Quote from kirokadura»

Is there any configuration than can be applied in the mod so that a single "panel" of bits is enough to block light? Like if I make a room out of walls that are only 1 bit thick (or any thickness lower than 16, as long as it's a full "side" of the block) and don't want light from inside the room to leak to the outside.

No, there is no config for that. A chiseled block must be entirely full of bits with block states that return 'true' from isNormalCube() to be completely opaque (opacity 255). Even a single bit with a state that returns 'false' (like an air bit or glass bit) will cause the chiseled block to be completely transparent (opacity 0).

It would be nice if it were configurable by percentage like light emission is, though.

Quote from Zedner»

when blood magic 1.8.9-2.0.0-17 is installed i cant climb stair block that was made with chisels and bits, this block is same dimensions like vanilla stairs, so im not sure what mod is causing this problem.

I investigated and found that this was a bug with Blood Magic (one introduced in v2.0.0-17). In his event handler, WayofTime set the default player step height to 0.5f, since in previous versions of MC that was the default. It's since changed to 0.6f. I've just opened a GitHub issue about it.

Quote from Zedner >>
im curious if config option "balance settings" {I:bagStackSize=512 is editable or it has to be 512

The purpose of a config is to allow a value to be changed by a user; they are all editable. Also, you should use the config GUI ('Mods' from the main menu or 'Mod Options' from the pause menu), as there are often tooltips with additional information. This is the case here. The GUI tooltip reads "Stack size of bits in the bag: Minimum of 64, maximum of 99,999".

Quote from Zedner >>
what do i have to type here "D:bitLightPercentage=6.25" to make every glowstone bit to emit light?

It is a percentage. You get light with 6.25% of the bits filled if set to 6.25. If you want even a single bit to be able to emit light, it should be set to 0%.

I really take too long to write messages... The redundancy was not intentional. Sorry Algorithm.

Quote from Phylogeny»

I have just added this functionality to the Extra Bit manipulation addon for Chisels & Bits:

In addition to this page, information on Chiseled Armor can be obtained in-game by the following means:

• Holding the control key while hovering the cursor over a Chiseled Armor itemstack will display usage information.
• JEI will give basic information on how to import copies of blocks in-world into armor pieces.
• Pressing the question mark button in the top right of the Chiseled Armor GUI will enter help mode, where all relevant objects will render detailed help text when hovering the cursor over them. (this is a particularly useful and expansive source of information about Chiseled Armor).

That looks really nice, pretty soon we're going to be swimming in fantastic armors as well as all this awesome architecture.

Quote from Phylogeny»

That answers that. How optimized? Maximally.

Its been a while since I wrote the code for it. But I can't think of any cases off the top of my head that would resolve into cases with extra polygons, so it could very well be maximized. It does tend produce polygons that are longer, since the focus is on speed, and count, rather then count and surface area. A fair trade when the output is consumed only for rendering.


The method doesn't leave much room for error, and is optimized for speed with buckets based on face and distance and by extending the previous quad where applicable. This is done to minimize quad count early and then minimize search space for further merging.

-

Addendum, Since posting I do see a few cases where it can generate sub maximized results based on directional. But I do stand by that the CPU saved in generation probably is worth the few extra polygons generated. Fully optimizing poly-count would probably be quite the cpu intensive process.

Modern GPUs make short work of polygons, especially since they are batched into VBO's and DisplayLists; Minecraft is almost always CPU limited unless the player sets their view distance too high in any-case.

Quote from DerpSquad1O1»

Even though you told us not to, I'm a rebel so I'm going to throw this out there.

1.7.10 is the most popularly used mod version out there, and everyone else out there like me is greatly disappointed in you. It should be brought backwards.

EDIT: This is not a request, but a wise suggestion.