You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the SummonPropFlags section of DBCEnums is missing most of the names of the flags. Because of this they also seem to be unimplemented in my testing, specifically the "PERSONAL_SPAWN" flag.
Expected Blizzlike Behaviour
These flags should all not only be named, but they should also have their mechanics implemented in the core.
Source
This is a list of the flags and their names taken from wowdev.wiki, appears to be from the TBC leak. There is also an instance of TC implementing one such flag here: Master & 3.3.5a
Current Behaviour
Right now the
SummonPropFlags
section of DBCEnums is missing most of the names of the flags. Because of this they also seem to be unimplemented in my testing, specifically the "PERSONAL_SPAWN" flag.Expected Blizzlike Behaviour
These flags should all not only be named, but they should also have their mechanics implemented in the core.
Source
This is a list of the flags and their names taken from wowdev.wiki, appears to be from the TBC leak. There is also an instance of TC implementing one such flag here: Master & 3.3.5a
Steps to reproduce the problem
A couple spells that are supposed to be making use of the "PERSONAL_SPAWN" flag are Jokkum Summon and Summon Veranus and Thorim.
.cast 56541/56649
.Extra Notes
No response
AC rev. hash/commit
4378493
Operating system
Windows 10 x64
Custom changes or Modules
mod-worgoblin
The text was updated successfully, but these errors were encountered: