Updated Common Errors (markdown)
parent
102e9e4bd5
commit
a07b590e82
|
@ -23,7 +23,7 @@ This means you have specified a settings file in one of your global settings, bu
|
||||||
Starting with version 2.1.0, you need to add an API token to settings.general.json to match the API token in your Profit Trailer settings. [See 2.1.0 release notes](https://github.com/PTMagicians/PTMagic/releases/tag/2.1.0).
|
Starting with version 2.1.0, you need to add an API token to settings.general.json to match the API token in your Profit Trailer settings. [See 2.1.0 release notes](https://github.com/PTMagicians/PTMagic/releases/tag/2.1.0).
|
||||||
|
|
||||||
### Unhandled Exception: System.NullReferenceException / Object Reference not set to an instance of an object.
|
### Unhandled Exception: System.NullReferenceException / Object Reference not set to an instance of an object.
|
||||||
Your settings.general.json file is likely missing a necessary setting in the "Application" section. Check the release notes for any recent releases that you might have skipped since you last updated PTMagic, for any REQUIRED settings changes.
|
Your settings.general.json file is unable to find a necessary setting in the "Application" section, either because it has been omitted, or a comma is missing at the end of the previous line. Check that you have a comma at the end of every line in your settings, and check the release notes for any REQUIRED settings changes that you might have skipped since you last updated PTMagic.
|
||||||
|
|
||||||
### PTMagic has been raiding since (DATE) (TIME). Checking things...
|
### PTMagic has been raiding since (DATE) (TIME). Checking things...
|
||||||
This usually happens when a raid takes longer than the **IntervalMinutes** you've set in settings.analzyer.json. The interval has elapsed, and PTM is trying to start a new raid, but the previous raid is still being executed. This not a serious problem, however, descreasing resource usage by other applications, or increasing PTM's priority can help speed up raids.
|
This usually happens when a raid takes longer than the **IntervalMinutes** you've set in settings.analzyer.json. The interval has elapsed, and PTM is trying to start a new raid, but the previous raid is still being executed. This not a serious problem, however, descreasing resource usage by other applications, or increasing PTM's priority can help speed up raids.
|
||||||
|
|
Loading…
Reference in New Issue