Lady Kyrah

Agreed OP not only make ammo rare, but adjust ammo spawning based on the amount of ammo the players have in their possession + ammo already spawned. The issue with most rare goods in games is that players will hoard them until they have enough of it to ignore that it's a rare commodity. I wouldn't be surprised if no bullets would spawn for several days on servers.

This is not world of warcraft, nobody is losing any money if you stop playing.

Aren't tanks doing like... 1 mile per gallon or less? Thing is... tanks bring a solution to a problem that doesn't exist in the game...

I don't think they care, if anything that's the kind of post they wear as a trophy.

I've always been for small civilian helicopters, but nothing more, especially not with any guns or armor.

I do see one issue tho, people are getting used to the current state of the game, and people today buy it expecting "this".

You're watching too many movies.

I'm sorry?

Arma had farm animals and dogs before, so far i havent seen anyone whine when they get killed. And you can be as heyneous as you want against pixel characters, they dont exist.

Votes serve absolutely no purpose but why not.

I'm partial to the Exile one.

I want THIS SOUND to play every-time someone log in :)

Who you where killed by doesn't consist of a hack prevention. Flagging players only encourage suspicion. Kicking is not allowed by server operators and i don't think this is going to change. Server operator are PLAYERS not admins, and that would imply that they have to be trusted, which we have seen with the mod, is a terrible idea. Hack prevention is done through code server side, not with "neighborhood watch". And it's not just about detecting hacks, it's also a question of hardening the server, i mean why is it even possible for a client to "create" a hacked magazine? Loot is created by the server, there is no point where it should even listen to the client for these things. The only thing i can point is "remains" of the way arma work.

Ah hey i'm expecting those who will scream bloody murder against this :)

Sorry to be blunt but... you CAN play a different game, a game doesn't have to be everything for everyone.

You're overthinking a game that is mostly using "handouts" of arma games as it's base assets.

It's not how it work really, the server doesnt just "follow" the client just takes preemptive actions which may be invalidated by the server. Your client does the jump, yes but the server has the last word, if the server deny the jump, your client will snap you back to the position you should be at as the jump effectively did not happen. It's rare that client and server disagree on that sort of things tho, unless you're cheating.

Why the hell do you need to jump anyway, this isn't CounterStrike360bunnyhopnoscope.

There is no timer, every-time you log out your character stay in the game for 30 seconds.

Bodies have an inventory, clothes, ,Bodies have a position, a rotation, a pose, collide with bullets and are interactive. In most engine that's considered an "active" object and DOES use a valid amount of CPU and bandwidth. Game engines do not consider every objects as unique little snow flakes, there is a tree of objects with more or less functionalities and bodies do not fit in the same category as trees or houses for obvious reasons. If i take the example of the torque engine, which is the one i'm familiar with familiar with: A player character would be: >SimObject (object is part of the simulation) >> NetObject (object is synchronised on the network) >>> SceneObject (object exist in the 3D world) >>>> GameBase (object can process ticks and has modifiable parameters) >>>>> ShapeBase (object has a visual, 3D shape) >>>>>> Player (object can be controlled by a client) A zombie would be: >SimObject (object is part of the simulation) >> NetObject (object is synchronised on the network) >>> SceneObject (object exist in the 3D world) >>>> GameBase (object can process ticks and has modifiable parameters) >>>>> ShapeBase (object has a visual, 3D shape) >>>>>> Player (object can be controlled by a client) >>>>>>> AIPlayer (object controlled by an AI engine) We can see here, that, in this example, a zombie is an object that is potentially as resource intensive as a player (it has all the features of a player and some more, i believe the RV engine use the same system) Now here is for example an item that you can pick up on the ground: >SimObject (object is part of the simulation) >> NetObject (object is synchronised on the network) >>> SceneObject (object exist in the 3D world) >>>> GameBase (object can process ticks and has modifiable parameters) >>>>> ShapeBase (object has a visual, 3D shape) >>>>>> Item (object can be interacted with by players, usually a pickup) We can see that while an item may not move at all, it still inherit many properties that are not entirely necessary because you do not build a unique class per object (which result in horrible snowflake code), so even if we don't strictly need it, an item can still process ticks (useful to make it decay) and could technically "move". What about things like trees and rocks and everything that represent our static world you ask? Torque (for example) has a special resource friendly class for this: >SimObject (object is part of the simulation) >> NetObject (object is synchronised on the network) >>> SceneObject (object exist in the 3D world) >>>> TSStatic (object has a shape and can be collided with) That is much shorter right? well here TSStatic is one of the most hated class on torque because of how messy it is (it has it's own code for a lot of things just so it wouldn't inherit of the features in GameBase/ShapeBase) The specificities of TSStatic is that it cannot move, it is barely networked (it's position is never updated on the clients, therefore it CANNOT move). While this is by far the most efficient object you can have in the game world it lacks many many features to be useable for anything but decoration. What does any of this has to do with DayZ? I don't know much about the RV engine, i'm sure that like torque it has it's shortcomings, no engine is perfect, but a lot of engines are very simmilar and have a lot of "look alike" features. THere are many ways to write an engine but only a few are reasonable and logical. In the case of torque, the most logical way of handling lootable dead bodies would be to detach the player from his body, effectively turning it into a "soul-less corpse" unable to do anything, and then set it in a death pose. It has the advantage that it's inventory will be intact and it's just a matter of letting looting players access it. The way DayZ bodies work is most likely very close to this. What's important here is that those objects are STILL player objects with all their attached features. So like zombies, they are a non trivial resource drain.

Nice suggestions, now here are a few of mines to complete this and prevent it from being too much like a player mount feature: -Animals may be hurt and/or wounded the same way players can be, broken bones for instance. -You may use medical equipment designed for humans (drugs) but it may very well have adverse effects (i don't have the details but some drugs do NOT work on a horse for instance). -Animals come with random desirable and undesirable traits that determinate their obedience, agility/clumsyness, and so on. You may find yourself with a dog that may be very disobedient and cannot be commanded properly, yet will still perceive strangers and hostiles around you. Bottom, line, there has to be a chance that your new animal friend will NOT become what you want him to be.

I like the idea that your guy might end up dozing off randomly if he is tired, like... some guy on sniper duty just nod off as his friends are looting the village nearby, and no one is with him to wake him up :p It could be an interesting system if when in a tired state, the danger is that your character might doze off during low intensity situations. But i cannot find a sleep mechanic that i feel is satisfying, even if logged off time counting as sleep seems more than fair to me. After all, this is not a subscription based game, devs have nothing to gain by encouraging you to play more. I used to play a game called "a tale in the desert" and you could select "offline actions". It allowed you to automatically collect common resources that are dull to harvest (grass, wood, sand) while being offline. It was less efficient than doing it by hand but it ment that if you needed a little bit of wood and where at the end of your session, you could get the wood auto collected when logged off (you DID need the right tools and right logoff location!)

dead bodies have to go regardless, do you prefer that the game spend processing time tracking live or dead players. Add to this the loot spawn mechanics, thats easily tens(hundreds?) of thousand objects that have to be tracked at some point. If anything, bodies should go by themselve in 5 minutes or less. Considering that the game spawn loot all the friggin time, that bodies disappear with all their gear is a good thing. Helps to keep the gear inflation under control.

it also takes too little time to recover from anything, it makes status effects a mere inconvenience. To take example with cataclysm-dda (and many zombie survival stories relate this kind of things), a bad encounter with a zombie mob left my character near dead in an abandoned cabin for more than a week, surviving to it was a miracle and recovering from it took a while.

Curious, tho they still understood the loss of energy was not instant. At the same time with the tools of the time it's pretty damn hard to accurately measure a projectile's curve. I suppose they assumed that at certain speeds it would overcome gravity fully before starting to drop. I don't know man, it's a reasonable conclusion to the fact that cannonballs are fired in a straight line but still end up dropping back on earth :) But by the time cannons where used by infantry this misunderstanding was solved. Come to think of i... did they even have parabolic equations at that time?