mojira.dev

Stephen R Hudson

Assigned

No issues.

Reported

MC-71354 Librarians can offer same book twice Works As Intended MC-70190 F3 + T leaves you in chat mode Fixed MC-70075 Commands not accepting custom language file translations Invalid MC-68454 Mobs glitch through floor (upon being hit or chunk reload) Duplicate MC-68276 Creepers suffering from premature eruption Duplicate MC-68214 Minecarts not reversing down slopes Incomplete MC-66398 Bizzare Endermen behaviour / no-aggro Incomplete MC-65369 No loaded activity in spawn chunks Incomplete MC-65117 Can't place signs on signs Duplicate MC-65099 Server crash in virgin nether Duplicate MC-62889 Unable to use minecart with hoppers to gather items from Nether Portals Incomplete MC-56177 Massive lag induced by carts on players lazy chunk fringe Incomplete MC-55996 Server: Regular freezing, chunk_loader chewing all CPU Duplicate MC-52967 Acacia Wood Plank not using translation file. Invalid MC-52966 Incorrect user created if playing offline. Invalid MC-52965 F3 BL reports head block, not foot block Duplicate

Comments

Very random, obviously the chances are low, even for the more common books. It has only happened once, although I regularly breed villagers and unlock their tiers - especially librarians. Again, because of the random percentages involved, I expect it to be quite some time before I reproduce it. I euthanised the villager in question, he had no books on offer that I didn't already have.

From what I know of the mechanics, it would only affect Librarians and their books, as that is the only item class that is capable of being offered multiple times on different tiers, ergo requires a specialised check just for this instance.

Also happening in 1.8

I strongly disagree with you. The entire point of I18N is to make it accessible in other languages. My example is fairly trivial, but a Chinese user should be able to enter /杀 @e[类=鸡]. As we have these strings in the L12N file, there is no reason why they can't be parsed before being handed to the core. Speakers of other languages shouldn't have to learn English in order to use commands.

I repeated the add / delete doors process that caused issues before (now running pre2) and it worked just fine.

Its a mechanism you can construct.

Are you using a 'keep-loaded' portal chucker?

Still in pre2, also affects redstone

Still happening in pre-1

yes, me too for pre-release. Albeit at reduced frequencies.

The OreSum Server is set to achingly rock hard, and zombies are happily smashing down doors. This guy offed himself about 6-8 blocks down the staircase from me. Damage from his blast was pretty normal I think; smashed a stone or stone brick block in every direction & popped a few levers off walls. There are other examples in other environments as well, this is just the most obvious as I was AFK and was returning when I heard him banging...

An extrusion of a supplied custom model...

Still an issue in 32d. Activating a lever on the top of an upside down slab breaks the lever.

Sounds like the ticking_entity problem

There also seems to be an issue with custom acacia doors, insofar as there is no _inner file, and the applied transparency seems hard-coded? Shouldn't these 'thin' blocks with transparency (doors / trapdoors) just be simple extrusions not requiring an inner face?

Seems a bit better in 14w32d, but still getting the x-ray effect and short delay, at a minimum, on breaking. Touch wood, I haven't had a long delay like before. For me, it is mainly affecting block removal, not placement.

These 2 crashes were probably triggered by removing a number of doors from a village. HTH.

Part of this issue is the mystery tick lag. I had no automation setup, no other tasks consuming CPU etc. It's pretty close to a virgin world.

A newly created, previously unentered Nether dimension

The block updates correctly on either:

  • a block update next to it
    or

  • going out of the view cone and re-entering it.

While a broken block is erroneously present, player can move through it.

I'm getting 100+ FPS on an i7-2600K beast, and still getting both placement and breaking delays from my local server on 14w31a. Placement delay at least shows a wirefarm 'selection grid' of the block (like selecting an invisible block). Arguably less frequent.