Jump to content

  • Quest giver update

    splinecl

    By splinecl

      • Main Category: Core / Mangos Daemon
      Sub-Category: Quest
      Version: 21.14
     Share

    When trying to turn in the quest "Ammo for Rumbleshot" it took a very long time, over a minute, of me standing around next to the quest turn in NPC "Hegnar Rumbleshot", before the golden quest "?" icon appeared over his head and I could turn in the quest.

    In the server log I saw this message at the time where I could finally turn in the quest: 

    WORLD: Received opcode CMSG_QUESTGIVER_STATUS_QUERY - for Player Rune (Guid: 6) to Creature (Entry: 1243 Guid: 265)

    How come this update took so long? If I didn't know that this was actually the correct quest turn in NPC, I would probably just have run past him. Is there any way to tune how often this status query is done?

    I have attached a screenshot of my standing next to the NPC with the quest and quest item.

    rumbleshot.png

     Share
    Go to bugs

    User Feedback

    Recommended Comments

    splinecl

    splinecl 0

    Posted (edited)

    It looks like the script controlling the group of dwarves around "Hegnar Rumbleshot" is interfering with the CMSG_QUESTGIVER_STATUS_QUERY message. As soon as the scripted event with the mortar crew ends, then the CMSG_QUESTGIVER_STATUS_QUERY opcode is received and handled. This also fits with what the log shows. 

    2018-10-11 22:09:24 DB-SCRIPTS: Process table `db_scripts [type = 3]` id 1061003, command 29 for source Creature (Entry: 10610 Guid: 269) (in world), target Creature (Entry: 10610 Guid: 269) (in world)
2018-10-11 22:09:24 WORLD: Received opcode CMSG_QUESTGIVER_STATUS_QUERY - for Player Oldtoxo (Guid: 8) to Creature (Entry: 1243 Guid: 265)
2018-10-11 22:09:24 WORLD: Sent SMSG_QUESTGIVER_STATUS for Creature (Entry: 1243 Guid: 265)
2018-10-11 22:09:35 Respawning...
2018-10-11 22:09:35 Creature (Entry: 721 Guid: 3611) enters grid[20,31]

    Here you can see the script 1061003 ends with command 29 right before CMSG_QUESTGIVER_STATUS_QUERY is handled.

    Edited by splinecl
    splinecl

    splinecl 0

    Posted

    Shouldn't the script 

    select * from db_scripts where id=1061003;

    Be triggered by the end of the quest "Ammo for Rumbleshot"?

    SELECT * FROM mangos0.quest_template where entry=5541;

    And not start playing just because players are near?

    splinecl

    splinecl 0

    Posted (edited)

    I have made the following local workaround. 

    delete from mangos0.db_scripts where script_guid in (1403,1798);

    These scripts remove and add the UNIT_NPC_FLAG_GOSSIP and UNIT_NPC_FLAG_QUESTGIVER from "Hegnar Rumbleshot". This makes it possible to complete the quest without having to wait for all the mortar team scripts to complete.

    I still think the triggers for the mortar team are wrong, but can not figure out how to make it trigger from completing the quest. So this is the only workaround I have been able to come out with for now.

    Edited by splinecl
    Necrovoice

    Necrovoice 72

    Posted

    Understanding that this is a local fix for you.

    The above is not a correct way of fixing this issue.  What we should be doing is reworking the script to start after this quest (6641) has been handed in. Something that you have stated above.  I will look into this when I have some free time, however  If you happen to get it working correctly before I do, I will be happy to push it to the git mangos repo and credit you for the work.
    Thanks for reporting this :)



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

Contact Us

To contact us click here
You can also email us at [email protected]

Privacy Policy | Terms & Conditions

Repositories

The Link to the master list
of MaNGOS repositories:
Copyright © getMaNGOS. All rights Reserved.

This website is in no way associated with or endorsed by Blizzard Entertainment®
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use