Are you kidding me? I already gave you my gproxy log and you just copy paste the same text. I am telling you 1. [Thu Nov 08 13:39:42 2012] [GPROXY] starting up custom Euroloader gproxy [Thu Nov 08 13:39:43 2012] [UDPSOCKET] using broadcast target [127.0.0.1] [Thu Nov 08 13:39:43 2012] [GPROXY] List of commands: /commands in console, !commands in chat [Thu Nov 08 13:39:48 2012] >>> /commands [Thu Nov 08 13:39:56 2012] [GPROXY] GProxy++ Version 1.7.3 [Thu Nov 08 13:40:50 2012] [GPROXY] starting up custom Euroloader gproxy [Thu Nov 08 13:40:50 2012] [UDPSOCKET] using broadcast target [127.0.0.1] [Thu Nov 08 13:40:50 2012] [GPROXY] List of commands: /commands in console, !commands in chat [Thu Nov 08 13:41:02 2012] [TCPSOCKET] closed by remote host [Thu Nov 08 13:41:08 2012] [GPROXY] Error: bad registry. Try to run registry fixer [Thu Nov 08 13:41:15 2012] [GPROXY] logon bnet successful 2. windows 7 3. I did all you wrote 4. I enter w3, battlenet, I log in and he closes w3. It said path not found, then I used w3 fixer, copied to c/program files and now it says [Thu Nov 08 13:41:08 2012] [GPROXY] Error: bad registry. Try to run registry fixer. 5. I really dont know what that w3fix does but it just cretaed some log file
If you start the gproxy and the game , log in and it just closes the game and in gproxy it says Path not found or / run WC3fixer. Download Wc3Fixer and puth your right path ( DONT FORGET TO REMOVE THE \Diabollo 2 FROM THE PATH !!!) If that also didnt help than put your wc3 into Program(e) Files folder almost always --> C:\Program Files\ and dont forget to rename your wc3 folder to "Warcraft III". If that didnt help than you have to reinstall your Warcraft III.
I did all of this. When I run that w3 fixer I just get some txt log. As I sad log says there is a problem with registry.
[Thu Nov 08 13:39:56 2012] [GPROXY] GProxy++ Version 1.7.3 [Thu Nov 08 13:40:50 2012] [GPROXY] starting up custom Euroloader gproxy [Thu Nov 08 13:40:50 2012] [UDPSOCKET] using broadcast target [127.0.0.1] [Thu Nov 08 13:40:50 2012] [GPROXY] List of commands: /commands in console, !commands in chat [Thu Nov 08 13:41:02 2012] [TCPSOCKET] closed by remote host [Thu Nov 08 13:41:08 2012] [GPROXY] Error: bad registry. Try to run registry fixer [Thu Nov 08 13:41:15 2012] [GPROXY] logon bnet successful
my w3 folder is in c/program files. New version of grpoxy instaled as you can see. Whats going on?
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
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.
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?
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.
WiKi
How To
Rules
Ban
Unban
LA Staff
Maps
Streams
Show Posts
