LogBlock Enchantment Visual Glitch

Discussion in 'Help & Support / Errors & Bugs' started by killrdarknes, Jan 10, 2020.

  1. killrdarknes

    killrdarknes The Final Act
    ECC Sponsor EcoLeader ⛰️⛰️⛰️ Ex-EcoLegend ⚜️⚜️⚜️⚜️ Prestige ⭐ V ⭐ Premium Upgrade

    Joined:
    Apr 9, 2012
    Messages:
    2,230
    Trophy Points:
    74,660
    Gender:
    Female
    EcoDollars:
    $93,445
    Ratings:
    +1,185
    Minecraft Username: killrdarknes

    Brief Description: Basically, place any enchanted tool in a chest that contains an enchantment which has various levels (unbreaking, efficiency, fortune, etcetcetc.)
    LogBlock the chest, and hover over the item name corresponding to the enchanted item.
    Notice that the LogBlock data displays the enchanted item as having enchantment levels all one higher than the actual enchantment.
    For instance, place an efficiency 3, unbreaking 2 pickaxe into a chest, then use LogBlock to see "player blahblah placed x1 DIAMOND_PICKAXE". Hover over "DIAMOND_PICKAXE"; the tooltip will show the item as an efficiency 4 unbreaking 3 pickaxe.

    Instructions: ^^

    How many times did you recreate this?: 3 times with 3 separate tools.

    Result: Seeing an eff5 unb3 fort3 pickaxe as an eff6 unb4 fort4 pickaxe in the LogBlock data.

    Expected Result: Seeing an eff5 unb3 fort3 pickaxe as an eff5 unb3 fort3 pickaxe in the LogBlock data.

    Evidence:

    discovered by @TM_iBeast
     
  2. andrewkm

    Founder Premium Upgrade

    Joined:
    Apr 5, 2011
    Messages:
    20,679
    Trophy Points:
    102,160
    Ratings:
    +15,143
    Please test this again after our 1.15.1 update, and report back if it still occurs.
    Unfortunately we cannot fix logblock issues until 1.15.1 is launched as we are mid-update.
     
    • Informative Informative x 1
    • List
  3. andrewkm

    Founder Premium Upgrade

    Joined:
    Apr 5, 2011
    Messages:
    20,679
    Trophy Points:
    102,160
    Ratings:
    +15,143
    Lobby is now on 1.15.1
    After testing this on the lobby, I cannot reproduce it.
    As such I'll have to say... fixed, but report back after 1.15.1 :)