dota replay manager

[liz_mi_fuz]

Ok so I downloaded drm and I tried to use enemy click but I cant. So I started looking at the log.txt and is there any other program that can detect clicks on heroes which are not allowed? I see when someone clicks on a hero but it only says [id='E02U', object=0x0000D9ED00006531] so I dont know what hero it clicked on.

thanks in advance

[kingW3]

http://176.9.26.177/forum/index.php/topic,42880.0.html

[DatFace]

Why you need that program anyway!

[shpura]

Best program for this is dw3gparser, tutorial can be found in our tools section. About in-game fogclick shower, it's for staff only, and you could be permabaned for using it.

[liz_mi_fuz]

First of all, I didnt use it yet. I just wnat to detect mh and post mh ban requests. I saw some people putting 16: Change selection (unit,are,building ) so I started googling and found about it. Thats all.

One more question why is fog clicking checking banable?

Tnx for that program shpura is it legal to use that?

[shpura]

No, parser is completely legal and I advise you to learn how to use it. In-game fogclick shower is illegal.

[liz_mi_fuz]

Its a misunderstanding. I am not talking about a IN GAME fogclick shower. I am talking about a program which uses DOTA REPLAY MANAGER log to detect fog clicking. Do you understand now? Sry if I was unclear.

[shpura]

You misunderstood me. The program dw3gparser is legal and the thing you want. I was just saying in-game tool is illegal because you mentioned it.

[kingW3]

Actually he didn't mention it ...

[dzokavac]

shpura is on some drugs

[div.ide]

Its a misunderstanding. I am not talking about a IN GAME fogclick shower. I am talking about a program which uses DOTA REPLAY MANAGER log to detect fog clicking. Do you understand now? Sry if I was unclear.

He understood you completely. Replay checking is not bannable.

I don't know why people bash on DRM + EC combo, dw3gparser is bit old and had some issues with setting it up. I personally like DRM and got usd to it.

Few tips to get this to work:
1. in DRM settings (replay tab) -  turn on generation of action logs to log.txt file (seems like you did it already though)

2. Enemy click checker must be in the same directory as DRM, otherwise it won't detect log file

3. Make sure your Enemy Click is up to date

4. More detailed info about commands is in ec_readme (I guess you saw that), but usually command you want to use goes like
c 5:00
Replacing c with ca will also check for allied hero selections (useful in case of share abuse - helps finding out who messed with your hero); 5:00 is a timestamp (duh), you might wish to adjust it depending if you casually check for pre-creepspawn selections or want to actually carefuly analyze whole game. If you're suspecting certain player, you can use command like
c 7 60:00
The number inbetween is player's slot  number (others will not be extracted).

5. Posting raw action code from parser is not necessary, in your report it will suffice if you put timestamp (replay time) and who clicked who, which can be written down as it stands in EC

6. If you insist on finding that action code in log anyway...

Spoiler for Hiden:

1) click Load actions
2) Select player
3) Type part of clicked hero's name (not player's nickname!)
4) Proceed clicking find next until right click is found
5) There goes your result

7. DRM sometimes hangs up and goesn't update log files at all - you'll need to restart it. Also it's better to save replays in your replay folder (you might create subfolder for this purpose) as opening straight from browser lso tends to cause log generatino to malfunction.

[kingW3]

I personally like the combination of DRM and EC but dw3gparser is most acurate i had few bug clicks with EC and a lot with DRM

[shpura]

shpura is on some drugs

Still mad?

[liz_mi_fuz]

Its a misunderstanding. I am not talking about a IN GAME fogclick shower. I am talking about a program which uses DOTA REPLAY MANAGER log to detect fog clicking. Do you understand now? Sry if I was unclear.

He understood you completely. Replay checking is not bannable.

I don't know why people bash on DRM + EC combo, dw3gparser is bit old and had some issues with setting it up. I personally like DRM and got usd to it.

Few tips to get this to work:
1. in DRM settings (replay tab) -  turn on generation of action logs to log.txt file (seems like you did it already though)

2. Enemy click checker must be in the same directory as DRM, otherwise it won't detect log file

3. Make sure your Enemy Click is up to date

4. More detailed info about commands is in ec_readme (I guess you saw that), but usually command you want to use goes like
c 5:00
Replacing c with ca will also check for allied hero selections (useful in case of share abuse - helps finding out who messed with your hero); 5:00 is a timestamp (duh), you might wish to adjust it depending if you casually check for pre-creepspawn selections or want to actually carefuly analyze whole game. If you're suspecting certain player, you can use command like
c 7 60:00
The number inbetween is player's slot  number (others will not be extracted).

5. Posting raw action code from parser is not necessary, in your report it will suffice if you put timestamp (replay time) and who clicked who, which can be written down as it stands in EC

6. If you insist on finding that action code in log anyway...

Spoiler for Hiden:

1) click Load actions
2) Select player
3) Type part of clicked hero's name (not player's nickname!)
4) Proceed clicking find next until right click is found
5) There goes your result

7. DRM sometimes hangs up and goesn't update log files at all - you'll need to restart it. Also it's better to save replays in your replay folder (you might create subfolder for this purpose) as opening straight from browser lso tends to cause log generatino to malfunction.

thanks man, but I downloaded 1.7.4 and it crashes. And version 1.7.0 works but doesnt show nothing. Not even teams

[div.ide]

Lookup DRM 2.10.