Jump to content

Arkadus

Members
  • Posts

    93
  • Joined

  • Last visited

  • Donations

    0.00 GBP 

Bug Comments posted by Arkadus

  1. DELETE FROM `creature_movement` WHERE `id`='30639' and`point`='9';
    DELETE FROM `creature_movement` WHERE `id`='30639' and`point`='8';
    UPDATE `creature_movement` SET `point`='8' WHERE `id`='30639' and`point`='10';
    UPDATE `creature_movement` SET `point`='9' WHERE `id`='30639' and`point`='11';
    UPDATE `creature_movement` SET `point`='10' WHERE `id`='30639' and`point`='12';
    UPDATE `creature_movement` SET `point`='11' WHERE `id`='30639' and`point`='13';
    UPDATE `creature_movement` SET `point`='12' WHERE `id`='30639' and`point`='14';
    UPDATE `creature_movement` SET `point`='13' WHERE `id`='30639' and`point`='15';
    UPDATE `creature_movement` SET `point`='14' WHERE `id`='30639' and`point`='16';
    UPDATE `creature_movement` SET `point`='15' WHERE `id`='30639' and`point`='17';

  2. Yeah in vanilla you could unlearn any proffession anytime but had to start again at 0. So you could specialize in axesmith, swordsmith or hammersmth. But you only had a choice to unlearn the whole profession, so you lose all blacksmithing recipes you learned and the skill etc... But in TBC they changed it so you could unlearn swordsmithing and still keep blacksmithing and all the recipes except the swordsmith specific ones and you could respec to axesmith or hammersmith and vice-versa. You could also unlearn your whole blacksmith profession aswell.

  3. There is an error here aswell where it says;


    switch (pCreature->GetEntry())
    {
    case NPC_LUCIFRON:
    if (m_auiEncounter[TYPE_GARR] == DONE)
    {
    pCreature->Despawn();
    break;
    }


    Should actually be;


    switch (pCreature->GetEntry())
    {
    case NPC_LUCIFRON:
    if (m_auiEncounter[TYPE_LUCIFRON] == DONE)
    {
    pCreature->Despawn();
    break;
    }

  4. FYI i made a mistake with the SQL update with:

    UPDATE `creature_template`
    SET `FactionHorde` = 55, `FactionAlliance` = 55
    WHERE `Entry` = 15436 AND `Entry` = 12385;


    is actually supposed to have "OR" instead of "AND" this is for the target dumies so you cant attack them and they still get destroyed by the mortar,
    this was my fault:

    UPDATE `creature_template`
    SET `FactionHorde` = 55, `FactionAlliance` = 55
    WHERE `Entry` = 15436 OR `Entry` = 12385;

  5. It sets a bunch of creatures that shouldnt be skinnable or lootable, for instance the panthers in ZG panther boss fight. The demented druids from the emerald dragon fight. Various other things like a pet cat, it shouldnt be skinnable even though you technically cant kill it. Also there is a sheep id in there because sheep's were not skinnable in vanilla and the deleted id's are simply 2 of the loot tables for a few of these creatures that is no longer used.

  6. Indeed it took me about 6 hours to generate all those fixes. The only difference between spell 72 and 11972 was that 72 was cast after the time set in the params and 11972 was cast only as a reaction to its target if the began casting a spell and couldnt cast it again until the time params had past. Counterspell had to be updated on a number of NPC's because they were using the wrong spell id.

  7. Heres all my fixes that i implemented into my server for the ai script errors, do what you want with it and i cant explain it but i basicly used other scripts as templates and tested them all out on a live server before making the changes permanent;

    UPDATE `creature_ai_scripts`
    SET `action1_param2` = 1, `action1_param3` = 0, `event_flags` = 1, `event_param3` = 15000, `event_param4` = 30000
    WHERE (`id` = 43101 OR `id` = 446601 OR `id` = 463702 OR `id` = 536401 OR `id` = 562301 OR `id` = 598201 OR `id` = 1474801 OR `id` = 178703 OR `id` = 255603 OR `id` = 260602 OR `id` = 264906 OR `id` = 402402 OR `id` = 648803 OR `id` = 702702 OR `id` = 727404 OR `id` = 779703) AND `action1_param1` = 7160;

    UPDATE `creature_ai_scripts`
    SET `action1_param1` = 8242
    WHERE `id` = 184605 AND `action1_param1` = 15655;

    UPDATE `creature_ai_scripts`
    SET `action1_param2` = 0
    WHERE `event_type` = 10 AND `action1_type` = 12 AND `action1_param1` = 15138;

    UPDATE `creature_ai_scripts`
    SET `action1_param1` = 20537, `action1_param2` = 1, `action1_param3` = 0, `event_flags` = 1, `event_param1` = 15000, `event_param2` = 30000
    WHERE (`action1_param1` = 15122 OR `action1_param1` = 20537) AND `event_type` = 13 AND `action1_type` = 11;

    UPDATE `creature_ai_scripts`
    SET `action1_param2` = 1, `action1_param2` = 0, `event_flags` = 1
    WHERE (`action1_param1` = 12555 OR `action1_param1` = 15615 OR `action1_param1` = 15621 OR `action1_param1` = 11978 OR `action1_param1` = 15614 OR `action1_param1` = 25788) AND `event_type` = 13 AND `action1_type` = 11;

    UPDATE `creature_ai_scripts`
    SET `action1_param2` = 1, `action1_param2` = 0, `action1_param3` = 0, `event_flags` = 1, `event_param1` = 4000, `event_param2` = 8000
    WHERE (`id` = 184504 OR `id` = 184605) AND `action1_param1` = 8242;

    UPDATE `creature_ai_scripts`
    SET `action1_param2` = 1, `action1_param2` = 0, `action1_param3` = 0, `event_flags` = 1, `event_param1` = 15000, `event_param2` = 30000
    WHERE (`id` = 1432105 OR `id` = 1432305 OR `id` = 1432605 OR `id` = 58702 OR `id` = 154004 OR `id` = 166404 OR `id` = 1383908 OR `id` = 312902 OR `id` = 319204 OR `id` = 373906 OR `id` = 432806 OR `id` = 560106 OR `id` = 580903 OR `id` = 606906) AND `action1_param1` = 11972 OR `action1_param1` = 72;

    UPDATE `creature_ai_scripts`
    SET `action1_type` = 32, `action2_type` = 32, `action3_type` = 32, `action1_param2` = 1, `action2_param2` = 1, `action3_param2` = 1, `action1_param3` = 4, `action2_param3` = 5, `action3_param3` = 6
    WHERE `id` = 684602;

    UPDATE `creature_ai_scripts`
    SET `action1_param2` = 1, `action1_param3` = 0
    WHERE `id` = 1082406 OR `id` = 1082407 OR `id` = 1571802;

    UPDATE `creature_ai_scripts`
    SET `action1_param1` = 11976
    WHERE `id` = 1082407;

    UPDATE `creature_ai_scripts`
    SET `event_type` = 9, `event_flags` = 1, `event_param1` = 0, `event_param2` = 5, `event_param3` = 7000, `event_param4` = 14000, `action1_param2` = 1, `action1_param3` = 0
    WHERE `action1_type` = 11 AND `action1_param1` = 11978;

    UPDATE `creature_ai_scripts`
    SET `action1_param2` = 0, `action1_param3` = 0
    WHERE `id` = 1145502;

    UPDATE `creature_template`
    SET `AIName` = ""
    WHERE `Entry` = 4509;

    UPDATE `creature_ai_scripts`
    SET `event_flags` = 0
    WHERE `id` = 1521501;

    UPDATE `creature_ai_scripts`
    SET `action2_type` = 32, `event_chance` = 5
    WHERE `id` = 327402 OR `id` = 327502 OR `id` = 339703;

    UPDATE `creature_ai_scripts`
    SET `action1_type` = 32, `action2_type` = 0
    WHERE `id` = 177203 OR `id` = 177303;

    UPDATE `creature_ai_scripts`
    SET `action2_type` = 0, `action2_param2` = 0
    WHERE `id` = 494903;

    DELETE FROM `creature_ai_scripts` WHERE `id` = 1018206;

  8. I didnt get any of those stats from any mangos release it was based off a website and the statistics people posted around 2007 which wasnt long after vanilla. If you goto the original post there is a reference that i linked to the website with all those statistics. I do believe that mangos r19 or r20 has mostly the same stats but there are some differences.

  9. spell id 28771 - this i the buff someone would have who carries the frostfire set. Elemental vulnerability from the frostfire regalia set bonus, 20% proc chance for each damaging spell that hits a target.

    [URL="http://www.wowhead.com/spell=28771/elemental-vulnerability"]http://www.wowhead.com/spell=28771/elemental-vulnerability[/URL]

    spell id 28772 - This i the debuff that would be on the effected target of the frostfire set bonus when hit by a damaging spell and successfully procced. It would last for 30 seconds and once the first damaging spell to hit after this procs, increases the spell damage modifier of that spell by +200 considering the spell power coefficiency ratio so for instance if the next spell to hit was 'moonfire' it would only increse the damage of the spell by like 75 and elemental vulnerability would dissapear from the target.

    [URL="http://www.wowhead.com/spell=28772#see-also-other"]http://www.wowhead.com/spell=28772#see-also-other[/URL]

  10. Xenithar is right, what i remember about vanilla is, you wouldnt see any stealthed enemies behind your range of vision which was about an angle of 135 degrees. If an enemy was within this view range they would be visible before you got into aggro range unless you were lower level than the stealthed mob. If there were stealthed enemies behind your view range, you would start getting attacked out of no where. One other thing i remember in vanilla is, when you see a stealthed creature and get within aggro range, they would remain stealthed and you would see them approaching your character at about the same speed as a walk/very slowly and you would have a flag for your character that your in combat. It was after TBC when they changed this so enemies break stealth when you get into aggro range of a stealthed enemy. The moment you see a stealthed enemy's model you were able to click on them and see their name/template. When you see a stealthed enemy and turn away so the enemy you just saw is outside your view range, you could still have them targeted and see them for roughly 5 seconds or so before they would dissapear.

×
×
  • 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