<!-- First of all, THANK YOU for your contribution. -->
## Changes Proposed:
- Implement Tarren Mill Fishermen
- Remove wrong spawn point for Phil (should be one of the pentagram
children instead)
- Fix waypoints and add emotes for Jay Lemieux & Julie Honeywell
- Rebuild guard spawns, remove custom guards and custom waypoints
- Implement the Tarren Mill Horsehand (Bessy and Young Blanchy event)
- Corrects waypoints for Tarren Mill Peasants in the orchard.
- Fix equip template for Tarren Mill Peasant (18644)
- Adds spawns of Tarren Mill Horse and Tarren Mill Horsehand
- Corrects Young Blanchy position
- Fix unit_flags for Tarren Mill Horse and Tarren Mill Peasant (sniffed)
- Implement the Orchard events (Peasants will periodically gather apples
and drop off sacks of apples at a nearby cart)
## Issues Addressed:
<!-- If your fix has a relating issue, link it below -->
- Closes
## SOURCE:
<!-- If you can, include a source that can strengthen your claim -->
Retail sniffs mostly
Classic sniffs for Spell IDs
## Tests Performed:
<!-- Does it build without errors? Did you test in-game? What did you
test? On which OS did you test? Describe any other tests performed -->
- Tested ingame
-
## How to Test the Changes:
<!-- Describe in a detailed step-by-step order how to test the changes
-->
1. `.go c 83518`
2. observe all 👁️
## Known Issues and TODO List:
<!-- Is there anything else left to do after this PR? -->
- [ ] The Tarren Mill Horsehand phases through the wall due to his
waypoints. He does not pathfind properly to the next waypoint so he
phases instead. This is sniffed data and possibly a core issue.
- [ ] The spell cast by Tarren Mill Peasants is **not** sniffed.
<!-- If you intend to contribute repeatedly to our project, it is a good
idea to join our discord channel. We set ranks for our contributors and
give them access to special resources or knowledge:
https://discord.com/invite/DasJqPba)
Do not remove the instructions below about testing, they will help users
to test your PR -->
## How to Test AzerothCore PRs
When a PR is ready to be tested, it will be marked as **[WAITING TO BE
TESTED]**.
You can help by testing PRs and writing your feedback here on the PR's
page on GitHub. Follow the instructions here:
http://www.azerothcore.org/wiki/How-to-test-a-PR
**REMEMBER**: when testing a PR that changes something **generic** (i.e.
a part of code that handles more than one specific thing), the tester
should not only check that the PR does its job (e.g. fixing spell XXX)
but **especially** check that the PR does not cause any regression (i.e.
introducing new bugs).
**For example**: if a PR fixes spell X by changing a part of code that
handles spells X, Y, and Z, we should not only test X, but **we should
test Y and Z as well**.
Process of translation: only original sources of deDE texts by
researching multiple sources, reverse translation by searching for
related quest items/NPCs and using these names to reconstruct a proper
translation.
This fixes the terms
Scrimshank (Kieselschliff), Banehollow (Schattenfluch), Trollbane
(Trollbann), Stonesplitter (Splitterstein), Stonemaul (Steinbrecher),
Captain (Hauptmann), Kromcrush (Krombruch), Earthbinder (Erdbinder),
Razorfen (Klingenhauer), Razorflank (Klingenflanke), Stonard (Steinard)
for quest progress/request text entries for the deDE localisation with
proper casus/declension (these are not proper translated names of
locations/NPCs that have been left over by Blizzard since their language
localisations in TBC in 2006 and onward).
Fixed a self-made translation for quest 334.
Added missing deDE text entries for 4481, 4482, 4483, 5306, 5863, 7723,
9436.
<!-- First of all, THANK YOU for your contribution. -->
## Changes Proposed:
- Fixing missing or wrong entries in the quest_request_items_locale
table.
## Issues Addressed:
<!-- If your fix has a relating issue, link it below -->
Fixes some of the tasks listed in the issues below:
- https://github.com/azerothcore/azerothcore-wotlk/issues/14244
- https://github.com/azerothcore/azerothcore-wotlk/issues/14618
- From CC Github:
https://github.com/chromiecraft/chromiecraft/issues/4697
## SOURCE:
<!-- If you can, include a source that can strengthen your claim -->
Read the text on top.
## Tests Performed:
<!-- Does it build without errors? Did you test in-game? What did you
test? On which OS did you test? Describe any other tests performed -->
- Not tested.
## How to Test the Changes:
<!-- Describe in a detailed step-by-step order how to test the changes
-->
All of the changes are to request texts of quests, can be tested by
accepting quests or simply reviewing the changed file.
## Known Issues and TODO List:
<!-- Is there anything else left to do after this PR? -->
- [ ] I still might want to check which of the tasks in above mentioned
issues are resolved by this.
<!-- If you intend to contribute repeatedly to our project, it is a good
idea to join our discord channel. We set ranks for our contributors and
give them access to special resources or knowledge:
https://discord.com/invite/DasJqPba)
Do not remove the instructions below about testing, they will help users
to test your PR -->
## How to Test AzerothCore PRs
When a PR is ready to be tested, it will be marked as **[WAITING TO BE
TESTED]**.
You can help by testing PRs and writing your feedback here on the PR's
page on GitHub. Follow the instructions here:
http://www.azerothcore.org/wiki/How-to-test-a-PR
**REMEMBER**: when testing a PR that changes something **generic** (i.e.
a part of code that handles more than one specific thing), the tester
should not only check that the PR does its job (e.g. fixing spell XXX)
but **especially** check that the PR does not cause any regression (i.e.
introducing new bugs).
**For example**: if a PR fixes spell X by changing a part of code that
handles spells X, Y, and Z, we should not only test X, but **we should
test Y and Z as well**.
Co-authored-by: Gultask <100873791+Gultask@users.noreply.github.com>
Process of translation: only original sources of deDE texts by
researching multiple sources, reverse translation by searching for
related quest items/NPCs and using these names to reconstruct a proper
translation.
This fixes the terms
Coldtooth-Mine (Eisbeißermine), Doomhammer (Schicksalshammer), Fizzle
(Zischel), Fizzledowser (Rutenwünschels), Fizzlebub (Zischelbub),
Burning Blade (Brennende Klinge), Ashenvale (Eschental),
Bloodscalp/s/stamm (Blutskalpe, Blutskalpstamm),
Darkspeartrolle/Darkspears/Darkspearstamm (Dunkelspeere,
Dunkelspeertrolle, -stamm), Moonglade (Mondlichtung), Starblaze
(Sternenschauer), Shadowglen (Laubschattental), Darrowshire (Darroheim),
Booty Bay (Beutebucht), Ratchet (Ratschet), Dizzywig (Flunkerblick),
Hearthglen (Herdweiler), Chillwindspitze (Zugwindspitze), Stormrage
(Sturmgrimm), Stormpike (Sturmlanze/n), Ironforge (Eisenschmiede),
Thunderhorn (Donnerhörner), Steamboil (Kesseldampf), Twilight-Hammer,
-klan (Schattenhammer/Schattenhammerklan), Fathom-Kern (Tiefenkern),
Blackfathom Deeps (Tiefschwarze Grotte), Blackrock-* (Schwarzfels-*),
Hawkwind (Falkenwind), Feathermoon (Mondfeder), Moonrage (Mondzorn),
Firemane (Feuermähne), Searingblade (Sengende Klinge), Ragefireabgrund
(Flammenschlund), Ironbands Areal (Eisenbands Lager), Zandalar
(Zandalari), Southshore (Süderstade)
for quest progress/request text entries for the deDE localisation with
proper casus/declension (these are not proper translated names of
locations/NPCs that have been left over by Blizzard since their language
localisations in TBC in 2006 and onward).
Added missing progress/request text entries for 308, 311, 417, 1644,
1787, 5059, 5060, 5721, 6004, 6023, 6025, 6187, 8042, 8043, 8044, 8046,
8047, 8048, 8050-8079, 8102, 8107, 8108, 8111, 8112, 8113, 8117, 8118,
8142, 8143, 8147, 8183-8195, 8238, 8239, 8240, 8243, 8246, 8860, 9594,
9692, 9707, 10414, 10415, 10919, 11451. (A lot of them are
Zandalari/Zul'Gurub related quests.)
Replaced post-Cataclysm progress/request text entries for 933, 935,
6387, 7383.
Fixed a wrong $R with plain text at progress/request text for 9147.
Added missing female gender equivalent to 6391.
(There are probably more changes in the file that aren't further
explained here as it was hard to keep track of everything. If you think
I made a mistake or have questions please contact me directly.)
<!-- First of all, THANK YOU for your contribution. -->
## Changes Proposed:
- Fixing a lot in the quest_request_items_locale table.
## Issues Addressed:
<!-- If your fix has a relating issue, link it below -->
- Fixing some of the tasks in
https://github.com/azerothcore/azerothcore-wotlk/issues/14244
Referring to my other two bug reports from CC Github:
- https://github.com/chromiecraft/chromiecraft/issues/4697
- https://github.com/chromiecraft/chromiecraft/issues/4745
## SOURCE:
<!-- If you can, include a source that can strengthen your claim -->
- Read the text on top.
## Tests Performed:
<!-- Does it build without errors? Did you test in-game? What did you
test? On which OS did you test? Describe any other tests performed -->
- Not tested.
## How to Test the Changes:
<!-- Describe in a detailed step-by-step order how to test the changes
-->
All of the changes are to reward texts of quests, can be tested by
completing quests or simply reviewing the changed file.
## Known Issues and TODO List:
<!-- Is there anything else left to do after this PR? -->
- [ ]
- [ ]
<!-- If you intend to contribute repeatedly to our project, it is a good
idea to join our discord channel. We set ranks for our contributors and
give them access to special resources or knowledge:
https://discord.com/invite/DasJqPba)
Do not remove the instructions below about testing, they will help users
to test your PR -->
## How to Test AzerothCore PRs
When a PR is ready to be tested, it will be marked as **[WAITING TO BE
TESTED]**.
You can help by testing PRs and writing your feedback here on the PR's
page on GitHub. Follow the instructions here:
http://www.azerothcore.org/wiki/How-to-test-a-PR
**REMEMBER**: when testing a PR that changes something **generic** (i.e.
a part of code that handles more than one specific thing), the tester
should not only check that the PR does its job (e.g. fixing spell XXX)
but **especially** check that the PR does not cause any regression (i.e.
introducing new bugs).
**For example**: if a PR fixes spell X by changing a part of code that
handles spells X, Y, and Z, we should not only test X, but **we should
test Y and Z as well**.
Asking for a test because my DB is quite polluted these days and I may
have forgot to set a value somewhere
<!-- First of all, THANK YOU for your contribution. -->
## Changes Proposed:
- Sniffs spawns for Draenei Vessel (already sniffed before)
- Pools normal Vessel them with trapped Vessel at 50% chance (confirmed
in sniff)
- Prevent trap from triggering at distance
- Fixes trapped Vessel being unlootable
- Fixes campfire with bad z coords using sniffed data
## Issues Addressed:
<!-- If your fix has a relating issue, link it below -->
- Closes https://github.com/azerothcore/azerothcore-wotlk/issues/14332
- Closes https://github.com/chromiecraft/chromiecraft/issues/4618
## SOURCE:
<!-- If you can, include a source that can strengthen your claim -->
WotLK Classic
## Tests Performed:
<!-- Does it build without errors? Did you test in-game? What did you
test? On which OS did you test? Describe any other tests performed -->
- Tested ingame
-
## How to Test the Changes:
<!-- Describe in a detailed step-by-step order how to test the changes
-->
1. `.quest add 10028`
2. `.tele Tuurem`
3. see if behaviour improves
## Known Issues and TODO List:
<!-- Is there anything else left to do after this PR? -->
- [ ] I haven't found a way to make a truly empty loot table without
worldserver errors so I duplicated the table for normal vessel and
lowered the chance to 0.1 (I've seen no loot in WotLK Classic, but it
was lootable)
- [ ]
<!-- If you intend to contribute repeatedly to our project, it is a good
idea to join our discord channel. We set ranks for our contributors and
give them access to special resources or knowledge:
https://discord.com/invite/DasJqPba)
Do not remove the instructions below about testing, they will help users
to test your PR -->
## How to Test AzerothCore PRs
When a PR is ready to be tested, it will be marked as **[WAITING TO BE
TESTED]**.
You can help by testing PRs and writing your feedback here on the PR's
page on GitHub. Follow the instructions here:
http://www.azerothcore.org/wiki/How-to-test-a-PR
**REMEMBER**: when testing a PR that changes something **generic** (i.e.
a part of code that handles more than one specific thing), the tester
should not only check that the PR does its job (e.g. fixing spell XXX)
but **especially** check that the PR does not cause any regression (i.e.
introducing new bugs).
**For example**: if a PR fixes spell X by changing a part of code that
handles spells X, Y, and Z, we should not only test X, but **we should
test Y and Z as well**.
* closes https://github.com/azerothcore/azerothcore-wotlk/issues/13851
Co-Authored-By: Grindelwald <137000133@qq.com>
<!-- First of all, THANK YOU for your contribution. -->
## Changes Proposed:
-
-
## Issues Addressed:
<!-- If your fix has a relating issue, link it below -->
- Closes
## SOURCE:
<!-- If you can, include a source that can strengthen your claim -->
## Tests Performed:
<!-- Does it build without errors? Did you test in-game? What did you
test? On which OS did you test? Describe any other tests performed -->
-
-
## How to Test the Changes:
<!-- Describe in a detailed step-by-step order how to test the changes
-->
1.
2.
3.
## Known Issues and TODO List:
<!-- Is there anything else left to do after this PR? -->
- [ ]
- [ ]
<!-- If you intend to contribute repeatedly to our project, it is a good
idea to join our discord channel. We set ranks for our contributors and
give them access to special resources or knowledge:
https://discord.com/invite/DasJqPba)
Do not remove the instructions below about testing, they will help users
to test your PR -->
## How to Test AzerothCore PRs
When a PR is ready to be tested, it will be marked as **[WAITING TO BE
TESTED]**.
You can help by testing PRs and writing your feedback here on the PR's
page on GitHub. Follow the instructions here:
http://www.azerothcore.org/wiki/How-to-test-a-PR
**REMEMBER**: when testing a PR that changes something **generic** (i.e.
a part of code that handles more than one specific thing), the tester
should not only check that the PR does its job (e.g. fixing spell XXX)
but **especially** check that the PR does not cause any regression (i.e.
introducing new bugs).
**For example**: if a PR fixes spell X by changing a part of code that
handles spells X, Y, and Z, we should not only test X, but **we should
test Y and Z as well**.
Co-authored-by: Grindelwald <137000133@qq.com>
* fix(DB/Gameobject): Fixed overlapping Milk Barrel / Food Crates in Stormwind City
## Changes Proposed:
Add Water Barrel and Food Create to a pool.
## Issues Addressed:
- Closes https://github.com/azerothcore/azerothcore-wotlk/issues/11776
## SOURCE:
n/a
## Tests Performed:
Logged in, ported to object, verified only 1 object spawns at a time. Verified alternating spawns of the object.
## How to Test the Changes:
1. Login
2. .go gameobject 31401 || .go gameobject 33607
3. Verify only 1 object has spawned.
4. Open object and take items, causing despawn.
5. Wait for respawn of another object.
6. Respawn of other object in pool.
7. Repeat 3-5.
## Known Issues and TODO List:
n/a
<!-- If you intend to contribute repeatedly to our project, it is a good idea to join our discord channel. We set ranks for our contributors and give them access to special resources or knowledge: https://discord.com/invite/DasJqPba)
Do not remove the instructions below about testing, they will help users to test your PR -->
## How to Test AzerothCore PRs
When a PR is ready to be tested, it will be marked as **[WAITING TO BE TESTED]**.
You can help by testing PRs and writing your feedback here on the PR's page on GitHub. Follow the instructions here:
http://www.azerothcore.org/wiki/How-to-test-a-PR
**REMEMBER**: when testing a PR that changes something **generic** (i.e. a part of code that handles more than one specific thing), the tester should not only check that the PR does its job (e.g. fixing spell XXX) but **especially** check that the PR does not cause any regression (i.e. introducing new bugs).
**For example**: if a PR fixes spell X by changing a part of code that handles spells X, Y, and Z, we should not only test X, but **we should test Y and Z as well**.
* Update data/sql/updates/pending_db_world/fix-11776.sql
added space for readability
Co-authored-by: Gultask <100873791+Gultask@users.noreply.github.com>
Co-authored-by: Gultask <100873791+Gultask@users.noreply.github.com>
* part1
* chef jessen
* done
* one more wandering creature
* Update rev_1672845950723513700.sql
* give up but it was an interesting experi
...ence (200 SAI lines)
* Update rev_1672845950723513700.sql
