Official V3n0M Thread

i did erything you guys said but when i run venomlite it shows an error message that says
V3n0MProxy has encountered a problem and needs to close.We are sorry for the inconvenience
then it gives me options to send error or not .
i just double click venomproxy and it pops up
what do i do x.X

I had a bit of trouble with making it work, but here is what I put (and I got it to work btw xD). This is an example of the Venus server.

Server5=Venus
Ip5=127.0.0.1 <--- this is the same as 1.
Port5=9958
ServerName5=Venus
HintWord5=
Pic5=servericon18

localloginport=9958
localmapport=5816
remoteloginport=9958
remoteloginip=216.93.164.137 <--- this is the original server ip
proxyip=127.0.0.1 <---- 1
consoleout=yes
logfile=coproxy.log
filter=0x3ee


I don't know if 127.0.0.1 will work for everybody, but I looked the i.p. up on google and this page tells you about it [Only registered and activated users can see links. Click Here To Register...]


EDIT: Why does it say to change from 127.0.0.1 in all the guides on this thread? It works for me =/

Ok Here is an effort from me to hopefully help the community ;)

If you just downloaded V3n0M-5000-Build1 follow these steps

First DO NOT run V3n0M without first installing all of these on your computer
as Queen-Of-Evil has said on page 1

GO TO PAGE 1 FOR THE LINKS

.NET Framework version 2.0 Redistributable package (x86)
.NET Framework version 3.0 Redistributable package
Microsoft Visual Basic 6.0 Common Controls
Microsoft Visual J# Version 2.0 Redistributable package
Visual J# .NET Version 1.1 Redistributable package
Microsoft Visual J# 2.0 Redistributable package 2nd Edition

After installing V3n0M into the main CO folder

1st open up your main CO folder find and open v3n0m01.ini

It should look like this...

localloginport=9958
localmapport=5816
remoteloginport=9958
remoteloginip=216.93.174.65 <----Change this line to your game servers IP Address
proxyip=127.0.0.1 <----Change this line to 127.0.2.1
consoleout=yes
logfile=coproxy.log
filter=0x3ee

Save and exit v3n0m01.ini

There is no need to open and change Server.dat from V3n0M-5000-Build1 they are already all changed to 127.0.2.1 unless your trouble shooting connections. Example...

**EDIT** How to connect if 127.0.2.1 Doesnt work for you, by me, The Most infamous, Queen-Of-Evil

Ok yourve installed the V3n0M and downloaded all the .Net and J# Files mentioned in the readme, but you just cant connect for some reason, Well First of all try changing 127.0.2.1 to 198.162.2.1 , and if that doesnt work, try using 10.10.10.10 as a second shot.... and finally, always seems to work in the end, Use YOUR I.P. (* Yours not your Routers, the one your ISP assigns you, Google for how to find out your i.p. if you dont know it. *) D Hope that helps peaple.


2nd Open version.dat should look like this...

4356 <----change to 5000 if you want to auto update or 9999 if you want to
manually patch from now on

Failure to change version.dat might cause auto update to download and overwrite some files.

3rd make a shortcut for V3n0M-Lite.exe on desktop

You must Run V3n0M-Lite.exe before running Conquer!!!

After both programs are running and you have logged in your character

Then type in the desired commands

Quote:

Originally Posted by timerman I tried it how you said Proxy i.p = 127.0.2.1 remote login = server i.p changed my server i.p to 127.0.2.1 Still doesnt work =/

Not what I said at all.
I said:

proxyip=127.0.0.1
NOT 127.0.2.1!!
That one is for the server.dat files.

Quote:

Originally Posted by limeyum I had a bit of trouble with making it work, but here is what I put (and I got it to work btw xD). This is an example of the Venus server. Server5=Venus Ip5=127.0.0.1 <--- this is the same as 1. Port5=9958 ServerName5=Venus HintWord5= Pic5=servericon18 localloginport=9958 localmapport=5816 remoteloginport=9958 remoteloginip=216.93.164.137 <--- this is the original server ip proxyip=127.0.0.1 <---- 1 consoleout=yes logfile=coproxy.log filter=0x3ee I don't know if 127.0.0.1 will work for everybody, but I looked the i.p. up on google and this page tells you about it [Only registered and activated users can see links. Click Here To Register...] EDIT: Why does it say to change from 127.0.0.1 in all the guides on this thread? It works for me =/

Umm...
Maybe you are just high?? I think that'd be what Queen would say.
But I dunno, maybe that does work. But I would still suggest that everyone uses the 127.0.2.1 in there server.dat file.
It's the more sensible thing to do.
If 127.0.2.1 is not working for you, especially if you are on dial up, then go to the first page and go to where it is orange, and there is troubleshooting for connecting with different ip's.

But hey, if it's working for you, then who knows?

Quote:

Originally Posted by tgsjlimt Ok Here is an effort from me to hopefully help the community ;) If you just downloaded V3n0M-5000-Build1 follow these steps First DO NOT run V3n0M without first installing all of these on your computer as Queen-Of-Evil has said on page 1 GO TO PAGE 1 FOR THE LINKS .NET Framework version 2.0 Redistributable package (x86) .NET Framework version 3.0 Redistributable package Microsoft Visual Basic 6.0 Common Controls Microsoft Visual J# Version 2.0 Redistributable package Visual J# .NET Version 1.1 Redistributable package Microsoft Visual J# 2.0 Redistributable package 2nd Edition After installing V3n0M into the main CO folder 1st open up your main CO folder find and open v3n0m01.ini It should look like this... localloginport=9958 localmapport=5816 remoteloginport=9958 remoteloginip=216.93.174.65 <----Change this line to your servers IP Address proxyip=127.0.0.1 <----Change this line to 127.0.2.1 consoleout=yes logfile=coproxy.log filter=0x3ee Save and exit v3n0m01.ini There is no need to open and change Server.dat from V3n0M-5000-Build1 they are already all changed to 127.0.2.1 unless your trouble shooting connections. Example... **EDIT** How to connect if 127.0.2.1 Doesnt work for you, by me, The Most infamous, Queen-Of-Evil Ok yourve installed the V3n0M and downloaded all the .Net and J# Files mentioned in the readme, but you just cant connect for some reason, Well First of all try changing 127.0.2.1 to 198.162.2.1 , and if that doesnt work, try using 10.10.10.10 as a second shot.... and finally, always seems to work in the end, Use YOUR I.P. (* Yours not your Routers, the one your ISP assigns you, Google for how to find out your i.p. if you dont know it. *) D Hope that helps peaple. 2nd Open version.dat should look like this... 4356 <----change to 5000 if you want to auto update or 9999 if you want to manually patch from now on Failure to change version.dat will cause auto update to download and overwrite some files. 3rd make a shortcut for V3n0M-Lite.exe on desktop You must Run V3n0M-Lite.exe before running Conquer!!! After both programs are running and you have logged in your character Then type in the desired commands

Um, what? Don't go and change the ve3n0m.ini proxyip. I have mine set to 127.0.0.1 and it works just fine. Don't change it. And no, failure to change version.dat will not result in auto patch because you are using *M*'s conquer.exe anyway, it comes with V3n0m, and skips the auto patch automatically. Which *M* did a FANTASTIC job on, and allows you to jump over anything. (Except guild gate, kudos to Queen for that.)

Quote:

Originally Posted by IfIWasAmish Um, what? Don't go and change the ve3n0m.ini proxyip. I have mine set to 127.0.0.1 and it works just fine. Don't change it. And no, failure to change version.dat will not result in auto patch because you are using *M*'s conquer.exe anyway, it comes with V3n0m, and skips the auto patch automatically. Which *M* did a FANTASTIC job on, and allows you to jump over anything. (Except guild gate, kudos to Queen for that.)

Well I'm speaking from experience IT CAN AUTO PATCH! and I was using the cracked Conquer.exe when it did. Maybe you didnt have this problem, Hopefully others don't either but if they do they will know how to fix it.

And as far as changing V3n0m.ini to 127.0.2.1 It obviously works either way
because I'm having zero problems with this setting.

So instead of telling people to only do it the way you tell them because you personally havn't had other problems is a bit wrong.

I'm sure your connections work fine but guess what so do mine and in the end thats all that matters ;)

Quote:

Originally Posted by tgsjlimt Well I'm speaking from experience IT CAN AUTO PATCH! and I was using the cracked Conquer.exe when it did. Maybe you didnt have this problem, Hopefully others don't either but if they do they will know how to fix it. And as far as changing V3n0m.ini to 127.0.2.1 It obviously works either way because I'm having zero problems with this setting. So instead of telling people to only do it the way you tell them because you personally havn't had other problems is a bit wrong. I'm sure your connections work fine but guess what so do mine and in the end thats all that matters ;)

I used *M*'s conquer.exe also and did not encounter an autopatch =/. Are you sure you were using Ms exe when you opened conquer?

Quote:

Originally Posted by tgsjlimt Well I'm speaking from experience IT CAN AUTO PATCH! and I was using the cracked Conquer.exe when it did. Maybe you didnt have this problem, Hopefully others don't either but if they do they will know how to fix it. And as far as changing V3n0m.ini to 127.0.2.1 It obviously works either way because I'm having zero problems with this setting. So instead of telling people to only do it the way you tell them because you personally havn't had other problems is a bit wrong. I'm sure your connections work fine but guess what so do mine and in the end thats all that matters ;)

Hahahaha, I am telling people to do it the way the CREATOR told them to do it. And no, *M*'s conquer.exe WILL NOT AT ANY TIME GO THROUGH AUTOPATCH. You simply just opened the wrong one. I am sure that Queen knows a hell of a lot more than you, and I am just telling people what she has clearly stated. Don't go and change IP's in hopes that it works.

Thanks Queenie ur doin well in every new update =)
but erm .. can any one upload the new build into another space share website cause rapidshare sux it always say i should wait 145 min's then after waiting it says your ip is already downloading ... :mad:
thanks all for co-op :D

Yep, uploading to megaupload.com for you right now...
Will have it posted in a few mins.

Here you are, I uploaded it to megaupload.com for you. :D
[Only registered and activated users can see links. Click Here To Register...]

Ps: Queen, I dunno if it is against any of your rules to do this, so just tell me if it is, and I'll remove it. I didn't change any files.

Quote:

Originally Posted by IfIWasAmish Hahahaha, I am telling people to do it the way the CREATOR told them to do it. And no, *M*'s conquer.exe WILL NOT AT ANY TIME GO THROUGH AUTOPATCH. You simply just opened the wrong one. I am sure that Queen knows a hell of a lot more than you, and I am just telling people what she has clearly stated. Don't go and change IP's in hopes that it works.

well 127.0.0.1 doesnt work for me but 127.0.2.1 does so GTFO

and since the last patch whenever i run CO i'm autopatching with venom running . .it's not a huge problem but i'll try chaning the version.dat

Quote:

Originally Posted by Dan_J well 127.0.0.1 doesnt work for me but 127.0.2.1 does so GTFO and since the last patch whenever i run CO i'm autopatching with venom running . .it's not a huge problem but i'll try chaning the version.dat

Lol

Um, it isn't V3n0m that stops the autopatch, its the conquer.exe.
And I think you could delete a few files to stop the autopatch all together if you wanted to just do it that way.

Quote:

Originally Posted by tgsjlimt NET Framework version 2.0 Redistributable package (x86) .NET Framework version 3.0 Redistributable package Microsoft Visual Basic 6.0 Common Controls Microsoft Visual J# Version 2.0 Redistributable package Visual J# .NET Version 1.1 Redistributable package Microsoft Visual J# 2.0 Redistributable package 2nd Edition

Windows Vista already has All those programs by default except like one of them, I forget which one it was.