-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: finishing writing documentation
- Loading branch information
Showing
9 changed files
with
114 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,48 @@ | ||
# Alerts | ||
# Alerts | ||
|
||
- `. alert` or `. alert --help` helps to find out all avilable alerts. Continue using `--help` for discovered sub commands, to find out all options. | ||
![](https://raw.githubusercontent.com/darklab8/fl-darkbot/master/docs/index_assets/alerts_commands.png) | ||
|
||
## Base alerts | ||
|
||
### Base health below threshold | ||
|
||
- `. alert base_health_is_lower_than set 90` - the most convinient command to receive alerts about. It pings you if any base health below 90% in the current configuration. | ||
- `. alert base_health_is_lower_than status` to check current configuration | ||
- `. alert base_health_is_lower_than unset` to disable alert | ||
|
||
### Base under attack | ||
|
||
- `. alert base_is_under_attack enable` - turns on alert if spotting the base in forum thread for base attack declarations. | ||
enable, disable, status sub commands are similar. | ||
|
||
### Base Health decreasal (may be miss maintained. To check.) | ||
|
||
![events view](alerts_base1_commands.png) | ||
|
||
- you can turn on `. alert base_health_is_decreasing enable` command for making alert if base rapidly looses its health. | ||
|
||
## Player alerts | ||
|
||
### Enemy player alert | ||
|
||
- `. alert player_enemy_count_above set 1` - Sets alert to ping if spotting enemies above this count in tracked regions/systems. | ||
- `. alert player_enemy_count_above status` to check status of configuration | ||
- `. alert player_enemy_count_above unset` to unset the alert | ||
|
||
### Neutral player alert | ||
|
||
- `. player_neutral_count_above set 1` - Sets alert if finding more than X neutral players in tracked systems, regions. Convinient command if not knowing who you track, but knowing where. | ||
- commands set, status and unset are similar to enemy alert configuration | ||
|
||
### Friends alert | ||
|
||
- `. alert player_friend_count_above set 0` - if your friends login, you can spot them right away across galaxy. This command is not affected by which regions/systems you track. | ||
- commands set, status and unset are similar to enemy alert configuration. | ||
|
||
## Ping message | ||
|
||
- By default Discord server owner is pinged ( `<@DiscordServer.Owner.ID>` ) | ||
- `. alert ping_message @here` - You can change to `@here` or `@specific_role` by setting this | ||
- `. alert ping_message status` - you can use sub command `status` to check configuration like | ||
- `. alert ping_message unset` - you can unset to default ping message |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,18 @@ | ||
# Events tracking | ||
|
||
![events view](https://raw.githubusercontent.com/darklab8/fl-darkbot/master/docs/index_assets/events_table.png) | ||
![events view](https://raw.githubusercontent.com/darklab8/fl-darkbot/master/docs/index_assets/events_table.png) | ||
|
||
This feature was implemented on request from Event manager Barrier, for the purpose of easily tracking | ||
that all players participating in event, arrived to the scene. | ||
|
||
- `. player event add PlayerPreffixOrSuffix` - add player for tracking for event | ||
- `. player event add Any Partial Name` - add player for tracking for event | ||
|
||
- `. player event remove Any Partial Name` - remove specific one from tracking | ||
|
||
- `. player event list` - check tracked players | ||
- `. player event clear` - clear all tracked players | ||
|
||
P.S. ensure you used `. connect` first one some channel to turn one bot on. | ||
Beware. bot automatically erases msgs for the channel for comfort of its usage. | ||
Use bot on dedicated channel. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.