From 6ef78086f8160f9c1355121e93b2bbb46ef8e082 Mon Sep 17 00:00:00 2001
From: Kevin Easton <caf@bitchx.org>
Date: Wed, 26 Jun 2019 17:26:02 +1000
Subject: [PATCH] Bump MAXPARA (maximum protocol message arguments) to 20 as
 per EPIC5

Needed to bump it to 16 anyway (the RFC says 15 plus the protocol command itself, so 16), but EPIC5 bumped it
up to 20 based on a report from users of RusNet so we might as well go up to that as well.
---
 Changelog       | 2 ++
 include/parse.h | 2 +-
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/Changelog b/Changelog
index 62c8b0c..8c435e7 100644
--- a/Changelog
+++ b/Changelog
@@ -1,5 +1,7 @@
 [Changes 1.2.2]
 
+* Bump MAXPARA (maximum protocol message arguments) to 20 as per EPIC5. (caf)
+
 * Correctly handle a last argument prefixed with : for any protocol message,
   for compatibility with inspircd.  Reported by trn. (caf)
 
diff --git a/include/parse.h b/include/parse.h
index 564aad7..4221d3b 100644
--- a/include/parse.h
+++ b/include/parse.h
@@ -44,7 +44,7 @@ extern	int	doing_privmsg;
 #define WAIT_BANS 1
 #define WAIT_MODE 2
 
-#define MAXPARA 15
+#define MAXPARA 20	/* RFC1459 says 15+1, but RusNet uses more */
 
 
 #endif /* PARSE_H_ */