VladimirMangos

this point then that you now possibl;e use right ad.exe. In new mangos revisions for all branches used new map format that let store data lot more compressed by size. No "other ad.exe's" thing. As i say you need use ad.exe exactly from used mangos resvision sources. Ofc. ad.exe changes no so often, but if you setup mangos (in different updating it) this only way been sure that you use right ad.exe.

Must be fixed in [11007]

Must be fixed in [11005]. Also will show propertly item creator name if set for item.

Not sure that i can select cases because from core point no diffs and mostly dependent from expected from scripting side way. Small note about code itself: faction checks is slow so place its aftr fasts checks always: IsFreindly must be checked after isAlive for example

This meaning: unclear why _client_ reject item looting... It not have any DB data that look wrong. Core not get any data so not related to looting error in loot time. Possible somethign not send to client that make client react wrongly.

Items 29434, 41596 and 43016 have similar (and only its) -1 max count -1 stackable and its currences (bagmask 8192) But item 29434 allowed by client to looting, and 2 other not allowed. None info send to server at error. No see any special in dbc data also: first have currency idx 7, other 8 and 9 in middle indexes range.

RemoveFromGroup(); - if player not in group this will ignored.

item must have in DB proper BagFamily, i not sure that this core related. But if you provide exactly item entry id maybe i can look in debug for have 100% sure that this not core related.

you must use ad.exe from _exactly build that you plan use. Base at you jumps by diff strange build you can use wrong ad.exe version from different build. map content can be considered as copyrighted in some way because build by client data and then not allowed discuss it download at forum.

Instead crazy things and steps with oudated versions, just (1) wait when SD2 team fix build with recent Mangos One version (former mangos-0.12), (2) use _normal_ db for 2.4.3 client linked as i already point at main site page.

Patch + mangos specific realmd changes in [11001]. Thank you. kero99 for pointing to patch and testing.

I not understand why you need so old revision, because you can use mangos one recent versions and for it exist sd2 patch + DB. But you can get it from normal mangos git repo.

you can check hardcodemode and forbid join to BG/arena queue. Hmm, maybe then will need at die remove from queues with hardoce more enable. It more like special Hardcore.PvP = 2 (including BG and arenas) and Hardcore.PvE = 2 (include main maps) So for PvP 0 - normal, 1 - hardcore at non BG/arenas, 2 - hardcore anywhere for PvE 0 - normal - 1 hardcore for instaces (now visit bosses really deadly), 2 - anywhere Maybe this more easy way and not linked to insignia that something not exactly same, yes. This let simplify main related tests. Then config options modes will need check only at death and set flag. Other places will need this flag check. But i see it as PLAYER_EXTRA_HARDCORE_DEATH for pvp and pve case common yes, better adding thsi when main part will in some complete state as independent patch maybe.

at main site page (click at icon at left) provided links for 1.12.1 compatible mangos branch. Its have own project forum.

mangos-0.12 renamed to mangos one and moved to own repo. Nothing more changed.

1) Apply SD2 patches and problems must discussed at SD2 forum in to related thread. 2) At main forum page (press at forum icon) you can find links to DB project creating DB compatible with MaNGOS One

Hmm, look intresting. But possible some improvements: 1) not sure good has been so hardcode and not allow resurrect at BG and arenas. 2) also maybe make option limit hardcoded more to instances only (maybe as limited version PvE hardcode allow submode option) If you allow insignia at normal maps then you can (a) know that player killed in PvP or no (b) can make player body lootable in current preexisted loot or that can let pre-fill loot by equipped items/etc... but loot size limited so some random selected for example. 3) if know pvp kill then possible have indepednet alow pvp fatal death and pve fatal death. as independent options for pvp kill also can be not good let "non-honoriable" kill case with fatal result. Base at not big affect normal code work can be possible in future look at including it to mangos repo maybe like existed FFA-PVP mode.

for avoid duplicate thread and etc, please create thread for patch and link it in bug reports instead direct links and chaos

this is bitmask with set 40 bit (if count from 0)

Backported in [s0658]

Lol, and what you will do with hight and etc data at maps with different ground. This just useless and silly.

I found missing sql update that i lost at backporting because mangos.sql already include this strings. Fixed in [s0656].

ok, i will compare DB strings for it, maybe need sync with master

[10987] must fix problem.

in any cases as i point possible damage spell must be cased from dummy effect of dummy spells. This part will same for current and vahicle way work. Another question ofc who cast dummy spells... But batter do half-step in tight direction if possible do it that none