Prerequisite Information
TASKS: There are two types of tasks that Shikari uses; Watchdog & Checkout.
• Watchdog tasks are the way Shikari monitors products. • Checkout tasks are what execute the checkout process.
You'll need to have at least one
Watchdogtask running for any site you plan to run for, as this is what's used to communicate to theCheckouttask that an item is in stock, so theCheckouttask will then try to Add To Cart -> Checkout.
Your
Watchdogtasks are not solely tied to one of yourCheckouttasks; they communicate with allCheckouttasks that you are running, even for ones in a different Task Group than where yourWatchdogtasks are located.
Each type of
WatchdogandCheckouttask where you can input more than one will be denoted by being a plural (TCINs, PIDs, OIDs, etc.).
Your
Checkouttasks do not have to exactly match the inputs of yourWatchdogtasks. You're able to split the input(s) depending on your use case.EXAMPLE 1:
TCINs Watchdog123456, 654321, 24680Checkout Task 1(Profile 1) 123456Checkout Task 2(Profile 2) 654321, 24680Checkout Task 3(Profile 3) 123456, 24680EXAMPLE 2:
TCINs Watchdog123456, 654321, 24680Checkout Task 1(Profile 1) 123456, 654321, 24680
You can just create a
Watchdogtask(s) that contains all of your desired input(s) then compartmentalize your profile(s) with yourCheckouttask(s).
If you have a
Checkouttask with multiple inputs and yourWatchdogspick up more than one at the same time, Shikari will select an input at random from yourCheckouttask to execute the checkout process.
Certain modules will have a
Watchdogwith theTarget MethodcalledRemote.Remoteis our server-side monitoring system where you will just need one of this type ofWatchdogrunning and then have any of yourCheckouttasks filled with any of the inputs we're monitoring for in the server's channel's. Works the same way as the otherWatchdogswithout the need to setup inputs yourself.
The examples shown above are using the Target module.
Last updated