Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[3.3.5] Quest: Take No Chances (11913) #17887

Closed
Treeston opened this Issue Sep 1, 2016 · 11 comments

Comments

Projects
None yet
7 participants
@Treeston
Copy link
Member

Treeston commented Sep 1, 2016

3.3.5 f5cbc17

Quest: Take No Chances

You can repeatedly use Wendy's Torch on the same sack of Frashire Grain. It never despawns.

@ghost

This comment has been minimized.

Copy link

ghost commented Sep 2, 2016

Probably lack of despawning the target http://www.wowhead.com/npc=26161/farshire-grain-credit or maybe even not setting data for the object as used by current player (not sure how it works now, though).

@Tauriella

This comment has been minimized.

Copy link

Tauriella commented Sep 2, 2016

@ghost

This comment has been minimized.

Copy link

ghost commented Sep 2, 2016

So the GO is supposed to change by despawning the original object and turn into a burning object with a certain duration? Or are the flames just a secondary object spawned on top of the original one?

@Treeston

This comment has been minimized.

Copy link
Member Author

Treeston commented Sep 2, 2016

Flames are already spawned on TC. Not sure how.

@Aokromes

This comment has been minimized.

Copy link
Member

Aokromes commented Sep 2, 2016

Maybe it's one aura.

@LKArthas

This comment has been minimized.

Copy link

LKArthas commented Sep 7, 2016

Mostly The SAI needs to have set an event_flags to 1 and check the reset SAI action script

@Staleness89

This comment has been minimized.

Copy link
Contributor

Staleness89 commented Jan 7, 2017

http://www.wowhead.com/spell=46574/burn-grain
^ Spawns a gameobject (the flame) on the spell focus, which is the bag of grains.

Anybody have an idea on how to stop the spell from casting while the flame is active?

@Treeston

This comment has been minimized.

Copy link
Member Author

Treeston commented Jan 8, 2017

Conditions. Do not allow casting if GO with entry within range = spell range.

@Staleness89

This comment has been minimized.

Copy link
Contributor

Staleness89 commented Jan 8, 2017

just wondering if that will make certain ones overlap with each other if two or more are too close to each other. If not, then this would be an easy fix:

DELETE FROM `conditions` where `SourceTypeOrReferenceId`=17 and `SourceEntry`=46574;
INSERT INTO `conditions` (`SourceTypeOrReferenceId`, `SourceGroup`, `SourceEntry`, `SourceId`, `ElseGroup`, `ConditionTypeOrReference`, `ConditionTarget`, `ConditionValue1`, `ConditionValue2`, `ConditionValue3`, `NegativeCondition`, `ErrorType`, `ErrorTextId`, `ScriptName`, `Comment`) VALUES 
(17, 0, 46574, 0, 0, 30, 0, 182071, 8, 0, 0, 0, 0, '', 'Spell requires no GameObject (182071) within 8 yards');
@Rushor

This comment has been minimized.

Copy link
Contributor

Rushor commented Jan 8, 2017

but the spellfocus go will not despawn with this?

@Staleness89

This comment has been minimized.

Copy link
Contributor

Staleness89 commented Jan 8, 2017

it still needs something for despawning

Killyana added a commit that referenced this issue Jan 8, 2017

Aokromes added a commit to Aokromes/TrinityCore that referenced this issue Jan 9, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.