Upcoming Detection List

Anything that doesn't fit the other categories
adrian_007
Senior Member
Posts: 126
Joined: 06 Jan 2008, 13:00

Upcoming Detection List

Post by adrian_007 » 30 Mar 2008, 19:23

ok, as i see no activity on branches, i suppose no suggestions are left on what is done.

so here it is, brand new list format. it's "initial release" so post eventual improvements in this thread.

Code: Select all

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<Profiles>
	<ClientProfilesV3>
		<DetectionProfile>
			<DetectionEntry ProfileID="1">
				<Name>DC++</Name>
				<Cheat></Cheat>
				<Comment>User Client</Comment>
				<RawToSend>0</RawToSend>
				<ClientFlag>0</ClientFlag>
				<IsEnabled>1</IsEnabled>
				<InfFields>
					<InfField Field="TA" Pattern="^<\+\+ V:%[VE],(M:[AP5]{1}),H:%[HN]/%[HR]/%[HO],S:%[SL]>$"/>
					<InfField Field="LO" Pattern="^EXTENDEDPROTOCOLABCABCABCABCABCABC$"/>
					<InfField Field="PK" Pattern="^DCPLUSPLUS%[VE]ABCABC$"/>
				</InfFields>
			</DetectionEntry>
		</DetectionProfile>
	</ClientProfilesV3>
	<Params/>
	<ProfileInfo>
		<DetectionProfile>
			<Version>N/A</Version>
			<Message>N/A</Message>
			<URL>N/A</URL>
		</DetectionProfile>
	</ProfileInfo>
</Profiles>

Toast

Re: Upcoming Detection List

Post by Toast » 30 Mar 2008, 20:21

kk when the time is ready for some testing and client list making just tell me and ill start making the lists

question CID Detection is that a possibly for the new CMD ?

i guess u checked my suggestion on XML file

adrian_007
Senior Member
Posts: 126
Joined: 06 Jan 2008, 13:00

Re: Upcoming Detection List

Post by adrian_007 » 30 Mar 2008, 21:29

i'm not quite sure if you get this right, if you're asking if you can detect CID.

you can detect, CID, SID, and any other INF field. all params are from infmap so it's like UserCommand, where in UC param is in format %[userFL], here it's just %[FL].
so to detect CID you have to add inffield to profile

Code: Select all

<InfField Field="ID" Pattern="^AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA$"/>
@todo add formatted params, like %[VE2] and so on.

note, there are no params in params list (check xml struct)

Toast

Re: Upcoming Detection List

Post by Toast » 31 Mar 2008, 06:08

Ok so i can make these parameters myself in the file then ?

like in the old lists

adrian_007
Senior Member
Posts: 126
Joined: 06 Jan 2008, 13:00

Re: Upcoming Detection List

Post by adrian_007 » 31 Mar 2008, 06:53

well yes, but i suggest to use regex only where you really need it in params :P

Toast

Re: Upcoming Detection List

Post by Toast » 31 Mar 2008, 07:07

kk mind explaining why ?

i noticed a problem in the current CMD that made it detect it wrong and that was (M:[AP5]{1}) don't really know why it misses on that part but it does

adrian_007
Senior Member
Posts: 126
Joined: 06 Jan 2008, 13:00

Re: Upcoming Detection List

Post by adrian_007 » 31 Mar 2008, 13:41

dunno what's wrong... but hmm.. how you checked it btw?
why minimize regex usage? to speedup match. all params are resolved before match, so there is no reason for using more and more patterns.

Toast

Re: Upcoming Detection List

Post by Toast » 31 Mar 2008, 14:19

in the current CMD used in all clients has this problem i checked against tag and then against regexp and in those cases it matches but when entered into client it mismatched (in this case i used apex)

Toast

Re: Upcoming Detection List

Post by Toast » 24 May 2008, 14:01

Any Progress ?

Still waiting to begin testing here

adrian_007
Senior Member
Posts: 126
Joined: 06 Jan 2008, 13:00

Re: Upcoming Detection List

Post by adrian_007 » 24 May 2008, 14:29

but what do you want?
in this matter imo, there is nothing else to do.

if crise include it in upcoming release, you will be able to use it (as i'm working on rsx++, still, i think he is going to have release sooner than me)

Locked