
Originally Posted by
DoctorGromit
Hi there! First off, kudos to an amazing bot. I'm amazed at the effort put into project and how well it works. I do have a few problems I want to ask about though.
I am using PerX, and the latest version of DanKsole and Nico's 1 hit/god dll. My bot works fine if I run Decisive Battle (I run on a 64bit version), but if I try any other map it doesn't work. Take for example, Red Ruins. The bot does everything fine until it gets the the map with the boss in it. It transforms and rushes forward and pretty much every time it gets stuck along a wall or obstacle. Then it spams conviction while still being stuck, and it never ends up getting to the boss.
I have a similar problem when running White Tyrant. The bot skips right to the first cutscene with the kobolds eating the meat, and spams conviction and kills all of them, but it never gets close enough to trigger the cutscene for the bear itself to come out.
Finally, I have tried it on Lab and it skips to all Doppleganger rooms just fine. However, it a) gets stuck on the wall and spams conviction or b) runs to the centre of the room, spams conviction, but no projectiles come out and rarely do any of the dopplegangers die.
I am sorry if this issue has been resolved already, but I have used the Search function and read the Readme and nothing pertains to my problem. Once again though, thanks for this awesome bot!
-edit- Just a few clarification points if it helps- I run Vindictus with console mode, and like your guide said on the front, I copied all the commands from the readme and pasted them into the console. I am running the game on windowed mode, but on full resolution so it takes up the entire screen.
The only thing that i could come to conclusion about without actually seeing the bot in action is:
1. Possibly the download you obtained was corrupted, redownloading it could fix that.
2. You may have a bad sector on your drive where some of the maps are residing, which could cause issues.
3. You may have some bad ram that's not bad enough to keep your comp from booting, but bad enough to not be allocated at times.
4. There could be too much or too little of a delay in the map skip times, or boss fighting procedures.
5. Some of the other timers may not be correct.
6. It may be your resolution, try lowering it, or raising it, both ways, and see if either helps. (the more pixels on the screen, the further you have to run to get to "X" area on the map apparently.)
7. Your computer might be too slow (adjusting load timer delays, and things like that could very well fix some of these issues, if not all of them.)
Please don't think that there's something wrong with your computer if there's not. These are just the most viable solutions to your problem.

Originally Posted by
Naix
I already posted my problem but I'l do it again since it was a couple of days ago and problem isn't resolved. I keep on trying to use the bot but when ever I try to run it nothing happens. I run windows 7 32 bit, always start the bot as admin. I never touched any of the binds and I tried using pie bind, danksole, and nico's v5 god mode and 1 hit kill. I used thouse seperatly together and everything but still nothing happens. SO, my question once again is, how do I make the bot work?

1. Run perx, set perx to Vindictus.exe
2. Choose the dlls you want to load IN THE RIGHT ORDER (topmost one loads first.)
3. Run vindictus.
4. Close perx if you chose to manually inject,
5. Log in
6. go to docks
7. Alt tab out of vindictus
8. double click on sinbot program to run it
9. choose map, and other settings.
10. make sure the right operating environment is chosen.
11. hit START
12 Go back into vindictus fast (you've only got 'x' amount of time.
13. Make sure your cursor is hidden in vindictus and press "INSERT" to start the bot.
14. Leave it alone, and let it do it's thing.
This really isn't that hard, if you're having problems with a certain part then you should tell me what steps you've done and WHERE it gives you an error...
sheesh.
Everyone wants help, and no one wants to be descriptive of their problem.
telling us that "it not work4me" doesn't tell us WHY.
We as the programmers can tell you why if you give us enough information.
But we require that information to be able to tell you.