Admining for skins

pest · **Admining for skins -** 10-23-2002, 12:22 PM

Let me start by saying that I strongly beleive that an admin should be able to set the rules for their server however they like.

Now that I said that, I also beleive that those rules should be clearly posted in the game (by auto kick or some similar means). Just saying no cheating is pretty vague. I dont really consider skins a cheat. If a server doesnt allow them, thats fine and I will honor their rules (aa.com and AAN for example). I prefer skins, but if no one else has them, then I am OK with that too. If I am on a server that doesnt patrol for skins, I am going to be using them because you can bet that 50-75% of the other guys on the server are using them also, probably a much higher percentage if the server is running custom maps.

I know this isn't the "PC" thing to say on this forum and I might just get flamed here or there for it, but its the way I feel. I am also pretty sure that I am not the only one that feels this way. Some "cheat" skins have as many as 4000 downloads and that is only the ones from this site.

Captain_McCusker · 10-23-2002, 01:57 PM

I agree with you, Pest. When you pay for a server you have every right to decide just how it's going to be run and on the flip-side should describe the rules in the best way possible. I, myself, have to determine a good balance of announcements for the server so these messages come across clearly, but I think you know the intention is there.

So, use "cheat" skins all you want. I really don't care. Just know that if they're detected on my server I'm going to ban you, so my advice is to make sure you've adjusted your skins before playing there.

pest · 10-23-2002, 03:46 PM

Dont get me wrong, I have no problem playing on a server where everyone HAS to use stock skins. I also wouldnt have a problem if the server forced you to use a skin of its choosing, as long as everyone has to do it.

On the other hand, I make no distinction between bright skins and 'realistic' custom skins. Who really knows what the 'realistic' skin looks like on the users computer. Sorry, a custom skin is a custom skin and cant be verified.

Maybe spearhead will have the answer.

rudedog · 10-23-2002, 03:57 PM

per the post over at TMT sv_pure will be working in spearhead. This should be the answer to our problems as rouge pk3 files go

wintersforge · 10-23-2002, 04:13 PM

Quote:

Originally Posted by rudedog

per the post over at TMT sv_pure will be working in spearhead. This should be the answer to our problems as rouge pk3 files go

that would be good and bad....how will they get around the custom maps, crosshairs, weapon skins...blah blah blah...doesnt that setting only use the default pk3 files?

rudedog · 10-23-2002, 04:55 PM

The sv_pure server option, when turned on, means that the server will send the client information about which files it is to use (and demanding that the client limit itself to only those files installed on the server) .. removing the ability to use custom models/skins/sounds etc while playing on that server if the server itself does not have those customisations.

The server requests checksum information about the .pk3 files being used by the client so that it can verify that the client is using the correct versions (i.e. not hacked ones).

The upshots of this are:

1) If you have custom .pk3 files, they will not be used when you are playing on a server with sv_pure set.

2) If you remove or alter your existing .pk3 files, you will not be able to join a server with sv_pure set.

3) If you edit or alter the Q3 binaries, you will not be able to join a server with sv_pure set.

The disadvatage (to you) of this setting is that you can't then use your cool new skins or sounds or HUD.

The big advantage is that you can be reasonably sure that nobody on the server is using spiked models or aimbots or anything else.

Captain_McCusker · 10-23-2002, 05:31 PM

Quote:

Originally Posted by rudedog

The sv_pure server option, when turned on, means that the server will send the client information about which files it is to use (and demanding that the client limit itself to only those files installed on the server) .. removing the ability to use custom models/skins/sounds etc while playing on that server if the server itself does not have those customisations.

The server requests checksum information about the .pk3 files being used by the client so that it can verify that the client is using the correct versions (i.e. not hacked ones).

The upshots of this are:

1) If you have custom .pk3 files, they will not be used when you are playing on a server with sv_pure set.

2) If you remove or alter your existing .pk3 files, you will not be able to join a server with sv_pure set.

3) If you edit or alter the Q3 binaries, you will not be able to join a server with sv_pure set.

The disadvatage (to you) of this setting is that you can't then use your cool new skins or sounds or HUD.

The big advantage is that you can be reasonably sure that nobody on the server is using spiked models or aimbots or anything else.

The disadvantage is almost an advantage if you ask me. Try your new hud mod/blood mod or skins out on a server where no one cares. Jumping on a server taking screen shots and playing half-assed can be annoying to those that are intent on just playing the game.

And furthermore, this gives the admin the option of screening the mods used on the server before allowing them. Maybe that's a little too admin-nazi for some people, but we know cheating will be curbed to a degree because of it.

wintersforge · 10-23-2002, 06:29 PM

i agree that the advantages outweight the negatives, but i know alot of us have a 100 mods cluttering up our MOH main folder.... evil: eek: oOo: