In T176035#2538269, @Aardappelvis wrote:

While your suggestions are interesting, they don't really change the core problem with the radio. The biggest reason that noone uses the radio is because noone uses it (obviously). People might try it once and drop it after they don't get a response after a few hours.

This is because:

1. The limited range. There should be white noise when communicating with someone far away, but they need to be audible wherever they are.
2. The limited availability. There was a time right around the release of .63/1.0 experimental, where everybody spawned with a radio + battery. I had so much fun meeting people at NWAF and having conversations on the radio back then. Also, the battery lifespan is too short if you want to keep it on 24/7.
   
   I think they'd have to make the radio have a map-wide range (and have the big backpack radio have no white noise or something), and remove the battery requirement first.

@Geez I was able to pinpoint the origin of this problem to the -noPause argument. Removing it from the command line arguments that started the launcher makes the .DayZProfile config takes over.

Yeah, I came here to open a similar task - same is true with baked tomatoes on PC and probably other vegetables too.

@Geez has this been getting any traction within the team?

Another point came to mind when watching this video. It is utterly unrealistic for someone to attach a codelock to a still moving gate. Attaching a codelock should also become a "hold-key-action".

In T167133#2348542, @BIS_fnc_KK wrote:

What game are you playing?

I have some further information:

Using the in-game settings to change the "Update In Background" setting, I can verify that after pressing Apply the "pauseMode" variable inside "[username]_settings.DayZProfile" is getting updated accordingly.

Hello Geez,

In T160583#2231228, @toupeira wrote:

The fix is removing the ability to cook grenades, it doesnt make sense and it is not realistic in the first place

In T160333#2228667, @Geez wrote:

Hello RoyBeer.
Since the fence cannot be built due to the rafters, this is not an issue as it does make sense - the rafters are in the way.
Regards,
Geez

In real life you'll most likely get kuru from eating the brain, eating other parts is way less harmful. It would be easy to add a script to human meat that gives it, like, a 1 in 10 chance to carry the disease, similar like the Unknown Food Can does with salmonella (iirc?). But I agree, something like a counter that goes up with every kcal of human meat (carrying kuru) would also make sense and could actually make human meat viable for a one-time emergency situation.

This is still an on-going issue. Either force-feeding should only be possible in front of someone and when they're tied up/unconscious or there should be a way lesser chance of catching kuru.

Indeed. Please keep the realism and rather expand upon it. You should be able to make decisions based on realism as much as possible as opposed to learning some "in-game lore" of how different systems perform in the name of balancing.

In T157709#2175860, @ProfessionalDead wrote:

I heard a reasoning against them would be people leaving harrassing notes, but (just like the ingame text and voice chat) notes could bring so much more value that would outweigh the bad interactions

In T157588#2173576, @Masgel wrote:

Technically you can by turning the flag into rags and then using a sewing kit on the rags to make a white armband.

Late to the party, but The Village was a vanilla and non-modded community server. @Geez

There you go

In T114685#2167411, @RoyBeer wrote:

This bug is still in. Even removing the batteries doesn't fix it. Only a rejoin does.

This bug is a big security issue because people who are actively using walkie talkies always have to fear their private talk might get broadcasted.

This bug is still in. Even removing the batteries doesn't fix it. Only a rejoin does.

Hey Geez,

Wish this would get a higher priority. It adds value to staying alive and apart from beards there's currently nothing else that does track a character's progress in a meaningful way.

This bug is still persistent on stable 1.10, even when inside buildings/under cover that would otherwise prevent rain from hitting the barrel.

Hello Geez,

It also limits the use of raincoats and NBC clothes as they are low insulation and therefore barely useful anywhere off the coast.

I used a hand drill kit to light a Long Torch, yesterday on Experimental servers. It still consumed the kit. @Geez

I can't see the screenshot (how do you download the file?), so my post is from my experience and feeling of the game as it is currently.

I can only agree with the people saying that you should have a radius of about 2-3m around you in which you can see almost everything (except of colors - or at least very desaturated), but then your vision should gradually fade into black.

What I find very important though, is that this shouldn't be instantly when you leave a lit place. Your eyes should have to adapt to the darkness, gradually becoming better adjusted to the dark (over, like, the course of 3 minutes) and be rapidly unadjusted again, once someone lights a torch into your face point blank.

This would add multiple aspects of realism to the game:
First it makes the torch more useful. Right now it only gives away your position and it will be even more the issue if darkness was made more navigable. Torches (especially mounted on weaponry) could be used in close-quarter assaults to incapitate a target adjusted to the dark.
Second, while it might be a good idea to light up your base, so noone can enter or move about easily unseen, it also makes you a target, standing literally in a spotlight, for outsiders.

TLDR: Up voted. Vision should adjust to Darkness (to a reasonable amount) over time. Adjustment should be destroyed by bright light.