1. freddyagogog Ex-SMod
    ECC Sponsor Mayor ⛰️⛰️ Ex-EcoLegend ⚜️⚜️⚜️⚜️ Prestige ⭐ II ⭐ Premium Upgrade

    Joined:
    Jun 7, 2014
    Messages:
    886
    Trophy Points:
    53,910
    Gender:
    Male
    EcoDollars:
    $371,584
    Ratings:
    +513
    Minecraft Username:
    freddyagogo

    Brief Description:
    Found an error in "Skylord Hoe" since all the other tools from that kit are in &5 and the "Skylord Hoe" color code is set as &b

    Instructions:
    Looking and reading the item.

    How many times did you recreate this?:
    N/A

    Result:
    Color code naming error.

    Expected Result:
    &7[&5Skylord&7] &fHoe

    Evidence:

     
    #1 freddyagogog, Apr 1, 2018
    Last edited: Apr 1, 2018
  2. Founder Premium Upgrade

    Joined:
    Apr 5, 2011
    Messages:
    20,682
    Trophy Points:
    102,160
    Ratings:
    +15,143
  3. JamieSinn Retired Lead Administrator/Developer
    Builder ⛰️ Ex-Tycoon ⚜️⚜️⚜️ Premium Upgrade

    Joined:
    Jun 4, 2011
    Messages:
    5,517
    Trophy Points:
    78,090
    Gender:
    Male
    Ratings:
    +4,588
  4. Founder Premium Upgrade

    Joined:
    Apr 5, 2011
    Messages:
    20,682
    Trophy Points:
    102,160
    Ratings:
    +15,143
    Please let us know if this is fixed after our next Skyblock restart (should happen within 6 hours) @freddyagogo
    Report back tomorrow night Eastern Time.
     
  5. freddyagogog Ex-SMod
    ECC Sponsor Mayor ⛰️⛰️ Ex-EcoLegend ⚜️⚜️⚜️⚜️ Prestige ⭐ II ⭐ Premium Upgrade

    Joined:
    Jun 7, 2014
    Messages:
    886
    Trophy Points:
    53,910
    Gender:
    Male
    EcoDollars:
    $371,584
    Ratings:
    +513
    I can't use my /kit skylord, anyone else who can confirm?
     
  6. pokeball92870 PokeManiac
    Resident ⛰️ Ex-President ⚒️⚒️ Prestige ⭐ I ⭐ Premium Upgrade

    Joined:
    May 3, 2017
    Messages:
    787
    Trophy Points:
    26,010
    EcoDollars:
    $0
    Ratings:
    +1,547
    @andrewkm @freddyagogo
    Issue was with the other tools besides hoe.
    Saw the kit recently, can confirm this is fixed.