VladimirMangos

No real parallel damage/heal. All world event proccessed in one world thread one by one in tick pass. All current events in queue procced in tick and thne new tick start. With default tick delay: 50 msecs. So 20 ticks in sec. + Network lags and caching data at send by network you will se at client its as parallel. As goal mangos team plan switch to per map thread event proccessing. But anyway all events at one map will be executed in queue. Someone can say that exist already patches for like per map execution but i only comment: in diff level hackish way...

If you use VS Express Edition (it show this error) then you must use VS Express Edition SP1 version that include as part masm. VS 2010 have one problem: it more slow that VS 2008 without any bonuses in mangos case.

In [9931]. Thank you

It must be fixed now. Thank you for reporting... (fixed by your github post )

Most strange that as i remember i build before pushing commit to repo... In any case thank you, fix added into [9928]

Code look good, but splels have one problem. All used for reduce chance base at description but in one used possitive basepoinst and another used negative for same task. So unclear how value must be used....

Nice catch of horrible typo set In [9926]. Thank you!

Existed code must auto-extend last bracket level range for all big levels.

In [9916]. Thank you

Description updated into [9915]. Thank you for pointing to outdated info.

as i test, dependent in order player login near another player. Naked visible player in most cases login near viewer. So possible dependent from sequence send update fields at login/far teleport.

I close thread: accepted section not for discussion spell _working_ but broken after next client switch. Threads in accepted open only for discussion _patch_ problem after it adding.

With this change and also update to new way set world states in [9910] Thank you

If we want have number full or partly pass minutes then need more code but float better avoid For example (base at fact that timer can't be < 0:

i not include referecnes forum remark. But other look good. In [9906]. Thank you

In fact i add it already before read this thread)This thread patch also will nice addition.

This is not good add include for one enum. Any new include in another header make more chance for cross includes when 2 headers include each other. In like case you will have strange buld errors different at different compilers and compile modes. More safe way move enum to common included header. And this done in [9903]

You need apply 9899_01_mangos_spell_bonus_data.sql, but i recommend update sources before do this: this sql updates has been fixed fast after first adding to repo.

aerolite meaning git. Problem must fixed in [9903]

i think (1) block value update by self to 200%. So not need double in calclation. (2) abs at patch notes block value cap is 30*level, 34.5 is cap for final damage...

Also MSSQL use different syntax for sql query indintifiers and partly for quaries. This can create big porblems because mangos include quary text to source code explicitly.

Suggested way cleanup and fixing spell bonus coeffs claculation added (in fact after manual recreating at current sources with some addition problem fixing) in [9893-9898]. Thank you It' can't fix opudated value (you need manually check data for find porblems as before) but patch let add to table less data.

Agree with last remark. Not see reason have different way code changes in branches for similar working code parts. Mns backport added to mangos 0.12. This must resolve problem. Nice another result in simplify backporting other related changes. In ideal state we must have branches different only in parts that work in different way in related client versions.

Thank you for preparing backport I am in fact remade it for be sure but only find that I made some typos and wrong changes that fix by your version. Nice work Added to mangos-0.12 and will backport to mangoszero also soon.

mangos master sources fine build at VS2010 without any patches. Base at suggested changes look like you have modified sources. So this is not mangos core porblem.