Jump to content

Chucksta

getMaNGOS Retired Staff
  • Posts

    552
  • Joined

  • Last visited

  • Days Won

    1
  • Donations

    0.00 GBP 

Everything posted by Chucksta

  1. Both [B]Details[/B] field and [B]Objectives[/B] field are empty in the quest_template table for this quest. Going in-game to see this for myself, from that perspective. [B]EDIT:[/B] This has been fixed already. That tomb starts a chain of quests. And the quest text and objectives is in place. [B][SIZE=3][COLOR="#800080"]This Thread Can Be Closed[/COLOR] [/SIZE][/B]
  2. Necklace found in: [B]Glinting mud[/B]: Entry: 154357 GUIDs: 31121, 20836, 110001, 110002 [url]http://www.wowwiki.com/Hilary's_Necklace[/url] Coordinates may put the mud out of the game world. I'll check just as soon as I can. [B]EDIT[/B]: The Glinting mud piles spawn perfectly fine. Tested all locations. Has this been fixed already... a mystery for Mr. Holmes, me thinks! Quest entry looks okay. Will now test as a Horde toon... All okay as a Horde char. Test appeared as it should at each stage. This has been fixed already :) [SIZE=3][B][COLOR="#800080"]This Thread Can Be Closed[/COLOR][/B][/SIZE]
  3. [quote=cabfever][url]http://outridersguild.proboards.com/thread/586[/url] Seems legit[/quote] Excellent, thanks, cabfever :D And I now have a couple of links to good resources to add to my bookmarks, thanks :) [SIZE=3][COLOR="#800080"][B]This Thread Can Be Closed [/B][/COLOR][/SIZE]:D
  4. [quote=cabfever]The instance needs to be redone.[/quote] Amazing, easy to forget just how nasty vanilla was! Although I did enjoy that insanity :) I guess we can consider this issue resolved. Are you happy with the drop rates for the gems: 13%, 17%, and 26% at present in the database ? No idea how they came up with those drop rates. I have been unable to locate the true drop rates :(
  5. Nice resource, cabfever, the link :D I reckon the drop rates are wrong in the database. That link you posted says 100%, and claims to be vanilla, so unless I can find otherwise, I will put forward and PR the fix, which will include: [B]Gemstone of Smolderthorn[/B] UPDATE `creature_loot_template` SET `ChanceOrQuestChance`='100' WHERE `entry`='9237' and`item`='12335'; [B]Gemstone of Spirestone[/B] UPDATE `creature_loot_template` SET `ChanceOrQuestChance`='100' WHERE `entry`='9196' and`item`='12336'; [B]Gemstone of Bloodaxe[/B] UPDATE `creature_loot_template` SET `ChanceOrQuestChance`='100' WHERE `entry`='9568' and`item`='12337'; [B][SIZE=4][COLOR="#B22222"]FORGET THAT[/COLOR][/SIZE][/B] I did not read the drop rate change link! Weird, do these elites respawn, or does the instance have to be redone?
  6. Drop rate chance for these gems are set to 13%, 17%, and 26% I believe they should be 100%. I'll check...
  7. PR has now been submitted that allows Misha to join Rexxar on his travels. It includes the following SQL scripts to get Misha going: [B]creature[/B] table: UPDATE `creature` SET `position_x`='447.226471', `position_y`='1766.857422', `position_z`='22.992067', `orientation`='3.143952', `MovementType`='2' WHERE `guid`='590005'; [B]creature_linking[/B] table: INSERT INTO `creature_linking` (`guid`, `master_guid`, `flag`) VALUES ('590005', '29113', '8835'); All done now, as far as Rexxar and Misha are concerned :D [B][SIZE=3][COLOR="#800080"]This Thread Can Now Be Closed[/COLOR][/SIZE][/B]
  8. I just tried this out on my local server, which is Rel20, and cloned yesterday, and I am afraid I had this issue. Skinned and looted and the corpse did not despawn. This was on wolves in Goldshire. I do recall that fix being discussed, and the proof is in the above link. Very odd. [B]EDIT:[/B] I just checked the creature.cpp file, and that fix has not been applied. It is still the faulty code. So, either the merge has not occurred yet, or I am losing the plot... don't answer that! :D [B][SIZE=3]So, the above linked commit not merged with Rel20 core, as yet ?[/SIZE][/B]
  9. Confirmed. I went on Cosmic Ray and tried it out on the mobs in Durotar, and they failed to despawn after skinning and looting the hide.
  10. [B][COLOR="#0000CD"]Rainer Schmelzeisen[/COLOR][/B] has come up with the answer: [B]creature_linking table[/B] You enter the main NPC's guid and that of its buddy, then they will stick together. I'll test this out now, as I need to figure out the correct flag to use in that table.
  11. Still working on the spawn coordinates of the egg. This little is kinda annoying me .. oops, sorry, teddy :( The Z ordinate is obviously being incorrectly calculated, but I cannot locate where this is happening in the code, as yet. I will , little !!!! The coordinates are obviously based on the location of the player. Anyway, still at it. This quest will be doable once the commit I made is merged. Or action what I stated above, as to how to fix it.
  12. Not forgotten about this :) re Misha the pet bear. I have figured out how to give Rexxar a companion/pet, but the result is that pet walking way way way behind him, so not ideal. Currently checking out the spells, to see if that will set off a light bulb moment.
  13. Chance of spawn was set to -100%. UPDATE `creature_loot_template` SET `ChanceOrQuestChance`='100' WHERE `entry`='11876' and`item`='13542'; Will apply fix and PR :D [B]EDIT:[/B] Pull Request has now been made for MaNGOSZero and MaNGOSOne with this fix [B][SIZE=3]This Thread Can Now Be Closed[/SIZE][/B]
  14. Pull Request with fix has now been made. [B][SIZE=3]This Thread Can Now Be Closed[/SIZE][/B]
  15. Confirmed (stated by Unkle Nuke), the target was incorrectly set to 0 (creature_ai_scripts), which is the thing being attacked, when it should be 0, which is itself: [B]FIX[/B] UPDATE `creature_ai_scripts` SET `action1_param2`='1' WHERE `id`='201401'; Will now apply and PR.
  16. Pull Request has now been made for the fix: including - UPDATE `creature_ai_scripts` SET `action1_param2`='0' WHERE `id`='258301'; [B][SIZE=3]This Thread Can Be Closed[/SIZE][/B]
  17. I changed the spell to 992, but it still gives that error :-( [B]EDIT:[/B] Fixed it :-) Parameter 2 (target) of action 1 (ACTION_T_CAST) in the creature_ai_scripts was set to 1, when it should have been 0. I'll PR the fix :D
  18. This group loot issue has been fixed. Re a thread on Scarshield Quartermaster, I tested this out on that NPC and the one in the Human start area (Northshire) and each member of the group was able to loot, letter in one case (Quartermater) and head in the other (Northshire). [B][SIZE=3]YOU CAN CLOSE THIS THREAD[/SIZE][/B]
  19. I've found out how to resize the egg, which was wayyyyy too big UPDATE `mangos`.`gameobject_template` SET `size`='0.2' WHERE `entry`='161513'; But it still spawns up high (accessible/clickable, though): [IMG]http://s29.postimg.org/bqy5u7zt3/floatingegg.jpg[/IMG] [B]EDIT (07 December 2014)[/B] - [COLOR="#FF0000"]This has been found to only happen on my machine!!! :( So not an issue! :)[/COLOR]
  20. [B][SIZE=4]PR applied with fix.[/SIZE][/B] The correct text entry in the npc_text table exists, but there is also a 2nd text entry linked to the NPC, that contains the "Missing US Text" text. The system was picking up the offending text entry instead of the correct one. The offending text entry was not used by anything else so I removed it, and also removed the link to it from the NPC, in the gossip_menu table. Tested and working :) [B][SIZE=3]EDIT - database had been updated with the fix, so I deleted the PR[/SIZE][/B] This issue has been resolved. [B][SIZE=3]THIS THREAD CAN BE CLOSED[/SIZE][/B]
  21. [B]Confirmed[/B] [B]Locating the offending entry:[/B] creature_template (Entry) -> creature_template (GossipMenuId) -> Gossip_menu (Entry) -> Gossip_menu (text_id) -> npc_text (ID)
  22. Tested the above script from Elarose in game, and it worked :) Pull Request actioned with these changes made to the database including the addition of an update script. [B][SIZE=3]THIS THREAD CAN BE CLOSED[/SIZE][/B]
  23. A fix has been applied for the group loot issue. Just to be sure, I went in with a group of 2 and then a group of 5, and each time all members were able to loot the item :D [B][SIZE=3]THIS THREAD CAN BE CLOSED[/SIZE][/B]
  24. A Pull Request has now been made for this fix, on all cores :D The egg, although spawned up high, is reachable. I have not as yet figured out which code causes it to be spawned.
  25. [B]FIX FOUND[/B] Issue is due to the quest's entry ([B]3861[/B]) in the [B][COLOR="#008000"]quest_template[/COLOR][/B] table The quest's [B][COLOR="#008000"]SpecialFlags [/COLOR][/B]field is set to[B][COLOR="#B22222"] 1[/COLOR][/B], when it should be [B][COLOR="#008000"]0[/COLOR][/B]. I'll sort this out for all databases that will require it (Zero to Four). [B][SIZE=3][COLOR="#B22222"]Extra issue:[/COLOR][/SIZE][/B] the egg appears about 1 foot above a human's height in the air. I'll see what I can do about it. I guess its coordinates are scripted, seeing as the egg could appear anywhere a chicken is. I'll do a quick check on the coords issue, and if it's not an obvious/quick fix, I'll implement and PR the quest fix before looking into the coords one further.
×
×
  • 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