MAJOR 1.0.4 Bug - Please Read

[cen]

Tested on default and modded PBOs. 

 

When maintaining an object it tells you that it was successful, the LastUpdated column in the database is updated, but the Damage on the object does not change.

 

What this means is that after a restart the object still shows as needing to be maintained.

 

This is a HUGE bug for servers that require maintenance.

[MGT]

It was just the hiveext.dll was not updated to the very latest build. DatabaseMySql.dll is just the library it uses.

 

The hiveext.dll in the link is dated 210114 and the older one (faulty) was 170114, that right?

 

Edit, working :)

[vbawol]

Thanks for confirming Dave!
 

Just to be sure I updated the server build again to make sure we included the following fixes: 

• Fix 'Logic' Typo: https://github.com/vbawol/DayZ-Epoch/commit/9c80054b1225bb9705a415a0aeffca5ddecf4290
• Update server_monitor.sqf private array: https://github.com/vbawol/DayZ-Epoch/commit/1c94205afed7bb181819de61d0a57abb4c9c9244
• Fixes to Panthera Traders

1.0.4b server hotflx build:

md5: 9958cbdc616eec2aeb7c28d737bccc5a

http://goo.gl/SpmKwg

 

The only changes between this and 1.0.4a is the  server_monitor.sqf and panthera #16 mission files server_traders.sqf, mission.sqm, and inside server pbo mission.sqf

[Defent]

Not sure if this relates to this problem but, when I damage a built part and the server restarts. That building is back to full health again.

(Even with the new 1.0.4b hotfix)

Is this intentional? 

[cen]

Thanks for the quick fix AWOL.

[vbawol]

Not sure if this relates to this problem but, when I damage a built part and the server restarts. That building is back to full health again.

(Even with the new 1.0.4b hotfix)

Is this intentional? 

That is currently intentional, we may make the objects retain there damage in the future. We do not do it now because of performance concerns having 1000's of damage handlers.

[vbawol]

Thanks for the quick fix AWOL.

Your welcome, hopefully this will tide us all over til the 1.0.4.1 patch.

[Defent]

That is currently intentional, we may make the objects retain there damage in the future. We do not do it now because of performance concerns having 1000's of damage handlers.

Ok thank you, I was going crazy here trying to fix it.

[GGDayZ]

thx for the quick fix awol, works now for us too!

[BetterDeadThanZed]

That is currently intentional, we may make the objects retain there damage in the future. We do not do it now because of performance concerns having 1000's of damage handlers.

 

So if an item is damaged via SQL event, that damage will be reset upon restart?

[vbawol]

So if an item is damaged via SQL event, that damage will be reset upon restart?

he is just talking about damage received in game not persisting, if you damage an item via SQL it will stay that way until it has been maintained.