Jump to content

Almost Night

Donator
  • Posts

    90
  • Joined

  • Last visited

  • Days Won

    3
  • Donations

    200.00 GBP 

Everything posted by Almost Night

  1. I have checked the source code as well now and couldn't find the problem. I also checked MaNGOS Two, going back to the source code of 2017 and it all seemed fine. After checking MaNGOS Zero ingame with rel 22.01.25 I can confirm that this is NOT a problem in Zero. I have checked MaNGOS Two ingame with rel 22.01.06 as well and could reproduce the problem at the same spot. In fact, it seems to be a problem with the mobs showing as gray while they should be green. The same bear (Felwood, level 47) is green in Zero, but gray in Two. Player level: 57 Mob level: 48 Gray level: Player level - 1 - Player level / 5 = 45 In Two it seems to be 49 for the same player level. Does anyone know if GetColorCode (https://github.com/mangostwo/server/blob/master/src/game/Object/Formulas.h#L65) is actually used somewhere or if the decision for the mob color is done client-side?
  2. MaNGOS Zero is based on WoW Classic from 2004, not the NuClassic from 2019. Furthermore the bug report was given on MaNGOS Two, which is Wrath of the Lich King, so calculations might have changed. Anyways, NuClassic gives some good clues on bugs or missing content. So I followed that clue and did some research on my own and the last entry on Wowpedia before the release of Burning Crusade states the same as it was in the other bug report: https://wow.gamepedia.com/Mob_experience?oldid=228414 But it wasn't quoted fully. As the Zero Difference states: And: Especially "Mob Level > Gray Level" is what seems to be missing here. This description hasn't changed on Wowpedia up to the day. I second that as a wrong implementation of the experience calculation. When a mob is gray, it shouldn't give any XP to the player. Thanks for being stubborn.
  3. Maybe it's simply just the GM mode activated? Can you describe: What have you tried? (as detailed as possible) What did you expect? What did actually happen instead?
  4. Tested on deDE: Works like a charm! Thank you.
  5. We've stumbled over a problem with the extractors in the current v0.22 build downloaded from GitHub (https://github.com/mangoszero/server/releases/download/v22.01.14/MangoszeroServer_x64_release.zip). @LordIcon was using the deDE client to run the extractors. I could reproduce the same error with deDE and enUS clients. Steps to reproduce the error: Download latest build from https://github.com/mangoszero/server/releases/download/v22.01.14/MangoszeroServer_x64_release.zip Extract into a folder Copy all files from "tools"-directory into deDE/enUS client folder Run extractors in the order map-extractor.exe, vmap-extractor.exe, mmap-extractor.exe Move folders (dbc, maps, mmaps, vmaps) into the server folder Database installation + configuration Run mangosd.exe The file "000.vmtree" exists in the given folder. Let me know if you need more information to confirm.
  6. https://classic.wowhead.com/quest=1462/earth-sapta https://classic.wowhead.com/quest=1463/earth-sapta
  7. ID 133202 Part of the original text for that quest (Quest ID 714) is missing. It should be Yes, yes, yes. Just a moment.$B$B<Lotwil continues to work on some kind of contraption.> Since I only translated according to the given text, it would be great if that could be changed for the German translation as well: Ja, ja, ja. Nur einen Moment.$B$B<Lotwil setzt seine Arbeit an irgendeiner Art von Apparat fort.> ID 133248 There's a missing gender differentiation in the English text: Ah, yes. Another traveler seeking something from the dwarves.$B$B$GSire:Ma'am;, I'm truly sorry, but I've no time to answer meaningless questions right now. Also 269937 might be a duplicate without the gender differentiation. ID 133260 Another missing gender in the English text differentiation: Oh. Greetings, $Gbrother:sister;.$B$BAnd praise to the dwellers beneath. ID 137642 Can't find the entry anymore, since I can't lookup specific IDs in MAGNET. I just made a note here: got weird construct that looks like a typo in a break `$Bb` (and maybe duplicate of 135901) ID 270419 Can't find the entry anymore, since I can't lookup specific IDs in MAGNET. I just made a note here: got missing breaks ID 133786 Can't find the entry anymore, since I can't lookup specific IDs in MAGNET. I just made a note here: should be split into 012- and ---3 since it refers to Northern Barrens there's already Translation ID 270057 with the correct sentence ID 133880 Can't find the entry anymore, since I can't lookup specific IDs in MAGNET. I just made a note here: should be split into 012- and ---3 there's already Translation ID 270090 with the correct sentence
  8. Can you add a possibility to setup recurring donations? I'd rather donate once a month to keep the project running instead of donating whenever I remember that I wanted to donate from time to time.
  9. There is a wrong `RequestItemsText` within the quest data of Fire Sapta (Quest ID 1464): UPDATE `quest_template` SET `RequestItemsText`=NULL WHERE `entry`=1464; This text is already correctly set within the `Objectives`.
  10. There are two missing texts in the Earth Sapta (Quest ID 1462 and 1463) quest for Zero, One and Two: UPDATE `quest_template` SET `OfferRewardText`='Take this and remember, it is sacred.' WHERE `entry`=1462; UPDATE `quest_template` SET `OfferRewardText`='I give you one in good faith. You already proved yourself once, but me tinkin\' you should be more careful in the future.' WHERE `entry`=1463; Might have to update locales_quest / MAGNET translations accordingly.
  11. The quest "Root Samples" (Quest ID 866) activates the collection of "Root Sample" (Item ID 5056) from specific game objects introduced just for this quest. Right now within the database of Zero, One and Two this is set to the loot templates of the standard rather than the specific game objects. (e.g. game objects Silverleaf ID 1617 vs. Silverleaf ID 3725) Since the game objects are placed within the Barrens correctly, this can easily be fixed by removing the item from the currect gameobject_loot_templates and adding it to the loot templates of the quest specific game objects: -- Remove wrong loot template associations (gameobjects not in Barrens) DELETE FROM `gameobject_loot_template` WHERE `item` = 5056; -- Add new loot template associations for Barrens gameobjects INSERT INTO `gameobject_loot_template` (`entry`, `item`, `ChanceOrQuestChance`, `groupid`, `mincountOrRef`, `maxcount`, `condition_id`) VALUES (2511, 5056, -40, 0, 1, 1, 0), (2512, 5056, -40, 0, 1, 1, 0), (2513, 5056, -40, 0, 1, 1, 0), (2514, 5056, -40, 0, 1, 1, 0), (2515, 5056, -40, 0, 1, 1, 0), (2516, 5056, -40, 0, 1, 1, 0); If deleting everything with Item ID 5056 is too drastic, you might want to add the entries 1414, 1416, 1417 and 1418 to the WHERE-clause, but IMHO the item shouldn't appear anywhere else, so wiping all entries would be the clean solution. This might be pretty similar for Three, but since I don't do Three, I can't tell.
×
×
  • 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