facoptere

yes I forgot but I put in on on FR129 too.

What are you talking about? diag_ticktime is just the clock (the most precise clock we have). It starts at 0 when the local game engine starts, and has a 1 second increment, whatever the server load is. Here, the piece of code is called every 60 seconds.

SmokeShellYellow is not on current vanilla DayZ mod.

you are not banned on FR130. I don't manage UK130.

yes "admin ban" without reason and you will be banned few minutes later. It's a bug I don't know where it comes from.

Which filter: scripts? publicvariable? setvariable? What is the content of the log file that corresponds to that filter?

Anyway this is the wrong forum. You should contact Breaking Point mod team, it's up to them to provide some working filters.

1st person is on FR129. FR34 and FR130 are "recruit" an so 3rd person is ON. The problem is much more how Arma2 engine did their 3rd person. The camera should move to 1st person when the player is watching what is behind an obstacle. Ok I found you. You were banned because you were cheating. I think it's wallhack since 'shell' is manual ban from me, and most of the time it's wallhack (stuck in hospital for example). you are unbanned now. you are not banned. when you have such message, try again on next minute.

you are not banned

I need more info, your UID for example, or the full ban message. you are not banned. No need to write about "Admin ban with no reason", unban is automatic few minute later. I am not responsible for these bans, it's a battleye bug.

no need to write about "Admin ban with no reason", unban is automatic few minute later. I am not responsible for these bans, it's a battleye bug.

I can't say SteeMrs is a cheater.

I can't see any Louie9 on FR130.

you are unbanned

Sorry I can't do that.

Very good, theLastEmp, you got it. The other bug is non empty loot pile : the loot pile is blocked till everything is gone. Since nobody takes empty cans... I think this bug is still not fixed for 1.7.8. I would add that stuff on a lootpile can't be spawned if another lootpile is closer than 2 meters. What has been fixed in 177 for loots (among other things): 1/ timestamp if more reliable, cleaning more reliable on serverside too 2/ spawn is done one after another, so same random number generator gives differents loot item. 3/ a check is performed to avoid duplicate item, such water bottles. 4/ the number of total lootpiles are controled to avoid fps drops. Nobody knows why fps drops, maybe it's the AI, maybe it's another other reasons. Loot & zombie spawns are done every 8 seconds, so the lag you should get should have this period.

The logic has been explained already: once some loot is spawned in a building, this building is blacklisted for several minutes (10 maybe) for all gameclients (loots around you are spawned by your gameclient). You won't find new loot during this time, even if you go to the forest or if you disconnect. Bugs are well known. First of them is some time drifts between clients and server : ArmA 2 engine cannot garantee the same time to everyone, so timestamps used to blacklist can be wrong. And if the server is up since more 3 hours, more problems occurs since cleanups and syncs are not done properly. Basically Arma2 does not suit to DayZ mod, since part of the code and time spent by the devteam is try to find some workaround to all these bugs. So your study is pointless if you don't know since when the server is up, how many other players are in your area, etc. I agree about your other point however.

I can't find any "Doyen" on any of the 3 servers.

Invizzz did not disconnect properly (Alt-F4 maybe), but he died just before. I don't know the mod behavior when a player disconnect like that. I don't know any TheSealHD.

ban with no reason = unban few minute laters.

To clarify things: By default all functionalities is fa_hivemaintenance are disabled. "IGNORED" means that the amount of vehicles of each class is controlled (it's one functionality among others), and some vehicles are seen as "extra" vehicles. Because someone changed the vehicles list on the hive side for all public servers, without any detailed changelog, after the 1.7.7 was released. The list in dayz_server.pbo is simply not up-to-date. Note: if you want to control vehicles amounts, updated version of config.cpp from dayz_server.pbo should be: Vehicles with 1 as damage are 100% damaged, so are not spawned by default. They still exists in the hive. They is a script on hive side that "recycles" these vehicles (new respawn, new loot, new damage, new fuel level) regularly. This functionality exists in fa_hivemaintenance too, but it unuseful since I have been told that the script on hive side was working properly. fa_hivemaintenance never deletes any entry in vehicle list stored in hive. If some vehicle are missing (deleted from the list you can see in HiveExt.log) this is the result of hackers, or a bug (or strange logic) on the hive side script. I don't think that fa_hivemaintenance lets vehicles in debug area. This may be the result of hackers. It's quite unlikely that it's a bug of the hive side script too. fa_hivemaintenance can add missing vehicles, but they will be destroyed less than 24h afterwards, since on the hive side there is a script that delete vehicles created by gameservers (and this scripts works very well, nobody never complained about this one :) )

You are unbanned, this was a temporary ban (10 hours). The problem here is using a hack for infinite ammo. Most of DMR users are not kicked/banned because of their weapon. You will be banned again if the server detects suspicious activity.

This means you edited server.pbo. Do not edit server.pbo if you don't know what you are doing.

"ignored" means that the vehicle exists in the hive but won't be spawned since this vehicle is outnumbered according to its class (you have too many vehicles according to vehicle list defined in server config). Uncomment VEH_MAINTENANCE_IGNORE_UNKNOWN if you want these extra vehicles. A vehicle still exists in the hive even if its damage = 100%, and is recycled (vehicle parts and fuel level redefined, random position chosen) on startup if VEH_MAINTENANCE_DONT_BE_SMART is in comment.

"No warning" server restarts are done when the server is hacked by cheaters. Sometimes they are ruining performances on serverside, or on network layer (both on netcode layer and UDP layer). The more I wait, the less I can warn the users since the server becomes unresponsive to RCON commands (used to broadcast a message to the players and to shutdown the server). So I try to display a warning, but in parallel I kill the server process after few seconds anyway.