From 937404e3118f10735875ff45a658facbf77e984d Mon Sep 17 00:00:00 2001 From: Sadie Powell Date: Mon, 5 May 2025 18:00:50 +0100 Subject: Optimise the maths for the jsonrpc oversize integer workaround. --- data/modules.example.conf | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'data/modules.example.conf') diff --git a/data/modules.example.conf b/data/modules.example.conf index 93aa0df54..b6c86871d 100644 --- a/data/modules.example.conf +++ b/data/modules.example.conf @@ -814,14 +814,14 @@ module * The maximum number of bits an integer can be have in its native type. * * By default Anope will emit integers as their native JSON type. If you are - * using JavaScript (which has 56 bit integers) or another language with + * using JavaScript (which has 53 bit integers) or another language with * native integer types smaller than 64 bits you may need to limit the size * of integers emitted by Anope. * * If this is enabled a string will be used for values outside of the range * supported by the native data type. */ - #integer_bits = 56 + #integer_bits = 53 /* Web service to use. Requires httpd. */ server = "httpd/main" -- cgit