Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

LiquidBounce Forum

  1. Home
  2. Bug Reports
  3. Item cooldown

Item cooldown

Scheduled Pinned Locked Moved Bug Reports
2 Posts 2 Posters 24 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • rus109R Offline
    rus109R Offline
    rus109
    wrote last edited by
    #1

    I'll try to be as brief as possible.
    Item Cooldown isn't working correctly and is very confusing. Let's start from the beginning.

    1. The processing is incorrect – the entire cooldown you want to set needs to be reduced by ~0.08 (if I calculated everything correctly). Why? I don't know; that's just how Minecraft ticks work. More specifically, when we set, for example, 1 - 1, it doesn't actually hit when the cooldown is at 100%, but rather gives permission to hit (as far as I understand). For example, I set the Item Cooldown to 0.88 (according to Minecraft's cooldown, it's actually 0.96, but I explained above why it needs to be reduced by 0.08). The server counts the hit as 0.99999994 (i.e., slightly less than the full cooldown). We didn't hit at 100% of the cooldown, but we hit at 0.96, but the damage doesn't change. (In fact, it does, but that's how the ticks work.
      A full charge is 8 damage.
      A charge of 0.99999994 is 7.999999046325684 damage.
      This is a netherite sword.)
      So, we hit at 0.96 of the charge, but we were counted as 100% damage, and we still saved 25 milliseconds.
      I think I explained it terribly 😞

    2. Item Cooldown doesn't work with Always Criticals mode.
      Why? Because Always always wants to hit at full charge. Although a critical hit is possible starting at 84.8% charge (Well, you can't hit exactly at 84.8%. Why? I don't know, that's how ticks work).
      But we can hit, for example, at 92%. And a critical hit is possible because 92 is greater than the 84.8% threshold. But no matter what value we set for Item Cooldown (in Killaura), it will always hit at 100% (or 99.999994%, to be precise). Why would it be simple to always hit at 100% cooldown? Right? Not quite, well, maybe in principle you can hit at 100%, but still, liquid bounces are about flexibility. In any case, hitting before 100% and after 84.8% can save time, which can, for example, increase DPS.

    That's about all I wanted to say.

    1 Reply Last reply
    0
    • kawaiinekololisK Offline
      kawaiinekololisK Offline
      kawaiinekololis
      Admin
      wrote last edited by kawaiinekololis
      #2

      2.:

      What you are looking for is that Cooldown will also overwrite itself based on the situation of e.g. critical hit?

      Regarding Always Criticals Mode:
      I swear to god I will delete the Always Criticals Mode. There is a Smart Criticals Mode for a reason.

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      About
      • Terms of Service
      • Privacy Policy
      • Status
      • Contact Us
      Downloads
      • Releases
      • Source code
      • License
      Docs
      • Tutorials
      • CustomHUD
      • AutoSettings
      • ScriptAPI
      Community
      • Forum
      • Guilded
      • YouTube
      • Twitter
      • D.Tube
      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups