forked from Noctem/Monocle
-
Notifications
You must be signed in to change notification settings - Fork 20
pgscout
Hydro74000 edited this page Nov 27, 2017
·
1 revision
If PGSCOUT_ENDPOINT
is set, PGScout will be used for encountering. Otherwise, usual Monocle encounter will be used if conditions are right.
If you have multiple instances of PGScout running, just set the endpoints separated by commas as in the example below. They will be cycled in round-robin.
####
### PgScout (Credit to Avatar690)
## MUST MATCH YOUR PGSCOUT CONFIG.JSON. Will encounter based on ENCOUNTER_IDs above.
## If encounter fails, worker.py will attempt to encounter with the running acount (if lv > 30)
## If it fails, sighting will be saved without additional encounter info.
### Enter in your address for PGSCOUT hook endpoint including hostname, port (if any) and path.
### If set to a url, PGSCOUT will be used. If None, normal Monocle encounter will be used.
#
#PGSCOUT_ENDPOINT = None
#
## Example,
#PGSCOUT_ENDPOINT = {"http://127.0.0.1:1234/iv","http://127.0.0.1:1235/iv"}
## Set the connection timeout to wait on a response from PGScout. Default is 40 seconds.
## Timeout will be connection dependent, proxy dependent, etc. I recommend keeping it at the default.
## Going too high will certainly guarantee a response from a Scout but will lead to greater inefficiency
## and instability for Monocle
#
#PGSCOUT_TIMEOUT = 40
#