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

Known bugs

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #76
    Updated first post with tower status bug. If anyone works out a better description please let me know and I'll update!

    Comment


    • #77
      Currently seeing the following issues:


      In MatchId = 153541960

      Tower Barracks info missing:


      <tower_status_radiant>0</tower_status_radiant>
      <tower_status_dire>1796</tower_status_dire>
      <barracks_status_radiant>0</barracks_status_radiant>
      <barracks_status_dire>0</barracks_status_dire>


      Also some abilityUpgrade confusion in the same match:

      For the Player with HeroId = 80 Lone Druid:

      <ability>
      <ability>5416</ability>
      <time>1070</time>
      <level>11</level>
      </ability>

      <ability>
      <ability>5415</ability>
      <time>535</time>
      <level>6</level>
      </ability>

      We have both 5415 and 5416 which point to two separate things in the npc_abilities file:

      lone_druid_true_form"
      {
      // General
      //-------------------------------------------------------------------------------------------------------------
      "ID" "5415" // unique ID number for this ability. Do not change this once established or it will invalidate collected stats.
      "AbilityName" "lone_druid_true_form"
      "AbilityBehavior" "DOTA_ABILITY_BEHAVIOR_NO_TARGET"
      "AbilityType" "DOTA_ABILITY_TYPE_ULTIMATE"

      lone_druid_true_form_druid"
      {
      // General
      //-------------------------------------------------------------------------------------------------------------
      "ID" "5416" // unique ID number for this ability. Do not change this once established or it will invalidate collected stats.
      "AbilityName" "lone_druid_true_form"
      "AbilityBehavior" "DOTA_ABILITY_BEHAVIOR_NO_TARGET | DOTA_ABILITY_BEHAVIOR_HIDDEN"
      "AbilityType" "DOTA_ABILITY_TYPE_ULTIMATE"

      Maybe this is because he takes the second level of true form while he is in true form? But from a Developer point of view it needs to map to 5415 to be consistent.

      Also as others have noted in this thread the times on the AbilityUpgrades correspond to when the match Captain's Mode begins not when the actual match begins which makes them virtually useless. I love Dota 2, Valve, and Steam but I hope these issues are worked out before new features are added to the api. It is very hard to use an API to do things automatically when you have to go over the results by hand to look for missing information or adjust certain values to not be weird as in the case of the AbilityUpgrade notes above.

      We also have the issue of sometimes winning teams in the Leagues disconnect before the losing team so the match shows as lost in the API but they actually won it. However this is more of an issue with professional match regulation rules than the API but is annoying to deal with at the API level. If developers point out these matches to Valve could the radiant_win flag be set to the correct value according to the League result?

      Currently I feel that if I automate downloading data it would just be inaccurate and have to be verified by hand which makes me a sad panda

      Edit - My post above is a bit negative and I do not want to be negative. Valve, how can I, a .net developer who writes web services and middle tier code all day, help make your api better? Is the problem that sometimes the game saves the data and it is messed up or is the actual data fine and the api is buggy reading the correct data? How can the people who use the api and read these forums contribute positive changes? Every time we see a bug should we submit it somehow? Just let me and others know the most effective ways that we can make the api more reliable and we will help.

      Thanks,
      Last edited by jwilsonw; 03-25-2013, 05:14 PM. Reason: content

      Comment


      • #78
        jwilsonw, I bet the 0/0 barracks status you're seeing is the "Dire Barracks status showing as a copy of Radiant Barracks Status" bug that myself and takua were discussing a few days ago. It looks like radiant lost all their towers/barracks, and dire still had some, but Dire showed the same status that Radiant had (0).

        I agree, there's a lot of issues with the API. Valve is a company, designed around making profit. Spending valuable developer time on improving the API (something which cannot be directly monetized) is essentially throwing money away. Thus, I think us developers have to come up with tricks to work around this sort of thing. In your Lone Druid example, the two skill codes should be the same - we just need to treat them as the same value in our code. I think your hypothesis is correct (lone druid skilled his ult while in ult form).

        It makes me wonder if the same exists for Chen or Shadow Fiend (heroes who have multiple buttons they could press to improve the "same" skill). If so, we'd have to track that somehow.

        It's not easy, but i'd say it's easier than having to do it all by hand. We're developers afterall! My job all day is to provide accurate and complete data from an inaccurate and incomplete database. When I get home and work on the API, the weaknesses in their code are easy to work around, by comparison. Plus, with the community here, there's lots of people willing to help. Let us know if you run into any difficult issues - don't get discouraged!

        Comment


        • #79
          Originally posted by Aardvarki View Post
          It makes me wonder if the same exists for Chen or Shadow Fiend (heroes who have multiple buttons they could press to improve the "same" skill). If so, we'd have to track that somehow.
          I think I've seen it with KOTL and Illuminate being leveled up in Spirit Form before. The Skill Build had the skill id for Spirit Form illuminate rather than regular illuminate if I recall correctly.
          datdota.com -- Dota 2 Stats for the Professional Scene

          Comment


          • #80
            Would be nice if valve could add function to get upcoming official matches. Something similar to ingame calendar.
            Last edited by JohnnyAjax; 04-25-2013, 10:15 AM.

            Comment


            • #81
              Originally posted by JohnnyAjax View Post
              Would be nice if valve could add function to get upcoming official matches. Something similar to ingame calendar.
              I'm not sure when this method was added, but it now exists to do exactly what you're asking.

              http://wiki.teamfortress.com/wiki/We...ledLeagueGames

              Comment


              • #82
                Originally posted by RJackson View Post
                I'm not sure when this method was added, but it now exists to do exactly what you're asking.

                http://wiki.teamfortress.com/wiki/We...ledLeagueGames
                Looks like new method and not documented in "THINGS YOU SHOULD KNOW BEFORE STARTING" topic, but atm returns empty games array. Same with GetMatchHistory and tournament_games_only=1 - status = 1 and no matches. But queries by league_id works.

                Comment


                • #83
                  Originally posted by JohnnyAjax View Post
                  Looks like new method and not documented in "THINGS YOU SHOULD KNOW BEFORE STARTING" topic, but atm returns empty games array. Same with GetMatchHistory and tournament_games_only=1 - status = 1 and no matches. But queries by league_id works.
                  Isn't that expected behaviour when there are no live tournaments?

                  Comment


                  • #84
                    Originally posted by jimmydorry View Post
                    Isn't that expected behaviour when there are no live tournaments?
                    Nah, scheduled = future matches, not on right now.
                    I think it's so we can build an "upcoming matches" calendar like the one in the client.


                    This method isn't fully implemented I think, hence it hasn't been announced anywhere yet.

                    Chances are somebody on the wiki checks http://wiki.teamfortress.com/wiki/We...pportedAPIList after each patch and documents any new methods.
                    The API Bible: Things You Should Know Before Starting API Development

                    Comment


                    • #85
                      Originally posted by MuppetMaster42 View Post
                      Nah, scheduled = future matches, not on right now.
                      I think it's so we can build an "upcoming matches" calendar like the one in the client.


                      This method isn't fully implemented I think, hence it hasn't been announced anywhere yet.

                      Chances are somebody on the wiki checks http://wiki.teamfortress.com/wiki/We...pportedAPIList after each patch and documents any new methods.
                      My bad... should have actually looked at the full name of the method. I was thinking of the getLiveLeagueGames

                      Comment


                      • #86
                        How many of these bugs have been fixed or even acknowledged? So far I see 4 from 5months ago.

                        Comment


                        • #87
                          As mentioned here:
                          is it considered a bug, that league matches were not returned when we search for match history?
                          Or "match history" is intended for Public Matchmaking matches only?

                          Comment


                          • #88
                            In GetMatchHistory :

                            -there is no more player_name
                            -game_mode isn't working
                            -date_max / date_min should'nt be rounded so you can find matches finest

                            Comment


                            • #89
                              It looks like GetMatchHistory's date_max and date_min parameters are being ignored, can somebody double check?

                              Comment


                              • #90
                                Originally posted by aiedail92 View Post
                                It looks like GetMatchHistory's date_max and date_min parameters are being ignored, can somebody double check?
                                I'm having the same problem. It started sometime between yesterday afternoon and this morning.

                                Comment

                                Working...
                                X