Code Monkey home page Code Monkey logo

libdullasswingtimer's People

Contributors

uffefl avatar

Watchers

 avatar

libdullasswingtimer's Issues

Wrong clipping reported when switching targets

When switching targets during auto shot cooldown no actual clipping occurs but an erroneous player facing clip of 0.5 sec is reported.

When switching targets during auto shot cast some clipping does occur, but no matter what the same player facing clip of 0.5 sec is reported.

"not in line of sight" error bugs the addon

Piggymorph โ€” Today at 12:06 AM
fwiw if I go out of line of sight and wait 0.5 sec for the auto to go off, I get the "not in line of sight" error and that bugs the addon, it won't show the 0.5 sec cast time for the subsequent shots until I restart auto shot

Movement detection does not detect jumping in place

Expected behavior:

If you jump in place during auto shot cast it should freeze the auto shot cast while in the air and restart the auto shot when you land on the ground (and report the clipped time). (Same behavior as moving on the ground.)

Observed behavior:

Jumping in place does not interrupt the auto shot cast bar, but instead the cast bar just stays full until the shot goes off (and no clipping is reported).

Project Epoch workaround for cast times for hunter spells

Currently Project Epoch has a bug where the cast time for hunter shots (Steady Shot, Aimed Shot and Multi-Shot) does not benefit correctly from ranged haste, but the tooltip and the values from GetSpellInfo() pretend that they do.

The correct formula, and the one in use on the tooltips, is cast time = base time / (100% + ranged haste). The one currently in use is cast time = (base time - 0.5 sec) / (100% + ranged haste) + 0.5 sec, which basically means that the first 0.5 seconds of the cast does not benefit from ranged haste.

This means that the actual cast times are slower than the advertised cast times. To provide guides for when to fit in casts without clipping auto shot this means that LibDullasSwingTimer has to do this calculation instead of relying on data provided by the game client.

When Project Epoch fixes this bug I would like to remove this code.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.