[Fix] TemporySummon DespawnTimer not correct when no player is around

[Auntie Mangos]

See more general bug fix for solution http://getmangos.eu/community/viewtopic.php?pid=127334#p127334

[ciphercom]

TemporySummons didn't calculated their DespawnTimer correct when no player is around, because no Update(...) is called.

Repository version was [s0368]

Author: me (github[at]ciphercom.de)

http://paste2.org/p/1061309

[darkstalker]

actually when there is no active object around, everything freezes

[ciphercom]

Right, but the timer has to go down... or '5 minutes' respawn is not a correct way to specify respawntime.

[VladimirMangos]

Why not do in used in other cases way? Instead adding new variable used with old timer, just replace timer by expire time value store (in msecs)

[ciphercom]

I calculated the 'real' diff time for Creature::Update(realDiff);. But now i would say the whole diff-computation system in mangos could be replaced with the timestamps... so a whole group of errors is fixed. Because the diff should always be calculated according to time i think.

[VladimirMangos]

we need anyway in many cases realdiff. So i only meaning expire time cases that better have as exactly value and then will not calculation errors added at each increase. But i agree that in most cases we need for any objects realdiff.

If do it then do for all worldobjects case maybe as generic sollution (item get realdiff from owner anyway)

So if do generic solution for worldobject then we can use expire timer in current way. This will independent small problem what better timer or final time.

[VladimirMangos]

move to rejected as outdated version