Ask the [Dev]s a (?)

[sweedensniiperr]

When did requiem rejoin the team?

[Spush]

Requiem is the founder, and I believe he's always had founders tags though.

[rodrigoma]

It is entirely possible.

I see what you did there

[Trooper909]

Requiem is the founder, and I believe he's always had founders tags though.

He had retired tags for awhile then randomly posted something than got the red tags again as far as I remember.

[doop-de-doo]

Karthus' all powerful Requiem. lol. Sux that db seems to be on shore leave.

[ShockUnitBlack]

Jafar with Hind sig. Somethin's goin' on.

[Rhino]

lol, and Leusch has a ground effect vehicle in his sig too!

[ShockUnitBlack]

Well he dropped a pretty blatant hint in his latest dev post and Stigger made that pretty little Hip a while back, so...

Also -

Khamisiyah?

[Rhino]

One flew in your theory is if we have a hind, why are the Polish ComFac making their own one and we are helping them out with it?
https://www.realitymod.com/forum/f128-p ... -hind.html

[Doc.Pock]

*aliens guy*
Devs.

You want grober to model, maybe your hind isnt as good as his could be or something.

Sent from my magic contraption using Magic

[tankninja1]

Will some DB mod changes be brought back in 1.0 some of them were very useful like the one cashe at a time on insurgency.

[WeeD-KilleR]

Will some DB mod changes be brought back in 1.0 some of them were very useful like the one cashe at a time on insurgency.

Some (like the hats) yes. BUT NOT the cache thing. That just made the game more action focused, gave away the plan b for blufor. A compromise would be okay: 1 cache known on the beginning and a second one spawns known after the BluFor got enough IP.

I really, really hope that change doesn't make it into the game. It'll kill INS for me.

PS: Yes, I know I techniclly wasn't "allowed" to answer that, but I had to.

[tankninja1]

Some (like the hats) yes. BUT NOT the cache thing. That just made the game more action focused, gave away the plan b for blufor. A compromise would be okay: 1 cache known on the beginning and a second one spawns known after the BluFor got enough IP.

I really, really hope that change doesn't make it into the game. It'll kill INS for me.

PS: Yes, I know I techniclly wasn't "allowed" to answer that, but I had to.

Unknowns are just annoying though they always seem to get picked off in rapid succession supposedly without "ghosting". Maybe a delayed unknown spawn would be a good compromise, like after 10-15mins an unknown spawns after a known assuming the known is still up.

[Pvt.LHeureux]

Some (like the hats) yes. BUT NOT the cache thing. That just made the game more action focused, gave away the plan b for blufor. A compromise would be okay: 1 cache known on the beginning and a second one spawns known after the BluFor got enough IP.

I really, really hope that change doesn't make it into the game. It'll kill INS for me.

PS: Yes, I know I techniclly wasn't "allowed" to answer that, but I had to.

Only 1 cache =

No "DON'T SPAWN ON UNKNOWN FUCKING IDIOT"
No cache ghosting
No unknown cache hunter squads
More action focused on the actual cache, less boredrom for insurgents
"Common blufor, attack, what are you doing, having tea at the airport?"

[WeeD-KilleR]

100 points for both. My compromise was that the second one SPAWNS KNOWN after Blufor got enough IP. Means that there is NO unknown. Just known caches. Same effect while providing blufor an plan b if they are not able to get the first cache.

[Pvt.LHeureux]

100 points for both. My compromise was that the second one SPAWNS KNOWN after Blufor got enough IP. Means that there is NO unknown. Just known caches. Same effect while providing blufor an plan b if they are not able to get the first cache.

Agreed, having unknowns gives the possibility to make "fake caches" aswell, that is cool. Just have to tweak the 1 cache system so the cache stays unknown for a longer period of time, etc.

[doop-de-doo]

Whoa whoa...back on topic.

Does a "certain" desert battle replacement map fix the floating infantry issue?

[AFsoccer]

Whoa whoa...back on topic.

Does a "certain" desert battle replacement map fix the floating infantry issue?

Huh? What is a floating infantry issue?

[40mmrain]

On kashan, overly jagged peaks result in some kind of terrain warping at long distance, and you can see people that are actually behind the tops of hills. This has been discussed, the only fix is to make hills less steep.

also, I remember thoroughly discussing the unknowns in DBmod feedback threads. I think they are a good element, but they place too much responsibility, and faith in the player. Insurgents who dont understand the game squander their oppurtunity to make the unknown a useful force dividing tool, by spawning on them, and walking away in plain sight with PKMs and such. Ive had great success treating unknowns as full knowns, or having small, discrete forces on top of unknowns that intercept cache hunters, and let the team know if the enemy has found your cache. Bad players leads to reductionist tactics of simply NEVER being near an unknown which gives the opponents a free lunch if they have any brains, and are searching for unknowns. With a totally experienced and well led team, the unknown makes the game more dynamic, and interesting, but harms the game otherwise.