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
Watchdog
task running for any site you plan to run for, as this is what's used to communicate to theCheckout
task that an item is in stock, so theCheckout
task will then try to Add To Cart -> Checkout.
Your
Watchdog
tasks are not solely tied to one of yourCheckout
tasks; they communicate with allCheckout
tasks that you are running, even for ones in a different Task Group than where yourWatchdog
tasks are located.
Each type of
Watchdog
andCheckout
task where you can input more than one will be denoted by being a plural (TCINs, PIDs, OIDs, etc.).
Your
Checkout
tasks do not have to exactly match the inputs of yourWatchdog
tasks. You're able to split the input(s) depending on your use case.EXAMPLE 1:
TCINs Watchdog
123456, 654321, 24680Checkout Task 1
(Profile 1) 123456Checkout Task 2
(Profile 2) 654321, 24680Checkout Task 3
(Profile 3) 123456, 24680EXAMPLE 2:
TCINs Watchdog
123456, 654321, 24680Checkout Task 1
(Profile 1) 123456, 654321, 24680
You can just create a
Watchdog
task(s) that contains all of your desired input(s) then compartmentalize your profile(s) with yourCheckout
task(s).
If you have a
Checkout
task with multiple inputs and yourWatchdogs
pick up more than one at the same time, Shikari will select an input at random from yourCheckout
task to execute the checkout process.
Certain modules will have a
Watchdog
with theTarget Method
calledRemote
.Remote
is our server-side monitoring system where you will just need one of this type ofWatchdog
running and then have any of yourCheckout
tasks filled with any of the inputs we're monitoring for in the server's channel's. Works the same way as the otherWatchdogs
without the need to setup inputs yourself.
The examples shown above are using the Target module.
Last updated