TrinityCore / TrinityCore

TrinityCore Open Source MMO Framework (master = 11.0.2.56513, 3.3.5 = 3.3.5a.12340, wotlk_classic = 3.4.3.54261, cata classic = 4.4.0.55262)
http://www.trinitycore.org
GNU General Public License v2.0
9.51k stars 6.04k forks source link

[ICC-Trash] Spirit Alarm / Deathbound Ward #4590

Open Amit86 opened 12 years ago

Amit86 commented 12 years ago

Problem: While checking ICC entrance without even entering the second chamber (from Lights Hammer) Deathbound Ward is being activated.

Deathbound Ward Should be activated when a player steps on his trap according to wowwiki:

Deathbound Wards are large trash mobs that are triggered by stepping over hidden Spirit Alarms in The Lower Spire before Lord Marrowgar. There are four Spirit Alarms randomly placed within the two rooms leading up to Marrowgar's chamber. A Spirit Alarm in one room may activate a Deathbound Ward in the other room.

Also these taps should be disarmed by rouges(wowwiki): Rogues can use Disarm Trap on the traps. Alternatively, warlocks can trigger the Spirit Alarms with Eye of Kilrogg so that alarms are not activated during other pulls. Surprisingly, Crashin' Thrashin' Racer Controller can also activate the Spirit Alarms. Single pulls of Deathbound Wards are recommended. If two or more are pulled accidentally, Deathbound Wards can be reset by running into the front Light's Hammer room.

http://www.wowwiki.com/Deathbound_Ward

Spirit Alarm IDs: 201814,201815,201816, 201817 Spawned GUIDs: 150166, 150192, 150357 Deathbound Ward Entry: 37007 (heroic: 38031) Using tip ced3460 on a clean tdb with no addons

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

durrrr commented 12 years ago

Confirmed.

jaredjones commented 12 years ago

Confirmed.

Expecto commented 12 years ago

confirm

Rushor commented 9 years ago

does someone has an idea how to archive, that the traps are always visible for rogues (and invisible for normal player) and.. how we archieve, that the traps can be deactivated by rogues?

jaredjones commented 9 years ago

Nope. This functionality for invisible rogue traps isn't programmed yet in TC

Rushor commented 9 years ago

hm i saw a similar function in the frosttraps from hunters. i modified the faction und it worked fine, but the triggerrange for the traps is still too huge.

D4R4 commented 7 years ago

I am currently working on this but I am clueless about the Trap object and Disarm function, @Rushor can you give me any pointers?

tje3d commented 6 years ago

Its very annoying

tje3d commented 6 years ago

Well i've fixed it by changing Spirit Alarm type to 1. Here is the sql query:

-- Changing Data4(type) for Spirit Alarm from 2 to 1.
UPDATE `gameobject_template` SET `Data4`=1 WHERE `entry` in (201814, 201815, 201816, 201817)
ghost commented 6 years ago

IIRC, changing Data fields in gameobject_template is considered to be a hack, because those fields are sniff values (need sniff data to verify changes to those values).

Golrag commented 6 years ago

I have this https://github.com/Golrag/TrinityCore/commit/c13a5c19c7ee669bc8adc40ff5fbea583a342925 It's old, and created some bugs in battlegrounds with the buffs, the client for some reason did not send that the player walked in an area trigger, so it's not really updated & finished. Someone could maybe take a look at it. master branch has the right names for those data values iirc

offl commented 4 years ago

Better to fix this with https://github.com/TrinityCore/TrinityCore/issues/12691#issuecomment-235773144 too

HoustonCore commented 4 years ago

@offl Can you tell me if we change the value in the "Date" database then this is a hack? Even if the value equals 0 example.


UPDATE `gameobject_template` SET` Data4` = 0 WHERE `entry` IN (201814, 201815, 201816, 201817);
offl commented 4 years ago

https://github.com/TrinityCore/TrinityCore/issues/4590#issuecomment-334930919

jackpoz commented 4 years ago

@Golrag any chance on finishing the todos in that commit and submitting it as PR ?

Golrag commented 4 years ago

I'll open a draft PR this week after I updated that commit :)