2017-03-13 21:50:16 +01:00
# Advanced Services Configuration
2017-03-13 16:35:32 +01:00
There are some service configuration options that you may want to be aware of.
#### Nick / Ident
2017-03-13 21:50:16 +01:00
You can override the `nick` or `ident` of a service bot using a directive liek this:
2017-03-13 16:35:32 +01:00
```yaml
servers:
somenet:
# ...
SERVICE_nick: OTHERNICK
SERVICE_ident: OTHERIDENT
2017-03-13 21:50:16 +01:00
```
2017-03-13 16:35:32 +01:00
2017-03-13 21:50:16 +01:00
You can also set an arbitrary nick/ident using a per-**service** directive.
2017-03-13 16:35:32 +01:00
```yaml
SERVICE:
nick: OTHERNICK
ident: OTHERIDENT
```
2017-03-13 21:50:16 +01:00
#### joinmodes
2017-03-13 16:35:32 +01:00
2017-03-13 21:50:16 +01:00
By default, service bots join channels without giving themselves any modes. You can configure what modes a service bot joins channels with using this directive:
2017-03-13 16:35:32 +01:00
```yaml
SERVICE:
joinmodes: 'o'
```
2017-03-13 21:50:16 +01:00
This would request the mode 'o' (op on most IRCds) when joining the channel.
2017-03-13 16:35:32 +01:00
Technically any mode can be put here, but if an IRCd in question doesn't support
2017-03-13 21:50:16 +01:00
the mode then it will be ignored.
2017-03-13 16:35:32 +01:00
You can also use combinations of modes, such as 'ao' (usually admin/protect + op)
```yaml
SERVICE:
joinmodes: 'ao'
```
Combinations should work provided an IRCd in question supports it.
2017-03-13 21:50:16 +01:00
#### Fantasy prefix
2017-03-13 16:35:32 +01:00
2017-03-13 21:50:16 +01:00
You can also set the service bot's fantasy prefix; of course this is only
applicable if the `fantasy` plugin is loaded.
2017-03-13 16:35:32 +01:00
The setting allows for one or more characters to be set as the prefix.
```yaml
SERVICE:
2017-03-13 21:50:16 +01:00
prefix: './'
2017-03-13 16:35:32 +01:00
```
2017-03-13 21:50:16 +01:00
The above is perfectly valid, as is any other string.
2017-03-13 16:35:32 +01:00