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.

[BetterDeadThanZed]

Yup... this has already been reported... not sure if it's being fixed for 1.0.4.1 but I hope so!

[vbawol]

Are you using the new hive dll? the damage and datestamp get updated with the new child calls we added. Most of the maintain code has changed if you have older code make sure your fully updated.

[DoS-gaming]

Yup same for me.

Fresh arma install with 1.0.4 code, only infiSTAR anti hack and it doesn't set the damage to 0.

Already made a thread about it earlier. 

[FUBAR22]

Hey...may have found a small problem with a file (spelling error)

 

If you look at the server_spawnCarshSite.sqf at line 40 see:

    diag_log(format["CRASHSPAWNER: %1%2 chance to spawn '%3' with loot table '%4' in %5 secounds", round(_spawnChance * 100), '%', _crashName, _lootTable, _timeToSpawn]);

 

Probably needs to be spelled seconds

 

Not sure how that will impact the server, but worth noting.

 

FUBAR

[MGT]

Yes, I don't know why it doesn't set the damage back down to 0????

 

Maybe pull the maintain area script to mission and edit it?

[cen]

I did a quick compare Dave and didn't see anything that jumped out.

Yes AWOL I'm using the updated .dll

[MGT]

It seems the maintain is updating the dates but not resetting the damage to "0"

What this means is even though the object will not get removed until the time set in the hiveext.ini has elapsed it will mean that players will get the option to maintain constantly

[DoS-gaming]

It seems the maintain is updating the dates but not resetting the damage to "0"

What this means is even though the object will not get removed until the time set in the hiveext.ini has elapsed it will mean that players will get the option to maintain constantly

 

This, it is updating the Datestamp and lastupdated column but not the damage.

[MGT]

I think the change was where on the old maintain area it removed and rebuilt the object, thus setting the damage to "0" and this doesn't remove the object, it just updates it.

The script needs something to reset the object damage to "0"

 

AxeCop where are you?!?

[GGDayZ]

Oh I see this thread has some responses. Im going live with 1.0.4 and just disable the maintaining and despawning for now hoping there will be a fix soon.

[Defent]

I'm not sure if I have the same problem as you guys. Apart from the updating of the Datstamp and LastUpdated table.

 

Any damaged buildings automatically repairs themselfs after restart, this can be because the Damage value in the database does not change. It's always at 0.
 

[maca134]

Wud this not work for now?

server_maintainArea.sqf

_key = format["CHILD:306:%1:%2:%3:",_objectID,[],0];

http://puu.sh/6CxCy/5b4c74bf40.png

[MGT]

Wud this not work for now?

server_maintainArea.sqf

_key = format["CHILD:306:%1:%2:%3:",_objectID,[],0];

http://puu.sh/6CxCy/5b4c74bf40.png

 

Going to test this now and it's maintain_area.sqf isn't it?

[maca134]

lol also, updating the damage will update the last updated timestamp, which if u base cleanups on that, as we do, kinda makes the other hive call redundant

[Defent]

Going to test this now and it's maintain_area.sqf isn't it?

 

Yea It is, line 47.

[maca134]

line 26 and 47

[MGT]

Also, I notice that having self bloodbag in the fn_self_actions causes the base parts to be deleted ;)

[maca134]

Also, I notice that having self bloodbag in the fn_self_actions causes the base parts to be deleted ;)

did that work? cos tbh u can probably remove the 396 calls, IF your cleanups are bases on last_updated

[MGT]

did that work? cos tbh u can probably remove the 396 calls, IF your cleanups are bases on last_updated

 

Our cleanups are from hiveext.ini, and no it hasn't worked the base parts maintained are still damaged

Would it be better to add the line around line 87 instead?

[Defent]

Also, I notice that having self bloodbag in the fn_self_actions causes the base parts to be deleted ;)

I have self bloodbag in the same file and I've not had any parts being deleted?

When I maintain parts they get repaired (without maca134s' fix), however the damage table doesn't change (remains on 0).

[maca134]

It should work lol

[vbawol]

Just checked and the last update of the dll was a few days older than the latest build, This meant it was missing the `damage` = 0.

 

1.0.4b server hotflx build:

md5: 9958cbdc616eec2aeb7c28d737bccc5a

http://goo.gl/SpmKwg

 

Note this also fixes several bugs that have been reported: 

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

[MGT]

It should work lol

 

DatabaseMySql.dll?

 

So based on that maintain_area should be updating damage to "0" but isn't?

 

Just checked and the last update of the dll was a few days older than the latest build, This meant it was missing the `damage` = 0 this version has it and should work fine:

md5: c5b717f666ef74312230b3c946ae07e2

http://goo.gl/89wlll

Testing now!

[maca134]

Its the hive source, sqlobjdata.cpp i think

[vbawol]

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