20 sec spawn time...

I have seen the spawn times greater than 20sec on servers that WERE set correctly.

A 20 sec spawn WILL give you spawns of 22+ seconds. Why? Because you catch a bad break on the delay.

.serverSpawnTime 20
.serverSpawnDelay 3

Will give you spawns of greater than 20 sec. Some servers are set even higher.

I don't know how it is figured exactly, but I suppose we best find out. I guess I really don't know how it works.

i got a fix for it...

dont die

nice Flip ..lol
Grassy (WD)
C0-Commander Wild-Diamonds
http://www.wild-diamonds.com/grassy/grassy.swf

I am not complaining, just commenting on it.

We have had the issue arise during match play, where the spawn time was greater than the settings indicate. I did not think that this meant somebody was cheating, and still don't. But I also don't like be under suspicion a witch hunt over this issue.

Dieing is the thing I do BEST!

what mustve happened is, the admin changed the settings to TWL's but didnt reset the server. new settings dont take effect until the server is reseted (stopped and restarted).

if you happen to kill a temamate or yourself the server adds a few seconds to punish you. Maybe this is whats happening.

well if they turned punish off (like your supposed to) that shouldn't happen. That's why pre-match tk fests are the way to go, test the punish and auto kick modes to make sure they are turned off.

Well actually in the ctf config file here at TWL, the spawnDelay is not specified... so no matter how many times you reset the server, it will still default to what it was set at the last time you specified it.
All the conquest configs have both settings in them, so you can see a range of times from spawnDelay to (spawnTime + spawnDelay)...

Originally posted by: THO
Well actually in the ctf config file here at TWL, the spawnDelay is not specified... so no matter how many times you reset the server, it will still default to what it was set at the last time you specified it.
All the conquest configs have both settings in them, so you can see a range of times from spawnDelay to (spawnTime + spawnDelay)...

Nice catch. I will update in a min.

Originally posted by: MelissA's Despair
what mustve happened is, the admin changed the settings to TWL's but didnt reset the server. new settings dont take effect until the server is reseted (stopped and restarted).

We have been using the BFSM for awhile now and the latest one, version 3j, has a default "Spawn Delay" of 3s. When we setup for a match, we use the TWL settings but we place them into the available sections in BFRM. Then we stop and restart the server to make them permanent.

Even with the above settings made, I have respawned anywhere from 14 seconds up to 26 seconds with a 20s "Spawn Time" (BFRM setting) set. I have heard from others on the server saying that they had 4 seconds.

After discussing this with several server admins that run both Windows and Linux game hosts, this seems to be common with BF1942.

Why is this happening? I have no idea, but I am sure it is a "low" priority fix to Dice/EA since this only affects match play and not public play. Why should they care about the varied spawn times on pub servers?

If Dice/EA were working for match play they would already have demo capabilites, auto screenshots, anti-cheats, etc.

Actually, I personally think there's a bug in the BFSM. Often times no matter what I load up in the .con file, when I refresh BFSM it still sticks to those default values it shows, spawnTime 15 and spawnDelay 3.
If you immediately hit apply, it does not change anything in the server. You have to move the slider a bit, and then hit apply, before it will actually change settings on the server.
Perhaps rented servers are different, but everytime our co-located server loads up a new map, all of the BFSM settings go out the window and it defaults to what is in the .con file. Hence we set up all our matches by uploading TWL's config files.
Again, maybe there is a setting somewhere to let BFSM's settings carry over from map to map, I don't know, our server doesn't deal with that.

But anyone curious about spawn times, look closely at the different .con files on your server, and check out those two values I mentioned above. I have never had this "bug" of BF giving me a random spawn time, it is ALWAYS within the values of 'spawnDelay' and 'spawnTime + spawnDelay'.

Originally posted by: Dreadk
well if they turned punish off (like your supposed to) that shouldn't happen. That's why pre-match tk fests are the way to go, test the punish and auto kick modes to make sure they are turned off.

Screw that! Can't mess up my BfStats.