sv_pure works for windows and linux servers.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeremy
Sent: Monday, October 15, 2007 1:06 PM
To: hlcoders@list.valvesoftware.com
Subject: Re: [hlcoders] sv_pure broken for mods?
--
[ Picked text/plain from multipart/alternative ] I was running a windows
server at the time for my test. Does sv_pure work on windows servers as
well? I got it from the hldsupdate tool. I'm not familiar with what
goldsrc is.
On 10/15/07, Mike Dussault <[EMAIL PROTECTED]> wrote:
>
> Are you running a goldsrc server? sv_pure should be there in a Source
> Linux server.
>
> As far as sv_pure with mods, it was designed to work with mods and I
> just verified it. Made a fresh mod, build a map with a custom
> material, connected with sv_pure 1, modified the material on the
> client side, connected again, and the server booted me.
>
> sv_pure 2 and sv_pure 1 work virtually the same. sv_pure 2 just
> hardcodes the whitelist to look like this:
>
> ""
> {
> sound\... from_steam
> models\... from_steam
> materials\... from_steam
> }
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Mulchman
> Sent: Thursday, October 04, 2007 10:49 AM
> To: hlcoders@list.valvesoftware.com
> Subject: RE: [hlcoders] sv_pure broken for mods?
>
> We also have the issue where typing "sv_pure" on a linux server from
> inside the 'console' saying "Unknown command sv_pure"...
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy
> Sent: Thursday, October 04, 2007 09:21
> To: hlcoders@list.valvesoftware.com
> Subject: [hlcoders] sv_pure broken for mods?
>
> --
> [ Picked text/plain from multipart/alternative ] Anyone manage to get
> sv_pure working for mods?
>
> I've defined a pure_server_whitelist.txt properly as far as I can
> tell, I enable pure stuff on the dedicated server
>
> sv_pure 1
> sv_pure_kick_clients 1
> sv_pure_trace 1
>
> I join the server with the client, and observe several things.
>
> First, on the client, if I type sv_pure it prints the description,
> along with The server is using sv_pure = 0 (no whitelist).
>
> which is wrong according to the server, which prints Current sv_pure
> value is 1.
>
> Second, the server didn't print out anything as a result of the
> sv_pure_trace 1 on this initial client join, am I missing something
> with this?
>
> I'm using hlds, as per
> http://www.srcds.com/db/engine.php?subaction=showfull&id=1097362093
> with our mod folder copied over.
>
> I can verify that the server is at least printing out the crc caching
> stuff.
> I can also verify that changing a file that is crc checked on the
> server has no effect on the clients ability to join, and there is also
> no resulting error message or kick as would be expected.
>
> Caching file CRCs for pure server...
> (Unique ): [DEFAULT_WRITE_PATH]\materials\effects\blood_gore.vmt -
> 3929000697
> (Unique ): [DEFAULT_WRITE_PATH]\materials\effects\blood_gore.vtf -
> 4191249401
> ...
> (Unique ): [GAME]\materials\effects\water_highlight.vmt - 1986976483
> (Unique ): [GAME]\materials\effects\yellowflare.vmt - 2841543358
> (Unique ): [GAME]\materials\effects\yellowflare_noz.vmt - 2384634143
> ...
>
> (Unique ): [DEFAULT_WRITE_PATH]\models\player\pyro\pyro.dx80.vtx -
> 2015996037
> (Unique ): [DEFAULT_WRITE_PATH]\models\player\pyro\pyro.dx90.vtx -
> 2080765850
> (Unique ): [DEFAULT_WRITE_PATH]\models\player\pyro\pyro.mdl -
> 2757397667
> ...
> Finished caching file CRCs for pure server in 10 seconds.
>
> So it appears to be working to some extent server side. My whitelist
> is pasted down below.
>
> whitelist
> {
> //
> // 3 modifiers are allowed on file specifications:
> //
> // from_steam - only check the Steam cache for the file
> (ignore
> anything on disk)
> // allow_from_disk - allow the file to come from disk
> // check_crc - used with allow_from_disk - server does
CRC
> checks on the client's file to make sure it matches
> //
> // The default modifier on all files is allow_from_disk. Thus,
all
> files can come from disk and don't need CRC checks unless
> // allow_from_disk can be set at the same time as check_crc. Use
> the +
> character in between them to signify this: allow_from_disk+check_crc.
>
>
> //
> // Three types of file specifications:
> //
> // 1. directory\*.* - refers to all files under the
> directory
> // 2. directory\... - refers to all files under the
> directory
> and all directories under that (recursively)
> // 3. directory\filename - refers to a single file
>
>
> //
> // By default, when in pure server mode, most content file types
> are only allowed to come from Steam.
> //
> materials\...
allow_from_disk
> materials\effects\...
> allow_from_disk+check_crc
> models\...
allow_from_disk
> models\player\...
> allow_from_disk+check_crc
> models\grenades\...
> allow_from_disk+check_crc
> models\projectiles\...
> allow_from_disk+check_crc
> models\flag\...
> allow_from_disk+check_crc
> shaders\...
> allow_from_disk+check_crc
> sound\...
allow_from_disk
> sound\sound\player\footsteps\...
> allow_from_disk+check_crc
> sound\buildable\sentry\sg_scan1
> allow_from_disk+check_crc
> sound\buildable\sentry\sg_scan2
> allow_from_disk+check_crc
>
> //
> // Allow custom player models. Don't do CRC checks on them because
> the clients may all
> // have different custom models and the server won't have them all.
> //
> //models\player\... allow_from_disk
> //materials\models\player\... allow_from_disk
>
> //
> // Allow custom spray decals.
> //
> materials\temp\... allow_from_disk
> materials\vgui\logos\... allow_from_disk
> materials\vgui\logos\ui\... allow_from_disk
>
>
> //
> // (Uncomment and edit these for mods).
> // Allow mod resources to come from disk.
> //
> // materials\mymod\... allow_from_disk+check_crc
> // models\mymod\... allow_from_disk+check_crc
> // sound\mymod\... allow_from_disk+check_crc
> }
> --
>
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlcoders
>
>
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlcoders
>
>
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlcoders
>
>
--
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlcoders
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlcoders
