Betabyte (DayZ)

Many thanks man.

Place 1st note in Obvious place: supermarket for example Gives a puzzle to get to note 2 Note 2: same Note 3: congratulates player for solving them, leaving best equipment as a reward.

I did the exact same thing, sickness went to red, but after 5 min yellow again, and after 30-ish minutes GONE Just wait it out. With charcoal eaten too

Solution 1 & 2 of combat logging fixes everything if: Solution 1: your disconnect, your body stays there for 1 minute (you need enough time to loot him/her). Offender cant join or respawn during that time. Solution 2 : you can enter 1 server every hour without a penalty. after that 30/60/90 minutes wait before you can join another (Depending on DISCONNECTS). If you reconnect the same server => you must wait 5 minutes to join . This small penalty intended for people with shitty internet. or RL interruptions. The 5 minute rule is to protect players from their bad internet, not punish them. A dayz player is a bohemia interactive customer and players with bad internet should not be punished. The SYSTEM needs to protect us from exploits, not the players

the problem is that you only see detailed status of your stomach, and only "emergency" status of actual food and drink levels. Those 3 things are seperate. Example: i had the same issue, was stuffed like a Turkey tonight, but my water was actually just above emergency. so i didnt heal either. Then i got the thirst warning. I drink like 5 canteens at a water pump. I was sick first (close to vomiting), but luckily didnt puke, and after 3-5 minutes i was starting to heal, this time well fed AND hydrated. So yes you can drink OR feed your tummy full, but you need both to start healing/regenerating. The game should have like erhm, "buff" status icons for food and drink, so we can track it better. Im sure the dev team isnt happy with current message system.

@ap_norris : yes, and that would be no problem at all. You would then just logout somewhere safe.

@ synystr: that variable should be on your account in the main hive, so that hackers cant fiddle with it. If you put it in the dayz program, hackers reach it easily. They would never be in combat. Trying to alter alt f4 behavior is futile, you can end process in taskmanager or just pull the plug.

I meant the loot of the dead one ofcourse. Currently(113860), all gear despawns when somebody logs off, so why not fix that by requesting a copy of that as "loot injected" by the main hive. Remember: the offender dc'ed already and is in his 120 sec penalty or LATER.

cgnoodlet: at the server. The game uses an mmo-like architecture. But with 40 player "realms" (servers).

@milspeczombie: because zombies are bugged right now. When zombies are "done" , the 10 second rule should go ofcourse. Right now you can get ambushed out of nowhere, like a zombie you aggro without knowing cuz hes running thru walls etc.

@Nanoton and @submarine: exactly! @alcapwn: agreed with first statement, it should be serverside. Disagree with the second though: the main hive containts the loot you are carrying, and that loot must be available to somebody who kills you, even AFTER the 120 sec i proposed in op. Maybe the current server should in that case (when someone alt f4's and gets killed after) create a copy of all loot, tell the main hive, and then the main hive should delete the character.

btw the offender who got killed should respawn with a permanent hat that says: "i alt f4 on first danger", -20% max health for a week :D A parody of "i fuck on first date".

@ gdaddy: yes maybe 120seconds is too long. hmm waiting 30 minutes is abit too harsh too no ? what about 15 minutes? And in ALL circomstances, give the abilty to still kill and loot the offender in the 120/60sec time. @Alcapwn: yes you are right. but the 120 sec rule would be run on the central hive. Dean&co wants to give server admins the power to create private servers. This feature should be Always on, regardless of private OR public. And the main hive server delivers for 250k players and counting, so every cpu cycle matters then, no ?

Actually, while i like your idea about the 30 seconds , i think we must consider the problem that all these checks need to be computed by the server. This could be a problem when moving to higher player numbers.

@Synystr : killing a character would punish someone with a flaky internet connection.