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

[pull] master from cmangos:master #43

Open
wants to merge 9,317 commits into
base: master
Choose a base branch
from
Open

[pull] master from cmangos:master #43

wants to merge 9,317 commits into from

Conversation

pull[bot]
Copy link

@pull pull bot commented Nov 7, 2021

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.1)

Can you help keep this open source service alive? 💖 Please sponsor : )

@pull pull bot added ⤵️ pull merge-conflict Resolve conflicts manually labels Nov 7, 2021
@killerwife killerwife force-pushed the master branch 3 times, most recently from d794e29 to b85aea8 Compare December 21, 2021 22:36
@killerwife killerwife force-pushed the master branch 3 times, most recently from b453f29 to 8522113 Compare May 28, 2022 14:56
@killerwife killerwife force-pushed the master branch 2 times, most recently from ba1adca to 6cd60c5 Compare June 30, 2022 11:53
@killerwife killerwife force-pushed the master branch 2 times, most recently from 7806a67 to d0cc28c Compare July 17, 2022 19:52
@killerwife killerwife force-pushed the master branch 2 times, most recently from bb2815b to 4ce90bc Compare February 15, 2023 09:35
@killerwife killerwife force-pushed the master branch 2 times, most recently from 653dbce to 82eb575 Compare February 19, 2023 23:51
@killerwife killerwife force-pushed the master branch 2 times, most recently from 83bbe1f to 46d21e6 Compare September 10, 2023 20:13
evil-at-wow and others added 30 commits January 12, 2025 02:51
This makes sure the AuthSocket member function pointer member gets
properly aligned by the compiler. Packing this struct is not really
needed because this struct isn't part of the client-server protocol.
Loot objects have ownership of their LootItem objects, and also keep
track of any associated GroupLootRoll objects. A GroupLootRoll object
in turn references the LootItem the roll is about, and its destructor
may still use the LootItem. So when a Loot object is destructed, it
can't delete its LootItem objects as long as any GroupLootRoll objects
are still around that may reference/use them!

Fixes cmangos/issues#3860.
Just a fair warning, a lot of things might go wrong here. That being said, this is supported by evidence. The temporary GOs never create type 11 so only here a change is needed
This reverts commit 124115d.

Reverting until i find fix. Still correct change.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⤵️ pull merge-conflict Resolve conflicts manually
Projects
None yet
Development

Successfully merging this pull request may close these issues.