InstaUnlagged CTF CAPTURELIMIT Problem

[Goop]

Okay, I'm probably missing something really dumb, but my InstaUnlagged 1.2b CTF server seems insistent upon keeping the CaptureLimit at 6.

The server cfg file has set capturelimit 10, and the map rotation is also setting the capturelimit at 10, ex:

set m2 "g_gametype 4 ; capturelimit 10 ; map wtf16 ; set nextmap vstr m3"

Where else is the capturelimit value set??

Server: 72.52.162.213 : 27960
Maps, Stats: DemonExile.com

[^misantropia^]

Weird. Does it work when you fire up vanilla Q3?

[Goop]

Just tried it with vanilla Q3 and the capturelimit works fine, so it's localized to InstaUnlagged 1.2b, I just can't seem to find what is causing the problem.

[Goop]

hmm, I tried setting it to 10 with rcon, and the server immediately set it back to 6. wtf?

[Goop]

Well, through the process of elimination I discovered that when I added a bot, the server then forced a certain capturelimit. Anyone know what might cause this?

[^misantropia^]

I'd wager a bug in IU. Pity the developer disappeared off the scene, so it probably won't ever get fixed.

[Goop]

Solution found - most of the links out there for InstaUnlagged 1.2b are actually an older beta. In the popular one, the qagame.qvm is dated 10/31/2002. The newest version had a qagame.qvm of 9/26/2004, and this version doesn't have the CAPTURELIMIT bug mentioned at the beginning of this thread.

A Google search of "IU1.2Beta3" should bring up some info, and the sticky should be updated to link to this version.