r4z0r49

I have no idea.

Not just yet we need to find another approach for this

We do know about the boat house it seems the lower platform of the boathouse wont hold any loot they just sink below. We have been looking at this on the dev build.

The hivedll has nothing to do with spawn selection or gender selection. So im not sure what you talking about however in the next main patch we do force the screens to always load until the user has given some input but again this will not work on some private hives.

You need to contact them we cant help with 3rd party hives sorry

What hive are you using. Our test server ones are coming back in fine placement is a little off but they spawn and save as they should.

I think we have found the issue Alby manged to stip some of it down today and found an issue with how we broadcast some of the lockout timers. We have a new solution worked out and will start testing later tonight. Im at work till Monday but expect a hotfix some time around then. ty

Yes ill get that added into the next hotfix as well.

Tested both The private isn't needed as all vars are global to the main scope we might have a return or something between causing the interference but it would happen all the time not as random as it is. As for the subsequent randoms we also tested this it returns a new value every time i left my machine running for the 12 hours i went to work last night and the results showed that random is giving a different result each time. The issue is the system just stops some how from reports of no loot. But all tests we have done show it always working. the only change from 18 to 1802 is that bias. Until it can be recreated every time how can we find a fix. but all instances of this happening are reporting the spawn check is still working so loot is still trying to be spawned and zeds are still spawning. Its a mad one. The only item i can see might be causing the issue is how the building gets locked for 15 mins. Until i get time to sit down and rip it apart to see whats going on i just don't know atm. So i think soon as i get a chance ill strip the bias change to an easy random 1 system and add some logging system's to try finding out wtf is going on.

[07:49:50] R4Z0R49: just tested again started one side cherno ran down the main road didnt have any sign of 0 loot [07:50:04] R4Z0R49: tested again with server at 1 fps. [07:50:17] R4Z0R49: same result not once did i get 0 loot. I have no idea whats going on just now and i just don't have to time to debug it so i have no choice but scrap the bias system not that i have much to scrap. Ive tested with server fps below 5 I've also tested with client fps low and im still not getting any instant where loot is 0 to the degrees your saying. ( i do not check buildings i do a 150 meter scan and list the amount of loot spawns i find). I did get a report from one of the devs this morning about this issue but no solid info in regards to the reasons or whys.

The issue is reports are saying 0 loot. < we can not recreate 0 loot.

Give us exact into to recreate no matter how much we try we can not recreate an instance where a town has 0 loot we can however recreate where the town has very low loot but we are still talking 3 numbers. The difference with loot from 1.8 to now is the bias from 100 to 67 that's it. I think for now we may just have to abandon the loot bias system and go back to a simple random system.

There's no actual issue with the loot buildings just have a chance to spawn nothing at all.

Basically we are trying to tie everything up a little more.

They have already been updated as part of the nutrition system. :-) This wont be coming in yet but here some info on the infection change from food.

Added. * [NEW] - Action menu update to destroy tents. (all items pile up outside)

added. * [uPDATED] - Full moon nights is now select-able by the server admins.

Added, * [NEW] - 1 new model (feather). * [NEW] - Woodern arrows can now be created. (Wood,FeatherX2) * [NEW] - Feathers added to Hens as you gut.

We are getting no other reports of this ? Take a look in your servers rpt file and go hit save on a tent show me what it says.

ok with the bias i think whats happening is when the building scan checks the buildings and accepts new loot to be spawned the bias then kicks in to control how many positions get loot. If the bias says no to all locations this means that building will be dead for new loot for 15 mins i think this is why logging out and back in fixes loot. Local vars get cleared meaning on logout the building has no longer been tagged and you can try again. I'm going to change the lockout to only happen when loot spawns so after the first location gets passed will the building be tagged this should mean all buildings have loot. At the lest they will always keep trying to spawn and not get tagged.

added * [FIXED] - LOOT - Building locks have been moved to after the building has spawned loot. (hopefully this should allow the bias to sometimes fail but allow other pass if no loot has spawned.

Added * [NEW] - Private SQL - Cleanup updated to move dead bodies to a new table(character_dead) before removal from main table(character_data).

Read the patch notes about files. Body issue we are aware off. https://github.com/DayZMod/DayZ/issues/138 < loot issue

just kill the AN2 for the time being.

replyed to in the issues post.