-########################################################################
-# #
-# ___ ___ ____ ____ _ #
-# |_ _|_ __ ___ _ __|_ _| _ \ / ___|__| | #
-# | || '_ \/ __| '_ \| || |_) | | / _` | #
-# | || | | \__ \ |_) | || _ <| |__| (_| | #
-# |___|_| |_|___/ .__/___|_| \_\\____\__,_| #
-# |_| #
-# ____ __ _ _ _ #
-# / ___|___ _ __ / _(_) __ _ _ _ _ __ __ _| |_(_) ___ _ __ #
-# | | / _ \| '_ \| |_| |/ _` | | | | '__/ _` | __| |/ _ \| '_ \ #
-# | |__| (_) | | | | _| | (_| | |_| | | | (_| | |_| | (_) | | | | #
-# \____\___/|_| |_|_| |_|\__, |\__,_|_| \__,_|\__|_|\___/|_| |_| #
-# |___/ #
-# #
-##################################||####################################
- #||#
-##################################||####################################
-# #
-# This is an example of the config file for InspIRCd. #
-# Change the options to suit your network. #
-# #
-# #
-# ____ _ _____ _ _ ____ _ _ _ #
-# | _ \ ___ __ _ __| | |_ _| |__ (_)___ | __ )(_) |_| | #
-# | |_) / _ \/ _` |/ _` | | | | '_ \| / __| | _ \| | __| | #
-# | _ < __/ (_| | (_| | | | | | | | \__ \ | |_) | | |_|_| #
-# |_| \_\___|\__,_|\__,_| |_| |_| |_|_|___/ |____/|_|\__(_) #
-# #
-# Lines prefixed with READ THIS BIT, as shown above, are IMPORTANT #
-# lines, and you REALLY SHOULD READ THEM. Yes, THIS MEANS YOU. Even #
-# if you've configured InspIRCd before, these probably indicate #
-# something new or different to this version and you SHOULD READ IT. #
-# #
-########################################################################
-
-#-#-#-#-#-#-#-#-#-# CONFIGURATION FORMAT #-#-#-#-#-#-#-#-#-#-#-#-#-#-
-# #
-# In order to maintain compatibility with older configuration files, #
-# you can change the configuration parser to parse as it did in #
-# previous releases. When using the "compat" format, you need to use #
-# C++ escape sequences (e.g. \n) instead of XML ones (e.g. &nl;) and #
-# can not use <define> to create macros. #
-#<config format="compat">
-
-#-#-#-#-#-#-#-#-#-# INCLUDE CONFIGURATION #-#-#-#-#-#-#-#-#-#-#-#-#-#
-# #
-# This optional tag allows you to include another config file #
-# allowing you to keep your configuration tidy. The configuration #
-# file you include will be treated as part of the configuration file #
-# which includes it, in simple terms the inclusion is transparent. #
-# #
-# All paths to config files are relative to the config directory. #
-# #
-# You may also include an executable file, in which case if you do so #
-# the output of the executable on the standard output will be added #
-# to your config at the point of the include tag. #
-# #
-# Syntax is as follows: #
-#<include file="file.conf"> #
-#<include directory="modules"> #
-#<include executable="/path/to/executable parameters"> #
-# #
-# Executable include example: #
-#<include executable="/usr/bin/wget -q -O - https://example.com/inspircd.conf">
-# #
-# <include executable="sh ./conf/config.sh" noexec="no">
-
-
#-#-#-#-#-#-#-#-#-#-#-#- SERVER DESCRIPTION -#-#-#-#-#-#-#-#-#-#-#-#-
# #
# Here is where you enter the information about your server. #