Greetings.

Would it be possible to write a cog that somehow prevents a player (in a SP game) from:
1) cheating?
2) hacking?

Either not allowing him to continue or somehow proving the player cheated would be great.

Is this possible at all?

Thanks.

Why would you WANT to?

So they dont cheat on his SP level.....

------------------
"Let my life cry Holy, Holy. Let my life scream Holy, Holy. I do believe that Your the only Way so let my life cry Holy..."

The Bible is the only religious book to actually state that it is the truth and the only way. Thats why I'm a Christian.

_-=MaTRiX=-_

For cheats/hacks like GodMode, infinite ammo, all weapons, all force powers, etc. it would be fairly easy. Just run a pulse that checks the player flags for the invulnerable flag, and in that same pulse checks for force/weapon bins that the player should not have. Checking against infinite ammo would be harder, I can't think of an easy way at the moment. You could guard against flying the same way you do against god mode; check for the flag.

And if any of the checks prove positive, you could teleport the player to an isolated sector, or just DestroyThing(player); and crash the game.

[This message has been edited by Aglar (edited July 10, 2001).]

You can't keep him from hacking the game though... cheating would probably work.

-Raze

All the stuff I said helps against hacking. The thing is, if they can make a hack, they can just modify the cheat detector cog to..not..detect cheats.

..... there's always a way around, isnt there?

Hackers and cheaters just suck if they cant play and beat it on their own

------------------
"Let my life cry Holy, Holy. Let my life scream Holy, Holy. I do believe that Your the only Way so let my life cry Holy..."

The Bible is the only religious book to actually state that it is the truth and the only way. Thats why I'm a Christian.

_-=MaTRiX=-_

It'd help against cheating, not hacking =P (at least if it's half a decent hacker who knows where to look).

-Raze

I agree with aglar
that'd be the best solution

[edit]also, you might be able somehow to write another cog that would detect if the anti-cheat cog is intact, that'd stop all but the most skilled/determined hackers[/edit]

------------------
*eats pie*

[This message has been edited by Midget Basher (edited July 11, 2001).]

Midget - The only way to do that would be easily spoofed.

Lord - It would still keep all but the hackers that actually know how to cog from cheating. The majority of hackers just download cogs, they don't write them. And, they don't visit this forum.

[This message has been edited by Aglar (edited July 11, 2001).]

But now that you've revealed all of this to us... (lol)

Something you could do...
in all the powerup cogs, ie: pow_strifle.cog, you could use a flagging system.

In the items.dat, you could add, say.. 10 new bin values.

in order:
str_flag, det_flag, bow_flag, rep_flag, rail_flag, seq_flag, conc_flag, sab_flag, sld_flag, hp_flag.

In the pow_strifle, add SetBin(player, str_flag, 1);

in pow_thermal & pow_single_thermal, you'd add SetBin(player, det_flag, 1);

See what I'm getting at here? In force_well.cog, have 10 variables, named similarly, to keep track of the last value of the bin.. and if the bin increases, check and see if the flag is tripped.. if it is, SetInv(player, (whatever bin), 0); If not, you know the player magically got a weapon/health/shields w/o picking it up.. Ie: red5, bactame.

That's two commands down..what else? Check the player's invulnerbility flags for jediwannabe, in the same pulse.

Checking for eriamjh might be a bit tricky.. you'd have to check the physics flags of the player.

There's always a way of doing something... usually there's a way of countering it, however.

aglar, I was just guessing

I would suggest for all weapons/force powers/etc. you make a new bin, and use that for the ammo/force/etc. that would make it so that you don't get anything for red5, wamprat, etc.

------------------
*eats pie*