-
-
Notifications
You must be signed in to change notification settings - Fork 22
Globals
kca_globals.py contains some additional settings meant for the advanced/power user of kcauto-kai. The variables contained in this file vary in scope and consequences across kcauto-kai's functionality. Some of the variables here should not be altered (the SIMILARITY and EXPAND variables, for example), but the others may be useful for tweaking kcauto-kai to the user's needs.
Specifies how many times per second the Sikuli image scan should be fired (a lower number results in less scans per second). If the machine running kcauto-kai has a weaker CPU/VM and the Live Combat engine is causing issues, lowering this value might help alleviate the CPU load.
Default: 20
Specifies how long to sleep between each kcauto-kai cycle, in seconds. Modifying this value changes the length of time between kcauto-kai printing its end-of-cycle stats and the next iteration where it begins to check for received expeditions, sorties, etc. If a more responsive kcauto-kai is desired, consider lowering this value, but take care since it may invite catbombs.
Default: 15
The default quest check frequency, assuming no other frequencies exist internally in the Quest module. Lower this value to have kcauto-kai check quests more frequently, raise it to check less frequently.
Default: 5
The sleep modifier is added to every internal sleep kcauto-kai conducts. If the network kcauto-kai is running on is slow/tends to have delays and the script frequently fails due to a laggy game, consider raising this little by little.
Default: 0
How many minutes to wait between sorties. Raising this allows for natural morale regeneration between automated sorties.
Default: 0
When using the Combat and ShipSwitcher module with the sparkle setting as a ShipSwitch criteria, the ShipSwitcher module will switch the ship out after this many combat sorties. Raise or lower according to how well your ships are being sparkled.
Default: 3
It is not recommended that these values be modified. If they are, extreme care should be taken. Most of them have been tweaked specifically for their use case, and modifying them may result in damage or fatigue states being mis-identified, or the fleet position being mis-tracked, or instability in general.
Please use the debug and debugc command line arguments to validate custom similarity thresholds.
kcauto Wiki
Developer's Corner