Meringue
- meringue
- meringue
- Europe/Stockholm
- Yes
- No
MC-91710
Deleted Comment:
Not resolved in 15w44b (i think?).
Planted and found sugar canes nearly always show age 0, sometimes 1, rarely 2. the other blockstates (age 3 to 15) are VERY rare. Even canes right before growing another on top show those values instead of 15. Ages are inconsistent in the stacked blocks. Sometimes there are randomly aged canes inbetween staying at those values. Screenshots attached with colored textures for various ages (green = age: 0, blue = age: 1, red = age: 3).A freshly-planted cane – and a cane which has just grown cane above it – each have an age of 0.
The age is incremented at random intervals.
At age 15, a cane may try to grow more cane above it.Maybe i just misunderstand this? In that case – sorry.
reeds.json{ "multipart": [ { "when": {"age": 0 }, "apply": {"model": "reeds" } }, { "when": {"age": 1 }, "apply": {"model": "reeds_1" } }, { "when": {"age": 2 }, "apply": {"model": "reeds_2" } } ] }
This happens also for non-HD (128x128px) custom fonts. It seems the spacing for the original "default.png" is used.
Yes please, would be great if fixed soon.
This means that most texture pack authors will have to remove their custom fonts until then.
Thanks a lot Grum! I assume by garbage you mean extra pixels in front of the letter images? Will a mcmeta file be needed for this fix?
What does "non-0 alpha values" mean? I have a also a few stray characters that i can't get rid of no matter what i try.
Edit: Duh, got it - anything else than pure white and opaque will cause errors. Thanks, works perfectly! http://i.imgur.com/MY0lamv.png
Not only the transparency is important, it seems also important that the visible pixels have to be pure white.
My font had a very light yellow tint (artistic reason, not a mistake), this caused problems - seems that the boundaries weren't detected properly anymore (as you mentioned already).
Not a complaint! I just felt like adding this to your list.
Confirmed for 14w31a.
How about adding up/down conditions? Would of course cause a few more models.
Something like this (hope i get it right)...
{ "multipart": [ { "when": { "north": false, "east": false, "south": false, "west": false, "up": false, "down": true }, "apply": { "model": "iron_bars_post_end_up" } }, { "when": { "north": false, "east": false, "south": false, "west": false, "up": true, "down": false }, "apply": { "model": "iron_bars_post_end_down" } }, { "when": { "north": false, "east": false, "south": false, "west": false }, "apply": { "model": "iron_bars_post" } }, { "when": { "north": true, "east": false, "south": false, "west": false }, "apply": { "model": "iron_bars_cap" } }, { "when": { "north": false, "east": true, "south": false, "west": false }, "apply": { "model": "iron_bars_cap", "y": 90 } }, { "when": { "north": false, "east": false, "south": true, "west": false }, "apply": { "model": "iron_bars_cap_alt" } }, { "when": { "north": false, "east": false, "south": false, "west": true }, "apply": { "model": "iron_bars_cap_alt", "y": 90 } }, { "when": { "north": true }, "apply": { "model": "iron_bars_side" } }, { "when": { "north": true, "up": false, "down": true }, "apply": { "model": "iron_bars_edge_up" } }, { "when": { "north": true, "down": false, "up": true }, "apply": { "model": "iron_bars_edge_down" } }, { "when": { "east": true }, "apply": { "model": "iron_bars_side", "y": 90 } }, { "when": { "east": true, "up": false, "down": true }, "apply": { "model": "iron_bars_edge_up", "y": 90 } }, { "when": { "east": true, "down": false, "up": true }, "apply": { "model": "iron_bars_edge_down", "y": 90 } }, { "when": { "south": true }, "apply": { "model": "iron_bars_side_alt" } }, { "when": { "south": true, "up": false, "down": true }, "apply": { "model": "iron_bars_edge_up_alt" } }, { "when": { "south": true, "down": false, "up": true }, "apply": { "model": "iron_bars_edge_down_alt" } }, { "when": { "west": true }, "apply": { "model": "iron_bars_side_alt", "y": 90 } }, { "when": { "west": true, "up": false, "down": true }, "apply": { "model": "iron_bars_edge_up_alt", "y": 90 } }, { "when": { "west": true, "down": false, "up": true }, "apply": { "model": "iron_bars_edge_down_alt", "y": 90 } } ] }uvlock is completely broken in 15w44b.
Screenshot 15w44a_vs_15w44b_uvlock shows coal_block with custom blockstate.json in previous and current snapshot.
{ "variants": { "normal": [ { "model": "coal_block" }, { "model": "coal_block", "x": 90, "uvlock": true }, { "model": "coal_block", "y": 90, "uvlock": true } ] } }Not fixed – the issue is confirmed in 15w45a.
The blockstate in my test is still the same as above, uvlock:true does not work as in 1.8.8 and older pre 1.9 snapshots, means that the textures are rotated even when uvlock is true.
Screenshot brokenuvlock_15w45a.png added.