[schmurgel1983]

sry, for offtopic but orpheu sig scan is horrible for me, the tut's are not cleary for me, no good samples/explane. so i stop working with orpheu.

nice work bugsy

Originally Posted by dark_style I have an idea for you. What about to add the reason when mp_autokick is set to 1 and the player get kicked by it?

is this not the "drop" message?

[Bugsy]

Originally Posted by schmurgel1983 sry, for offtopic but orpheu sig scan is horrible for me, the tut's are not cleary for me, no good samples/explane. so i stop working with orpheu.

I am working on a program that will create signatures, the user only needs to paste info from IDA. I think many others, including myself, are hesitant to use orpheu since signature making is intimidating.

[Bugsy]

I am thinking about changing the plugin functionality a bit:

1) Notify of all types of disconnect reason, not only allowing timed out or dropped. Should I keep a cvar to allow users to select only particular types or only do all?

2) Get rid of console notify option. I haven't played CS in a long while but I believe all users get a console message when a user disconnects, the only advantage to the console notify of the plugin is it is formatted nicely.

Comments anyone?

[schmurgel1983]

Originally Posted by Bugsy I am working on a program that will create signatures, the user only needs to paste info from IDA. I think many others, including myself, are hesitant to use orpheu since signature making is intimidating.

sounds good.

[nikhilgupta345]

Originally Posted by Bugsy I am thinking about changing the plugin functionality a bit: 1) Notify of all types of disconnect reason, not only allowing timed out or dropped. Should I keep a cvar to allow users to select only particular types or only do all? 2) Get rid of console notify option. I haven't played CS in a long while but I believe all users get a console message when a user disconnects, the only advantage to the console notify of the plugin is it is formatted nicely. Comments anyone?

For #1, a cvar would make it more customizable, but I don't know why somebody would only want certain types of disconnects are displayed.

For #2, If this plugin blocks the other notification in console by CS itself, then I say keep the console notify of this. If not, I don't see a point of having 2 different notifications for why somebody dropped out.

[Bugsy]

New release posted, see change log for changes.

Edit: Posted minor revision v0.4a, no functional changes just cleaned up the code a little.

[Stressful]

Hey , I have this error in console , How do I fix it ?

	Parsing functions started.
		Parsing file "SV_DropClient" started
				Argument type "int" validated
				Argument type "int" validated
				Argument type "char *" validated
				Searching for signature "[0x55][0x8b][*][0x81][*](...)" ... NOT FOUND
		Parsing file "SV_DropClient" ended
	Parsing function

[Arkshine]

Edit orpheu/functions/SV_DropClient file and replace the signature with :

[0x55,0x8B,"*",0x81,"*","*","*","*","*",0x8B,0x4D,"*",0x53,0x56,0x8D,0x45,"*",0x57,0x50,0x51,0x8D,0x95]

@Bugsy: you don't need to have such length. Once the signature is unique, meaning one reference, like explained in the tutorial, it's enough. This sig should work on the hlbeta too.

[Bugsy]

I thought more bytes would result in it being more unique, which I didn't realize could prevent it from working (Is this detail covered in the tut?). I will update though.

[Arkshine]

Yes, technically, but you have to be aware people use the hlbeta too, too much bytes and you might need to have 2 different signatures because some part could use different opcodes. But, like said in the tuto, once you see one reference it's unique, you don't need to add extra bytes because you would have more chance the sig won't match at the end.