Announcement

Collapse

Forum Rules

  • No flaming or derogatory remarks, directly or through insinuation.
  • No discussion, sharing or referencing illegal software such as hacks, keygen, cracks and pirated software.
  • No offensive contents, including but not limited to, racism, gore or pornography.
  • No excessive spam/meme, i.e. copious one liners in a short period of time, typing with all caps or posting meme responses (text/image).
  • No trolling, including but not limited to, flame incitation, user provocation or false information distribution.
  • No link spamming or signature advertisements for content not specific to Dota 2.
  • No Dota 2 key requests, sell, trade etc.
  • You may not create multiple accounts for any purpose, including ban evasion, unless expressly permitted by a moderator.

  • Please search before posting. One thread per issue. Do not create another thread if there is an existing one already.
  • Before posting anything, make sure you check out all sticky threads (e.g., this). Do not create new threads about closed ones.
  • It is extremely important that you post in correct forum section.

  • Balance discussion only in Misc.
  • All art related (such as hero model) feedbacks go to Art Feedback Forum.
  • All matchmaking feedback should go here: Matchmaking Feedback
  • All report/low priority issues should go here: Commend/Report/Ban Feedback
  • No specific workshop item feedback. These should go to workshop page of that item.
  • When posting in non-bugs section (such as this), use [Bugs], [Discussion] or [Suggestion] prefix in your thread name.



In case you object some action by a moderator, please contact him directly through PM and explain your concerns politely. If you are still unable to resolve the issue, contact an administrator. Do not drag these issues in public.



All rules are meant to augment common sense, please use them when not conflicted with aforementioned policies.
See more
See less

Bug/Feature request for panorama ability API

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Bug/Feature request for panorama ability API

    Create lina hero, her ultimate in panorama will be Entities.GetAbility(heroId, 3), but Game.GetKeybindForAbility(3) will give a keybind for a settings slot number four, not ability slot.
    If this is rational, then we should have a way to get a Keybind from ability entity. Also, please add some way to get quickcast keybind.

  • #2
    Not sure I understand, could you elaborate a bit?

    Comment


    • #3
      What I'm saying is ability index and keybind index do not correlate, so there is no fail-proof way to tell the keybind of specific ability.

      Comment


      • #4
        Ahhh, thanks for the clarification!

        I went through the API and I can't seem to find a way to get the actual slot the ability has taken.

        Game.GetKeybindForAbility( integer iSlot ) -> iSlot is related to actual ability slots ( pic, so 5 would return an ultimate )
        GetAbility.Entities.GetAbility( integer nEntityIndex, integer nSlotIndex ) -> nSlotIndex is related to the ability number on the hero ( so for lina, 3 would return the ultimate )

        Given that heroes can have hidden abilities etc, as DoctorGester requested it would be neat to have an API call that would return the keybind of an ability entity along with the one we have. In addition, perhaps a rename of of Game.GetKeybindForAbility() is warranted? Seeing as usage of slots is not consistent and can easily be mistaken.

        Comment

        Working...
        X