Bug#433671:

[Victor Luchits]

> Why would it be preferable to force the download of these modules,
> "pure" or not? Why can't the binaries that ship with the client just
> be used?
> 
> Also, the Debian packages contain some bug fixes already, and I'm sure
> there will be more to come. From what you've said, this means that
> clients connecting to these "pure" servers are still going to have a
> problem anyways.
> 
> Also, Michel has a point. This is a problem when cross compiling.

Well, it means that
a) custom modifications are automatically downloaded and used by
connecting clients
b) all clients are guaranteed to run the same client-side module on the
same server
c) it's a cheating protection measure

Of course all of the above may be avoided using a custom-compiled binary
but we have BattlEye for that..
Not that I like this wicked system, but we have to add some cheating
protection measures so that online gaming experience is not ruined for
the majority of players by some script-kiddie.

As for the patches, we'll gladly accept bugfixes. The patch for original
bug report of Michel Dänzer is already in the tree for 0.32

-- 
Best regards,
 Victor Luchits

Bug#433671:

[Victor Luchits]

Filenames for game modules need the arch suffix so that they can be
distinguished at load time. All game modules for all archs are packed
into a single .pk3 file which is used for "pure" servers. Clients that
connect to "pure" servers are forced to download, unpack this .pk3 and
load the game modules of their arch. A typical modules.pk3 file (which
is essentially a .zip file) looks something like this:

game_x86.dll
game_x64.dll
game_x86.so
game_x86_x64.so
...

-- 
Best regards,
 Victor Luchits


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]