SinBotv2.2 (5 Map Pack)

Originally Posted by nick2412

Really O.o.. that's how I set it up to work in Dank's source. Working pretty good so far. Perhaps in the future I might a write pixel searching script, but I rather not fix something that is not broken.

Your technique clearly is way more advanced than what I use on dank's!

I'll give you a snippet of my code, so you can see what's going on.

Code:

Func Error()
	ToolTip("SinBotv2.3 is now taking steps to remove errors. Waiting for all error messages to appear", 50, 50)
	Sleep(500)
	Send("{ALT DOWN}")
	MouseClick("left", $CloseBattleScreenX, $CloseBattleScreenY, 1)
	Sleep(500)
	Send("{ALT UP}")
	Sleep(500)
	Do
		ToolTip("There are " & 180-$ErrorCountdown & " seconds remaining until manual launch of boat.", 50, 50)
		$GameUIErrorPixel=PixelGetColor($GameUIErrorPixelX,$GameUIErrorPixelY)
		Sleep(1000)
		$ErrorCountdown=$ErrorCountdown+1
	Until $GameUIErrorPixel=0 OR $ErrorCountdown>180

Originally Posted by Zaiakunokami

I'll give you a snippet of my code, so you can see what's going on.

Code:

Func Error()
	ToolTip("SinBotv2.3 is now taking steps to remove errors. Waiting for all error messages to appear", 50, 50)
	Sleep(500)
	Send("{ALT DOWN}")
	MouseClick("left", $CloseBattleScreenX, $CloseBattleScreenY, 1)
	Sleep(500)
	Send("{ALT UP}")
	Sleep(500)
	Do
		ToolTip("There are " & 180-$ErrorCountdown & " seconds remaining until manual launch of boat.", 50, 50)
		$GameUIErrorPixel=PixelGetColor($GameUIErrorPixelX,$GameUIErrorPixelY)
		Sleep(1000)
		$ErrorCountdown=$ErrorCountdown+1
	Until $GameUIErrorPixel=0 OR $ErrorCountdown>180

Interesting.. looks way too complicated for me though. In order for me to implement such scripts in to dank's I would also need to define the variables for

CloseBattleScreenX
CloseBattleScreenY
GameUIErrorPixelX
GameUIErrorPixelY
ErrorCountdown

Too rediculous, maybe that's why I am not scripting a bot from scratch

I just improve or customize existing work to work better for me.

Originally Posted by nick2412

Interesting.. looks way too complicated for me though. In order for me to implement such scripts in to dank's I would also need to define the variables for

CloseBattleScreenX
CloseBattleScreenY
GameUIErrorPixelX
GameUIErrorPixelY
ErrorCountdown

Too rediculous, maybe that's why I am not scripting a bot from scratch

I just improve or customize existing work to work better for me.

You think that's bad...
Here's my variable declaration area

Code:

; Declare Variables
dim $AP, $APTimes, $SmartAP, $BCCheck, $BCCheckTimer, $BCPixelCheck1, $BCPixelCheck1X, $BCPixelCheck2, $BCPixelCheck2X, $BCPixelCheck3, $BCPixelCheck3X
dim $BCPixelCheckY, $BetweenMapDelay, $BlackHammerWaitTime, $BloodLordWaitTime, $Bombs, $BQButton1X, $BQButton1Y, $BQButton2X, $BQButton2Y, $CenterX, $CenterY, $CloseBattleScreenX
dim $CloseBattleScreenY, $CloseHardModeX, $CloseHardModeY, $CreateParty1X, $CreateParty1Y, $CreateParty2X, $CreateParty2Y, $CurrentDir, $CurrentMap, $ErrorCheck, $ErrorCountdown, $Exit, $EzrochWaitTime
dim $FirstMapDelay, $GameUIErrorPixelX, $GameUIErrorPixelY, $GameUIErrorPixel, $GiantSpiderWaitTime, $GiantHeight, $GnollChieftainWaitTime, $God, $Grab, $HeightDelay, $IniFile, $KlausWaitTime, $LaghodessaWaitTime, $LaunchButtonDelay
dim $LaunchX, $LaunchY, $LeavePartyConfirmX, $LeavePartyConfirmY, $LeavePartyX, $LeavePartyY, $MapListScrollDownY, $MapListScrollEndY, $MapListScrollStartY, $MapListScrollUpY, $MapListScrollX
dim $MapSelectListX, $MapSelectListY, $Mine, $MiningDelay, $MiningRepeat, $NormalHeight, $OneHitKill, $Paladin, $Paladin2, $PaladinSkill, $Pause, $Paused, $PixelCheck, $PixelCheckBoatX, $PixelCheckBoatY
dim $PolarBear20WaitTime, $PolarBear36WaitTime, $Reach, $Refill, $ReplayButtonDelay, $ReplayX, $ReplayY, $Secondary, $SewersX, $SewersY, $ShipList, $SkillBoxX, $SkillBoxY, $SkillDelay, $SkipMap, $Spears, $SpeedKey
dim $SpeedToggle, $Start, $StartPixelCheckHigh, $StartPixelCheckLow, $StartPixelCheck, $Tentacle, $TinyHeight, $WeepingQueenWaitTime, $XColumn1, $XColumn2, $XMax, $XMouseLargeLeft, $XMouseLargeRight, $XMouseNormalLeft
dim $XMouseNormalRight, $XMouseSmallLeft, $XMouseSmallRight, $XMouseSpinLeft, $XMouseSpinRight, $XTab2, $XTab3, $XTab4, $XTab5, $XTab6, $YMax, $YMouseLargeDown, $YMouseLargeUp, $YMouseNormalDown, $YMouseNormalUp
dim $YMouseSmallDown, $YMouseSmallUp, $YMouseSpinDown, $YMouseSpinUp, $YRow1, $YRow2, $YRow3, $YRow4, $YRow5, $YRow6, $OnBoatX, $OnBoatY, $HardModeX, $HardModeY, $HeroModeX, $HeroModeY, $RaidReplayX, $RaidReplayY, $RaidLeavePartyX, $RaidLeavePartyY
dim $OathX, $Oath1Y, $Oath2Y, $Oath3Y, $Oath4Y, $Oath5Y, $Oath6Y, $OathScrollX, $OathUpY, $OathDownY, $BCReload, $MiniMapPixel1X, $MiniMapPixel1Y, $MiniMapPixel2X, $MiniMapPixel2Y, $MiniMapPixelCheck1, $MiniMapPixelCheck2
dim $TownCheckX, $TownCheckY, $TownPixelCheck, $TownPixelCheckHigh, $TownPixelCheckLow, $ScreenResDetectX, $ScreenResDetectY, $RunCounter, $SkillCheckbox

Originally Posted by Zaiakunokami

You think that's bad...
Here's my variable declaration area

Code:

; Declare Variables
dim $AP, $APTimes, $SmartAP, $BCCheck, $BCCheckTimer, $BCPixelCheck1, $BCPixelCheck1X, $BCPixelCheck2, $BCPixelCheck2X, $BCPixelCheck3, $BCPixelCheck3X
dim $BCPixelCheckY, $BetweenMapDelay, $BlackHammerWaitTime, $BloodLordWaitTime, $Bombs, $BQButton1X, $BQButton1Y, $BQButton2X, $BQButton2Y, $CenterX, $CenterY, $CloseBattleScreenX
dim $CloseBattleScreenY, $CloseHardModeX, $CloseHardModeY, $CreateParty1X, $CreateParty1Y, $CreateParty2X, $CreateParty2Y, $CurrentDir, $CurrentMap, $ErrorCheck, $ErrorCountdown, $Exit, $EzrochWaitTime
dim $FirstMapDelay, $GameUIErrorPixelX, $GameUIErrorPixelY, $GameUIErrorPixel, $GiantSpiderWaitTime, $GiantHeight, $GnollChieftainWaitTime, $God, $Grab, $HeightDelay, $IniFile, $KlausWaitTime, $LaghodessaWaitTime, $LaunchButtonDelay
dim $LaunchX, $LaunchY, $LeavePartyConfirmX, $LeavePartyConfirmY, $LeavePartyX, $LeavePartyY, $MapListScrollDownY, $MapListScrollEndY, $MapListScrollStartY, $MapListScrollUpY, $MapListScrollX
dim $MapSelectListX, $MapSelectListY, $Mine, $MiningDelay, $MiningRepeat, $NormalHeight, $OneHitKill, $Paladin, $Paladin2, $PaladinSkill, $Pause, $Paused, $PixelCheck, $PixelCheckBoatX, $PixelCheckBoatY
dim $PolarBear20WaitTime, $PolarBear36WaitTime, $Reach, $Refill, $ReplayButtonDelay, $ReplayX, $ReplayY, $Secondary, $SewersX, $SewersY, $ShipList, $SkillBoxX, $SkillBoxY, $SkillDelay, $SkipMap, $Spears, $SpeedKey
dim $SpeedToggle, $Start, $StartPixelCheckHigh, $StartPixelCheckLow, $StartPixelCheck, $Tentacle, $TinyHeight, $WeepingQueenWaitTime, $XColumn1, $XColumn2, $XMax, $XMouseLargeLeft, $XMouseLargeRight, $XMouseNormalLeft
dim $XMouseNormalRight, $XMouseSmallLeft, $XMouseSmallRight, $XMouseSpinLeft, $XMouseSpinRight, $XTab2, $XTab3, $XTab4, $XTab5, $XTab6, $YMax, $YMouseLargeDown, $YMouseLargeUp, $YMouseNormalDown, $YMouseNormalUp
dim $YMouseSmallDown, $YMouseSmallUp, $YMouseSpinDown, $YMouseSpinUp, $YRow1, $YRow2, $YRow3, $YRow4, $YRow5, $YRow6, $OnBoatX, $OnBoatY, $HardModeX, $HardModeY, $HeroModeX, $HeroModeY, $RaidReplayX, $RaidReplayY, $RaidLeavePartyX, $RaidLeavePartyY
dim $OathX, $Oath1Y, $Oath2Y, $Oath3Y, $Oath4Y, $Oath5Y, $Oath6Y, $OathScrollX, $OathUpY, $OathDownY, $BCReload, $MiniMapPixel1X, $MiniMapPixel1Y, $MiniMapPixel2X, $MiniMapPixel2Y, $MiniMapPixelCheck1, $MiniMapPixelCheck2
dim $TownCheckX, $TownCheckY, $TownPixelCheck, $TownPixelCheckHigh, $TownPixelCheckLow, $ScreenResDetectX, $ScreenResDetectY, $RunCounter, $SkillCheckbox

O.O that is a lot of coordinates to find..

Originally Posted by nick2412

O.O that is a lot of coordinates to find..

Why do you think it took me so long to add resolutions? Luckily, I've now figured out a way to bypass needing co-ords for each resolution.

want to get bot, but meh, it doesn't support 1080p

Originally Posted by Pluto Kiss

want to get bot, but meh, it doesn't support 1080p

Next version (v2.3) will support all resolutions, even those I can't test on.

Update on v2.3

Currently this is what I have done for SinBotv2.3:

New Features:

Auto screen resolution detection appears to be fully working, have tested on 9 different resolutions so far with no noticed bugs.

Added a settings.ini file to incorporate compatibility with Pie Binds, so you don't need to rely on a console. (Note: I do not use Pie Binds myself, so I will not guarantee that it works fully)

Added a battles cleared counter to see how many battles you successfully cleared using the bot. Will appear at the termination of the bot in the ending message box.

Bugs Fixed:

Added another error check system to detect system response delayed or connection time out errors before the boss room starts.

Refined boat selection process to better use the command, rather than relying on running up to the board to select to the boat.

Made sure that the Hero difficulty selection actually takes, as v2.2 had issues with it clicking in the right spot, but not accepting the click.

Removed unnecessary command lines that may have been causing glitches with some people's ability to start the bot.

Removed the predefined settings for pixel colors to start the boat, and instead allowed the bot to grab the users pixel color at the initial boat launch, and then check comparative to that for future boat launches.

Added extra tooltips to help diagnose errors with the bot from start to stop.

Boss wait times have been corrected and redefined.

Maps Supported:

Perilous Ruins:
Decisive Battle - Trampled Plains

Hoarfrost Hollow:
Dethrone the White Tyrant - White Tyrant's Challenge

Ainle:
Being from the Other World - Regrets Too Late - Shadowed by Darkness

Ruins of Sanctity:
Ruins of Sanctity - Gnoll King, Ruler of the Ruins - Hidden - Nightmare at the Ruins

Hoarfrost Depths:
Yeti King - Madness

Hilder Forest Ruins:
Fight That Must Be Won - Shady Forest

Fomorian Base:
Contact - Cadet's Challenge - Fruitful (Mining Bot) - Buried Sorrow - Rescue - Last Fragment

Sewers:
Taking Initiative - Strong Drink

Resenlian's Labyrinth (Will run 3 times and stop)

Known Issues:

Still occasionally has an issue with too much lag between starting the boat and the first map, working on a color checking systen to identify when the "The boat is launching" message is on the screen, and to only start first map timer after it goes away.

Cutscene skips have issues with some slower computers, as they can't handle the gigantic change height commands. There is a timer in the .ini that you can increase if you have this problem.

My pixel check to automatically detect whether you have the "Trained Skills Only" box ticked doesn't seem to work 100%, so make sure you have it ticked anyway.

The mining bot seems to function optimally at 1680x1050 with my custom bind settings (included), and usually has some difficulties at other resolutions or with different settings. This is due to the amount of movement commands and mouse movements that are required to make it get the mine bombs to the target ore veins. I have no plans to fix this currently, as the sheer amount of work it took to make it work at one resolution was enough that I never want to see that map again.

Ruins of Sanctity bot has issues running the longer boss map without getting stuck. I've done the best I can to make sure it gets to the boss room, but it's rather difficult with all the angles and walls. And again, this will work optimally at 1680x1050. Still working on tweaking it, but it seems quite hard to do at the moment.

Future Updates:

Many of these maps are still in a testing phase, and one of my beta's has stopped playing Vindictus entirely, so it's slow going at the moment. I've approached a couple of MPGH'ers about being new beta tester, and if they accept this could speed up the process a bit.

My hopeful release date for v2.3 will be August 17th, after making sure that consoles and god/ohk still work, as well as all commands used by the bot are still functional.

OLI CARP!. MINING BOT,

me.. love... zaiakunokami, bromance!

Wow lots of progress I see

Can't wait to test out your new creations. I've been using your bots on and off the last few days and I notice that the skipmap may sometime miss. I notice that there is no inherently bad side effects from having the bot hit the skip map twice even though the map only requires one skip to get to the boss..

As a result I think it will be a good idea to let the bot have at minimum +1 more skip functions than necessary to insure that the map actually skips.

Also do you choose beta/alpha testers are random or is their an application somewhere O.o?

Originally Posted by nick2412

Wow lots of progress I see

Can't wait to test out your new creations. I've been using your bots on and off the last few days and I notice that the skipmap may sometime miss. I notice that there is no inherently bad side effects from having the bot hit the skip map twice even though the map only requires one skip to get to the boss..

As a result I think it will be a good idea to let the bot have at minimum +1 more skip functions than necessary to insure that the map actually skips.

Also do you choose beta/alpha testers are random or is their an application somewhere O.o?

Yeah, I noticed that bug in v2.2 as well. It's due to the occasional start boat lag. Trying to implement a pixel check that doesn't start the firstmap= timer until that "The boat is being launched..." screen goes away, but I have a feeling that I'll run into a lot of issues of color differences on peoples screens.

What I've done instead, is add an extra function, that if the Battle Cleared screen doesn't show, it skips all the maps again to make sure it's at boss room. I thought about adding an extra map skip per map, but that adds time to every run. Whereas my method only adds time (albeit more time) to runs that error out.

And I chose two people here who seem like they have some experience and/or fast learners with scripts to help me diagnose where issues are. Haven't heard back from one yet.

I used a pixel check on the health bar for that one (Boat is being launched... delay)

once the health bar goes away, the boat is successfully started

Originally Posted by dumblet

I used a pixel check on the health bar for that one (Boat is being launched... delay)

once the health bar goes away, the boat is successfully started

Yeah, I was going a different route with it, doing a check on the bottom toolbar area was my most recent try. It seems to be working, so I'll run with it. Thanks for the idea though.

@Zaiakunokami

Here you are as a token of appreciation for creating this wonderful bot!

http://i.imgur.com/8jbNq.png

I have different styles if you want to see them

, Its just the border color difference, nothing major.

V2

Originally Posted by getdunkedonby

Here you are as a token of appreciation for creating this wonderful bot!

http://i.imgur.com/8jbNq.png

I have different styles if you want to see them

, Its just the border color difference, nothing major.

V2

@getdunkedonby
That sir. Is awesome.
I love the top one for everything but the name
Do you think it'd be possible to just remove the border around the name, but leave it around the rest?

If so, I will so be using that! My little GIMP creation is alright, but that is just .... pure win.

Oh hey. Post #200. In 2 weeks.

Similar Threads

Tags for this Thread