Jump to content


Photo

[Fixed] Already-seen movies preventing quest completion


  • Please log in to reply
4 replies to this topic

#1 Myrroddin

Myrroddin

    Glass Joe

  • New Members
  • 6 posts

Posted 10 June 2014 - 10:22 PM

I was doing the following three quest in Badlands:

  1. http://www.wowdb.com...-deathwing-came
  2. http://www.wowdb.com...-the-real-story
  3. http://www.wowdb.com...really-happened

And then I noticed DBM's feature of not showing a cinematic you have already seen prevented the second and third quests from being functional.

 

When you are on those quests, your character gets replaced by a playable cinematic character, and you perform the actions described in the quests' stories.

 

Once completing the first quest in the chain, DBM learns which movie it is, and thus never lets it be seen again. If you fail the first quest, or move onto the second or third quests, DBM automatically exits the cinematic and you cannot do the quests.

 

When I checked the saved variables for DBM, I saw a list of "MoviesSeen", but that doesn't help me because there is no description to indicate which movieID is which.

 

What I suggest to fix this is perform a zone check before exiting a cinematic. Assuming Blizzard adds more such quests, then exit the function that cancels movies if you are in x, y, or z zones. Badlands is zoneID 3.

 

Things might get complex if the player has the map open, but it can be done.



#2 MysticalOS

MysticalOS

    French Hacker

  • ♦ Administrators
  • 1138 posts
  • LocationGeorgia

Posted 10 June 2014 - 10:25 PM

The problem in first place is blizzard api blows. Because these movies don't have movie IDs available to API, blocking them is a royal pain. Map ID is far from accurate. I can probably fix this by disabling movie blocking outside of instances again. Just a shame, cause feature is useful for realm first leveling race. Since blizzard removed that anyways though I guess removing blocking outside of instances is the answer.



#3 Myrroddin

Myrroddin

    Glass Joe

  • New Members
  • 6 posts

Posted 12 June 2014 - 06:26 AM

Because of something I am working on unrelated to DBM, but related to maps and mapID, could you elaborate why mapID "is far from accurate" please? As far as I can tell, the mapIDs are immutable, and the only caveat is when the player has the map open, in which case:

  1. Save the open map to variable
  2. Close the map
  3. Get the mapID of the current zone
  4. Open map
  5. Set map to previous variable

Oh yes, it is a pain (thanks, Blizzard), but isn't that how it is done?



#4 Myrroddin

Myrroddin

    Glass Joe

  • New Members
  • 6 posts

Posted 12 June 2014 - 06:29 AM

I found something that might be better than checking for zone: http://wowpedia.org/API_IsInInstance ... If you aren't in an instance, then don't exit the movie.

 

God forbid Blizzard mixing the two for solo instances. Yikes!



#5 MysticalOS

MysticalOS

    French Hacker

  • ♦ Administrators
  • 1138 posts
  • LocationGeorgia

Posted 12 June 2014 - 07:25 AM

Without a MOVIE id, you cannot filter movies properly. Siege of Org for example is a single mapid with tons of different movies. as well as you've seen in bad lands, because they are all in same zone, it can't tell first movie from the last one (which is why it filtered all but first). It's also why movie filtering is disabled in SoO if you are on any of the visions quests.

 

The instance check is exactly what I did. It was originally that way in fact but I actually liked blocking movies out of instances and removed it because I wasn't aware of it breaking any zones until you pointed out badlands.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users