Lady Kyrah

former is called shadow volumes, BIS objects always had a simplified model for this method because it's cost is proportional to the complexity of the shaded object. latter is called Deferred Shading and is how most modern games render shadows nowaday, the crenelation can be lessened by a smoothing pass but it's never gonna be perfect -> https://en.wikipedia.org/wiki/Deferred_shading most modern games use this.

Muzzle flashes are an art asset, they are not engine dependent (like 99% of things in a game).

My main issue is that your second poll lump a lot of statements together as if they where part of the same idea, i can't really vote on this because i only agree to some of the enumerated elements of each statement. Why not a multiple checkbox poll type wih each element being its own option/ this way people can cherry pick what they like and what they don't?

And you can do this right away, you don't even need to have it hardcoded in. Come on, everyone's watching.

For technical reasons bodies have to get removed, sooner or later, i will not argument this, it's pretty obvious as to why. A second reason to get rid of bodies is called INFLATION. The game spawn gear, this gear need to be consumed and recycled somehow, food is naturally consumed by players, same for bullets, but weapons and wearables are created much more often than they are destroyed 'naturally'. Making everything reuseable wouldnt be as much of a problem if nothing ever spawned (it would create a completely different set of design imperatives however), but it isnt the case.

Could you at least pretend to offer objective options when you create a poll? your options are biased by your personal opinion.

OP I suggest that you read the suggestion posting rules if it's not beneat you.

Because there is nothing worse than meeting a Leg0las08 and XxxKILLERxxX in any game that is all about immersion, here are a few suggestions to restrict name structures. First letter is capitalized and the rest is lowercase No symbols or numbers At least a single vowel and a single consonant per word. No less than 4 letters, no longer than 20. One to 3 wordsExample: Jeffrey, Lewis Baxter, Long John Silver Examples that would not work: Unr3@D4Bl3, KosLOL-AK47

Seems to be another reason to kill him before he gets any closer.

why stop there, carbs, fat, sugars add to this sugar rush and sugar crash.

Look ... this is just XML, not a binary format. The whole point of XML is to be both human and machine readable. It's as difficult as filling a configuration file... Plus the idea behind squad.xml files was that clan admins could update them in real time from the clan's web server.

"Hacking" XML "code"? Dude, XML is a standard thing...

Grenades have a 5 second fuse, that's a LOT of time to get in cover once the grenade "holder" got a bullet in his brain-bucket. That being said grenades where successfully used during the Vietnam war as a way to booby trap containers with lids and dead bodies, but the key element here is "surprise" really. While the idea of a dead man switch is appealing, do you really want to give more reasons to camp on hills without looting bodies?

No but i do hope there will be more use for it at some point.

If i can't be Kyrah This, i'll be Kyrah That. That's the entire point of first/middle/last name IRL

Laura Anne is not okay? or do you absolutely need the hyphenation? Well this is a basic idea, it's not perfect by any means and you can punch holes into it all the way you want unless we get our name chosen for us :D, write a better ruleset? 3 words is pently, i don't mind cultures that wish to be more verbose, but these are names we should be able to remember...

Well you should (normally) be capitalized, you have a proper name, you're not a chair or a fridge :)

I'm okay with this, as long as the "text" clan tag is just skipped, there is nothing i hate more in game than those stupid bracketed tags. The clan logo/arm patch doesn't bother me in the least tho.

Oh i perfectly understood what you ment, but it's simply not what you wrote. But no, you get the game cheaper as a thank you for trusting the developers and funding the project. You don't need to be praised for your decision, you already got something out of the deal. You would probably be entitled some extra goodies if, on the other hand you got a "founder pack" that would cost 2-3 times the final retail price, as a thank you for wanting to give more than the minimum. But they don't do that sort of thing.

And hence why i ask, why should the guns have the same specifications as their real world counterpart, what if they want to adjust muzzle velocity to make things more interesting for example? It doesn't make the gun less realistic, it would be like altering the propellant. And it would end any spreadsheet debates :)

Not having to design new guns from scratch? It's not that easy to come up with a gun that looks good and also look functional.

It was done in the mod. It was... not very good.

Following your logic buying the game now would mean no patches and having to re-buy at release. As kichilron said, you are rewarded for trusting the devs this early on by a reduced price, you will get the same game as anyone who will pay full price when the game goes gold. Also you get to play earlier. This isn't "space civilian" ( :) ) where you have the "filthy release players" on one side and the "awesome early adopters" on the other. That sense of entitlement O_O ...

Just for the sake of argument, the guns can be realistic while not being perfectly accurate clones of their real world counterpart, the devs are free to adjust weapon parameters right? just because it doesn't behave as the real thing doesn't necessary make it unrealistic. Hell, they could make the M4 the worst piece of shit ever, i mean it's just a 3D model with ballistic specs attached to it. I would be all for this even if it only stops a single person from diving into wikipedia for weapon specifications.

Slice this in about half for taxes and expenses, and divide it by the number of employees, then you can estimate how long they can keep a given person employed in that team. And yes, too many cooks do ruin the soup, having worked with other people in the past on multimedia projects, it's all fine as long as you don't have overlaps in competences. The more coders you have the more difficult the source code become to read, the more outdated the documentations become, the less clear the writing style become, the more often you have to do reunions with the coders to discuss how to tackle this or that problem. And that's just the code, it would be wonderful if every team member built a nice little brick that can be nested with all the other bricks perfectly, but that's not how it works, it's more like tetris board where instead of 12 shapes with 90° angles, you have 50 billion shapes and none of them fit euclidean geometry.