Back to Medal of Honor: SpearHead

Honesty Config Rule Change

Historical capture recovered from the Wayback Machine · captured 2003-09-14 · 26 posts
All SpearHead Ladders:

Honesty config is no longer a rule. It is no more. Dead. see ya later. Toast.

More than likely many teams will be confused for a small period till word gets out, so plz be understanding if any teams still think its a rule. This is effective 7/20. Thus no disputes involving the honesty config anymore from here on out.
__________________________________________________________________
MoHAA Game Admin
CoD Game Admin
Send Email
why the hell didn't i think of that? wait, i kinda did. it's still setting those things, but with the help of a modified MAM pak. but we could do away w/ it too i guess, i mean, so long as we have another cheat protect in store to replace it..... we DO have one already lined up, right? right?
Post edited by {GP} Grin Reaper at 7/20/2003 3:27:28 AM



When the toast is burned
And all the milk has turned
And Captian Crunch is waiving farewell
When the Big One finds you
May this song remind you
THAT THEY DON'T SERVE BREAKFAST IN HELL
Originally posted by: n3xUs

...and remember where those 2 middle fingers go.

-N3xus.


up both nostrals. that's so cool. twice the fun

twice the fun... hmmm .... [the dots continue to trail, unfortunately, the trail leads to:
...............
_______________·j the gutter

and btw... who's this n3xus bitch? isn't that the stuff i see when i walk into the hair cuttery? with the queer guys and not so (but striving to be) hot chicks sponsoring hair care products?

go shampoo your hair, maybe you'll get the urge to herbal and (bitch and) moan there, too
Post edited by {GP} Grin Reaper at 7/20/2003 3:33:45 AM



When the toast is burned
And all the milk has turned
And Captian Crunch is waiving farewell
When the Big One finds you
May this song remind you
THAT THEY DON'T SERVE BREAKFAST IN HELL
Originally posted by: n3xUs
Oh i get it. YOU guys take the fucking easy way out. instead of dealing with problems involving cheaters and people with questions. You take the easy way out. Great ladder you have going on!

So now, you'll have alot more clans complaining about someone using no fog and this and that. You've digged yourselves a mighty hole by making this "rule change". Running away from thr problems. This is truly pathetic. You guys are pathetic. Think about it for a second, you'll get twice as many clans bitching and moaning about those little cvar commands/cheats. After every single match.

I just hope you have something planned, something better maybe. I can't beleive it, you guys have a "0 cheat" policy but yet your oppening the doors to all those lazy cheaters that use the no fog and ect...

Well from this moment You guys get both of my middle fingers up and standing proud. Great job on making this a rule. Way to run away from little problems.

Pathetic, Stupid and worthless is what this has become. Just when i thought things were improving your little admins here got tired of dealing with shit and just decided to give everyone the oppertunity to cheat. Great job assholes. Hmm what else can i say other then you guys have gone from 1 of the best gaming communities to THE WORST WHEN IT COMES TO SETTING UP RULES.

I think i'm done for now. ban me if you think its necessary. though i know plenty more thoughts like mine are to come in the near future.

Good night and remember where those 2 middle fingers go.

-N3xus.


Amen!

But seriously guys, your only going to get more questions and more moaning from the new teams and ect... Why must this be gone? ITs not hard to add a few lines to your config. C'mon now. Jesus christ.
ZzZzZzZzZ Im glad its gone bring on the no fog!!!!! jk I could care less, imo teams that actually dumpusered my guys in sv_pure have some serious cheating paranoia.
Originally posted by: Impactplayer
ZzZzZzZzZ Im glad its gone bring on the no fog!!!!! jk I could care less, imo teams that actually dumpusered my guys in sv_pure have some serious cheating paranoia.


I think you have too much faint in sv_pure....especially when no fog and such are cfg hacks, not pk3.
Post edited by PhattyB at 7/20/2003 10:48:11 AM
Originally posted by: n3xUs
Originally posted by: n3xUs
Oh i get it. YOU guys take the fucking easy way out. instead of dealing with problems involving cheaters and people with questions. You take the easy way out. Great ladder you have going on!

So now, you'll have alot more clans complaining about someone using no fog and this and that. You've digged yourselves a mighty hole by making this "rule change". Running away from thr problems. This is truly pathetic. You guys are pathetic. Think about it for a second, you'll get twice as many clans bitching and moaning about those little cvar commands/cheats. After every single match.

I just hope you have something planned, something better maybe. I can't beleive it, you guys have a "0 cheat" policy but yet your oppening the doors to all those lazy cheaters that use the no fog and ect...

Well from this moment You guys get both of my middle fingers up and standing proud. Great job on making this a rule. Way to run away from little problems.

Pathetic, Stupid and worthless is what this has become. Just when i thought things were improving your little admins here got tired of dealing with shit and just decided to give everyone the oppertunity to cheat. Great job assholes. Hmm what else can i say other then you guys have gone from 1 of the best gaming communities to THE WORST WHEN IT COMES TO SETTING UP RULES.

I think i'm done for now. ban me if you think its necessary. though i know plenty more thoughts like mine are to come in the near future.

Good night and remember where those 2 middle fingers go.

-N3xus.


Amen!

But seriously guys, your only going to get more questions and more moaning from the new teams and ect... Why must this be gone? ITs not hard to add a few lines to your config. C'mon now. Jesus christ.


n3xUs
Email: not available
ICQ:
Date Joined: 7/15/2003
No active teams found for selected member.


Who the hell are you? Since you dont belong to a team on any Sh ladder what the hell does it matter to you? And if you do don't post under a smurf name I have ZERO respect for people who do that.

As long as I'm not facing cham skins in match I really don't care if code security is used or not. SV_PURE will catch the really bad stuff and what it dont I can handle no problem.
so you don't mind someone in the hunt sniping you in the allied sniper house from the sand bags in the back of the axis side? just so long as it's no fog and not cham skins, right?


When the toast is burned
And all the milk has turned
And Captian Crunch is waiving farewell
When the Big One finds you
May this song remind you
THAT THEY DON'T SERVE BREAKFAST IN HELL
just be aware, there are no fog hacks that work in pure and honesty dosent catch, so this was not really stopping much of anything.
As an admin we are in a position to have a better perspective of what is effective and try to balance it with fair play without causing a huge problem and burden.

The honesty config has a ton of versions. Most cheats and hacks dont even use any of these. With sv_pure and code_security the need for some sort of honesty config is mute. Even if there was a valid arguement for it, it causes more disputes and questions about whether this variable or that variable is suppose to be there or not. And each day the honesty config seems to have more variables then can be displayed in the console, where most players have no idea what the correct numbers are for all those.

This doesnt mean that the honesty config that comes with Code Security cant be used. CS includes a server side force honesty config already. The only difference from here on out is that teams wont be disputing if a player doesn't have all the lines that others may have. If you happen to do a dumpuser of a player who has an honesty config that proves they have cheats on then by all means send it in and they will be removed from competition. This does not change TWL's no tolerance policy. It only reduces the frivilous complaints and mass confusion that results from trying to enforce a config that at this point literally does next to nothing that CS and pure cant catch.
__________________________________________________________________
MoHAA Game Admin
CoD Game Admin
Send Email
Originally posted by: {GP} Grin Reaper
so you don't mind someone in the hunt sniping you in the allied sniper house from the sand bags in the back of the axis side? just so long as it's no fog and not cham skins, right?


Yes I mind but its not that big of an advantage, you have to be visible for them to see you (with no Fog) where with a cham skin they see you period.

There are cheats and then there are CHEATS. As long as SV_PURE catches the CHEATS I can live with the cheats it doesn't catch.

There have only been a few times that I have felt that I was on the wrong end of a cheat in spearhead and those times were in pub play with SV_PURE off. All of the teams I've played in matches on the spearhead ladders not once did I ever feel that someone on the opposing team was using a cheat. Where as in AA there was rarely a match that I played in where I wasn't sure someone was using a cheat.
Post edited by [D12C]Hobbes at 7/20/2003 1:15:29 PM
Geronimo hit it on the head... Code Security is still required , therefore you can still force the 'honesty config' on clients from the server side.
Nexus, who are you?? Besides someone without a team or a clue???
This is a good idea , not a bad one. I envision substantially fewer problems for eliminating something that was useless anyway.
Alright thanks for clearing it up Geronimo. Looking at my first reply now..... its not too nice, guess i was in the "heat of the moment". Either way....


Code Security...... What has to be turned on with that? is the cheat check enabled? or no? Just curious thats all.
Nexus , glad you see that now.... as for your first post , I think Edit-->Delete Post would be appropriate , IMO...
Post edited by DieselFuel! at 7/20/2003 2:42:17 PM
what honesty config comes with CS, and if it DOES have one that it can force on ppl, why didn't we just say we'll have CS force the honesty config from day 1?

and please enlighten me on how to go about forcing the honesty thru CS and if what the rules are on that with TWL as far as forcing it and whatnot. just to be clear.


When the toast is burned
And all the milk has turned
And Captian Crunch is waiving farewell
When the Big One finds you
May this song remind you
THAT THEY DON'T SERVE BREAKFAST IN HELL
Originally posted by: n3xUs
Alright thanks for clearing it up Geronimo. Looking at my first reply now..... its not too nice, guess i was in the "heat of the moment". Either way....


Code Security...... What has to be turned on with that? is the cheat check enabled? or no? Just curious thats all.


Here are the two lines of code that scan and activate the honesty config server-sde.

rcon g_antihack 1
rcon g_instahexen 1
or
rcon set g_antihack 1
rcon set g_instahexen 1

When you do a dumpuser what will be displayed are 1 of 3 things: 0, 1, Hacked

0= which means they are clean
1= means they enabled cheats
Hacked= means they tried to hack their .exe file to bypass anticheats or a dumpuser check.
__________________________________________________________________
MoHAA Game Admin
CoD Game Admin
Send Email
Alright. Sounds good. Thanks Ger.
I just want to know how Code Security can force the honnesty?
[

Here are the two lines of code that scan and activate the honesty config server-sde.

rcon g_antihack 1
rcon g_instahexen 1
or
rcon set g_antihack 1
rcon set g_instahexen 1

When you do a dumpuser what will be displayed are 1 of 3 things: 0, 1, Hacked

0= which means they are clean
1= means they enabled cheats
Hacked= means they tried to hack their .exe file to bypass anticheats or a dumpuser check.

There ya go ... lol
Just like forcing screenshots. Only now instead of doing a dumpuser and not seeing "hidden" values the server forces the client to display their values. (The ones pretaining to cheats)

This saves each player from having to install their own and wondering why Player A has this and Player B doesnt. This simplifys everything for everyone and still allows teams to have the ability to make sure "all is well."
lol.. if that would have been included in your first post i think n3xus wouldn't have blown a gaskit!

ty Geri.
just FYI, i believe the reason why for some reason, we didn't include this in the first place, is that i remember some ppl trying to claim that the instahexen and antihack execution caused lag (which i never noticed on our server that runs MAM and we've always had server side set some cvars).

so can i get an official "you must have instahexen and antihack set to 1" ? would be a simple 2 lines in the match config file. i think this would put at ease most everyone who would have been, or are against taking away the honesty config.


When the toast is burned
And all the milk has turned
And Captian Crunch is waiving farewell
When the Big One finds you
May this song remind you
THAT THEY DON'T SERVE BREAKFAST IN HELL
When i have done it , it only causes lag when you execute the command. So if you do it before the match/map starts , lag isn't an issue.
antihack and instahexen do different things - antihack is periodic, which means the variable will be forced periodically throughout the match...instahexen is a one time shot, done when you call it through console......i asked this before and the answer i got was instahexen is permitted, antihack is not.....has that changed?
Both are fine. Neither affect gameplay and only force settings which teams cant argue about. Players dont have to do any work about an honesty config. So long as your playing fairly the hexen and antihack wont matter to you.
thanks

26 posts recovered