Battlezone Universe

Battlezone Universe => Archive Vault => Public 1.3 Beta 4 Archive => Topic started by: General BlackDragon on August 05, 2008, 08:27:17 PM

Title: BZC late joiner bug.
Post by: General BlackDragon on August 05, 2008, 08:27:17 PM
Please test this.

When ever someone joins late, all the clients get kicked?

-- This only seems to occur with BZC Demo so far. ???
Title: Re: PB4a late joiner bug.
Post by: Nielk1 on August 05, 2008, 08:41:37 PM
Was this stock or BZC? We all know you tend to cause 'cough 'cough issues with BZC.
Title: Re: PB4a late joiner bug.
Post by: General BlackDragon on August 05, 2008, 09:33:29 PM
I was testing the demo, but nothing BZC specific could do it?

Eh, maybe im wrong...whatever.
Title: Re: PB4a late joiner bug.
Post by: Red Devil on August 05, 2008, 09:34:51 PM
I haven't observed/experienced any kicks due to late joins.
Title: Re: PB4a late joiner bug.
Post by: Steeveeo on August 05, 2008, 09:46:03 PM
Nothing here.
Title: Re: PB4a late joiner bug.
Post by: General BlackDragon on August 05, 2008, 09:47:23 PM
Could it be BZC's DLL? (gsh?)
Title: Re: PB4a late joiner bug.
Post by: Commando on August 05, 2008, 11:14:56 PM
I didn't get that when both Spawn and feared-1 joined my game 30 minutes in.
Title: Re: PB4a late joiner bug.
Post by: General BlackDragon on August 05, 2008, 11:47:46 PM
Yea, then it's something bzc related ?

but what could cause it?
Title: Re: BZC late joiner bug.
Post by: bigbadbogie on August 06, 2008, 12:04:05 AM
Since you are one of only 2 people with access to BZC, why the heck are you asking us??
Title: Re: BZC late joiner bug.
Post by: General BlackDragon on August 06, 2008, 12:10:55 AM
Was hoping GSH might give some hopeful glean as to wth might happen.
Title: Re: BZC late joiner bug.
Post by: GENERAL MANSON* on August 06, 2008, 03:51:36 AM
Quote from: General BlackDragon on August 05, 2008, 08:27:17 PM
Please test this.

When ever someone joins late, all the clients get kicked?

-- This only seems to occur with BZC Demo so far. ???

Ive had that happen with 1.2 and pb41.3 havent tried pb4a yet.